Page Comparison

...

1. Navigate to  <EI_HOME>/bin/ via the terminal  and start the Message broker profile:

   Panel
   borderColor #542989 bgColor #ffffff borderWidth 1
   Localtabgroup Localtab active true title On MacOS/Linux/CentOS Open a terminal and execute the following command: Code Block wso2ei-6.46.0-broker Localtab title On Windows Go to  Start Menu -> Programs -> WSO2 -> Enterprise Integrator 6.4.0 Broker.  This will open a terminal and start the Message Broker profile.

2. Check for ‘member joined’ log messages in all consoles.

   Info
   title Additional information on logs and new nodes
   When you terminate one node, all nodes identify that the node has left the cluster. The same applies when a new node joins the cluster. If you want to add another new node, copy existing node without any changes if you are running it on a new server (such as xxx.xxx.xxx.184). If you intend to use the new node on a server where another WSO2 product is running, use a copy of node and change the port offset accordingly in the <EI_HOME>/wso2/broker/conf/carbon.xml file. You also have to change localMemberPort in the <EI_HOME>/wso2/broker/conf/axis2/axis2.xml file if that product has clustering enabled. Also, map all hostnames to the relevant IP addresses when creating a new node. The log messages indicate if the new node joins the cluster.

3. Access the Management Console through the LB using the following URL:  https://xxx.xxx.xxx.xx2:443/carbon
4. Sign into the management console using admin as the username and password.
5. Click Node List.
   
   You see that the 2 nodes are up and running successfully. The message store health needs to be Healthy and only one node can be the Coordinator Node. 
   

...