|
|
A general discussion of configuring messaging engine failover with the No Operation Policy is provided in 9.7, Default messaging provider failover with No Operation policy. In this section we discuss how to configure VCS to correctly failover the messaging engine with the No Operation policy.
In order to describe the configuration we refer to the example defined in 9.7.2, Default messaging provider with No Operation policy scenario. In our setup, we have two WAS nodes. One node is the system named Bottechia and the other is the system named SystemB. Each node hosts a single appserver which is part of a cluster called TradeCluster. The cluster members are TradeServer1 on Bottechia and TradeServer2 on SystemB. The Trade 6 application is configured with two messaging engines (ME): TradeCluster.000-TradeCluster and TradeCluster.001-TradeCluster. The primary cluster member for the TradeCluster.000-TradeCluster messaging engine is TradeServer1 and the primary cluster member for the TradeCluster.001-TradeCluster messaging engine is TradeServer2.
In order to configure VCS, we need to define the following service groups:
| 1. | WAS servers service group |
This group will be configured as parallel (Active/Active) and will start, stop, and monitor the Node Agent and the cluster members.
| 2. | ME activate for system Bottechia |
This group will be configured as failover (Active/Passive) and will activate, deactivate and monitor the ME on system Bottechia (primary) and failover to system SystemB (secondary).
| 3. | ME activate for system SystemB |
This group will be configured as failover (Active/Passive) and will activate, deactivate and monitor the ME on system SystemB (primary) and failover to system Bottechia (secondary).
We also need to configure links (dependencies) between each group. The ME activate groups are linked to the WAS servers group. This means that the ME activate groups will not start until the WAS servers group completes starting. The ME activate groups are not linked to each other.
