Passing the token to another node in the Cluster without restarting the IBM Sterling B2B Integrator Server

Body

In this blog you will learn how to pass the token to another node of the Cluster without restarting the node who currently owns the token on the IBM Sterling B2B Integrator Server.

In order to achieve this, you need to use the following commands:
 
opscmd.sh -cMarkNodeUnavailable -pname=node_name (Ex: node1)
 
This command marks a node unavailable for the system. Any node that remains available will take the token.

After this you will need to make the node is available again with the following command:
 
opscmd.sh -cMarkNodeAvailable -pname=node_name
 
This will make the node available again, but the token will remain on the node which became the new token node.
 
NOTE: Meanwhile a node is unavailable the business processes in this node, may not be processed.
 
Example:

In this example node1 has the token.

If node1 has the token and you want node2 to take the it without bringing down the IBM Sterling B2B Integrator (hardstop or softstop), you need to go to the command line of any of the two nodes in the Cluster and run the following command in the <SI>/install/bin directory:

opscmd.sh -cMarkNodeUnavailable -pname=node1

(NOTE: If the script command is not found on this directory go to the <SI>/install/ directory)

If you go the Operations > System > Cluster > Node Status page, you will see the following:

After this you need to wait between 30 to 45 seconds for node 2 to take the token.

Once node 2 has the token you need to run the following command on any of the nodes:
 
opscmd.sh -cMarkNodeAvailable -pname=node1

This will bring node 1 back up in a couple of seconds and the token will remain on node 2.
 

For more opscmd.sh commands visit the following Blog:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Wf96854c0c8fc_4762_9b83_c6247feca5fc