Changing the Messaging Bus of an Environment

Changing the Messaging Bus EMS is a high-impact operation that affects all nodes in a particular ActiveMatrix Environment. The high-level steps are:

Procedure

  1. Stop all the Nodes in the Environment (except SystemNode) for which you want to update the messaging bus. This is a quicker alternative to stopping each Application, when there are a variable number or a large number of Applications. For SystemEnvironment, stop each Application on the SystemNode.
    Warning: In this step, the SystemNode cannot be stopped because "setMessagingBus" would fail in the next step if SystemNode was stopped.
    To automate this step, refer to the CLI sample script: node_build.xml and node_data.xml (ANT target "stop") or use the following command: 
    tibcohost stopNodes -nodeNames DevNode DevNodeReplic
  2. Edit the messaging bus configuration, as described in Configuring an Environment's Messaging Bus.
    To automate this step, refer to the CLI sample script: environment_build.xml, environment_data.xml (ANT target "setMessagingBus").
  3. Start all Nodes in the current Environment (or restart the Nodes, if they were already running). The Nodes now use the new Messaging Bus configuration. However, applications that use Virtualization will not work until step 4 and 5 are also completed.
    To automate this step, refer to the CLI sample script: node_build.xml and node_data.xml (ANT target "stop") or use command: 
    tibcohost startNodes -nodeNames DevNode DevNodeReplic
  4. Stop all Nodes in the ActiveMatrix Environment again.
  5. Start all Nodes in the ActiveMatrix Environment again.
    After this, the applications that use Virtualization will start working correctly.