...
You configure datasources to allow the manager node to point to the central database. Make sure that you copy the database driver JAR to the manager node and follow the steps described in Setting Creating a Cluster#Setting up the central database.
| Info |
|---|
In most WSO2 products, only one data source is used. If there is more than one data source, make sure they reference the central databases accordingly. For example, the API Manager deployment setup requires more specific data source configurations. |
...
You configure the data source to connect to the central database. If there are multiple data sources, configure them to reference the central database as well. Since the data source changes are the same for all worker nodes, you can configure this file on one node and then copy it to the other worker nodes. Make sure you copy the database driver JAR to each worker node and follow the steps described in Setting Creating a Cluster#Setting up the central database.
After you have finished configuring the data source, be sure to copy this configuration to the other worker nodes in the cluster.
...
- Enable clustering for this node:
<clustering class="org.apache.axis2.clustering.tribes.TribesClusteringAgent" enable="true"> - Set the membership scheme to
wkato enable the Well Known Address registration method (this node will send cluster initiation messages to WKA members that we will define later):<parameter name="membershipScheme">wka</parameter> - Specify the name of the cluster this node will join:
<parameter name="domain">wso2.esb.domain</parameter> - Specify the port used to communicate cluster messages (if this node is on the same server as the ELB, manager node, or another worker node, be sure to set this to a unique value, such as 4000 and 4001 for worker nodes 1 and 3 and 4002 for worker node 2, which is on the same server as the ELB and manager node):
<parameter name="localMemberPort">4000</parameter>
Note: This port number will not be affected by the port offset incarbon.xml. If this port number is already assigned to another server, the clustering framework will automatically increment this port number. However, if two servers are running on the same machine, you must ensure that a unique port is set for each server. - Define the sub-domain as worker by adding the following property under the
<parameter name="properties">element:<property name="subDomain" value="worker"/> Define the ELB and manager nodes as well-known members of the cluster by providing their host name and
localMemberPortvalues. The manager node is defined here because it is required for the Deployment Synchronizer to function.Code Block language html/xml <members> <member> <hostName>elb.wso2.com</hostName> <port>4000</port> </member> <member> <hostName>mgt.esb.wso2.com</hostName> <port>4001</port> </member> </members>
- Enable clustering for this node:
...