|
|
A discussion of configuring the Transaction Manager failover with No Operation Policy is provided in 9.6, Transaction Manager failover with No Operation policy. A discussion of configuring the messaging engine failover with No Operation Policy is provided in 9.7, Default messaging provider failover with No Operation policy.
In this section, we discuss how to configure Sun Cluster to correctly failover the Transaction Manager and messaging engine with the No Operation Policy. For this scenario, we need an Active/Active (or scalable) configuration. Some of the steps for making the Node Agent and appservers available in an Active/Active scenario are similar to the Active/Passive scenario. A scalable group still requires a failover group which contains a logical and scalable host name. This example uses the db2_db2inst1_0-rg as the failover group containing the logical host name, suncluster.
When using an Active/Active or scalable configuration, WebSphere's Transaction Manager and default messaging provider need to be controlled differently. They must be activated manually to avoid conflicts between two active servers trying to use them at the same time.
