I wouldn't have guessed from the title, but the topic of the posting is details about how the High Availability Manager in WAS 6.x works. The HA Manager is a major step forward, and part of the basis for WXD. It works by keeping the cluster members in contact with each other, electing where to run singletons, and holding new elections when outages are detected. Billy explains some of the details about how all this works.
Have you ever wondered, "Why use WAS 6 instead of some other J2EE app server? Aren't they all just J2EE?" One of the main capabilities that separates the J2EE app server men from the boys is clustering and high availability. WAS does this really well; a WAS application sees the results as what we call workload management (WLM), which provides load balancing and failover, which makes apps HA even when individual app servers or host machines are not so HA. It's interesting to read about how it all works.
For more info:
- Webcast: WebSphere Extended Deployment
- WAS: Details on Async Beans and Startup Beans
- J2EE: More Good Stuff from Billy Newport
- WAS 6 High Availability Redbook
- "Transactional high availability and deployment considerations in WebSphere Application Server V6" by John Beaven and Ian Robinson
- "Automate peer recovery for transactions and messages in WebSphere Application Server V6.0.x" by Li-Fang Lee and Kristi Peterson
- "Configuring and using XA distributed transactions in WebSphere Studio" by Bobby Woolf (hey, that's me!)