Hardware Clustering and WAS-ND
While the clustering provided by WAS-ND is sufficient for many high-availability deployment requirements, there are cases where hardware clustering can be complementary to WAS-ND clustering. The cases when you may want to consider hardware clustering are:
Application servers that coordinate distributed transactions. As stated earlier in Chapter 11, “Transactions with WebSphere Application Server,” the transactional state is written persistently to disk by WAS. If the machine should fail, that state would be lost, resulting in the transactions being hung in an undefined state. While you can manually recover transaction logs and restart a server process on another node (and there are directions for this in the WAS ...
Get IBM WebSphere: Deployment and Advanced Configuration now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
