This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

For information on additional configuration required for clustering other WSO2 products, click that product's link here.

WSO2 provides Hazelcast Community Edition as its default clustering engine. Advanced users can fine-tune Hazelcast by creating a <CARBON_HOME>/repository/conf/hazelcast.properties file and adding the relevant Hazelcast properties as described in the Hazelcast Advanced Configuration Properties documentation. If you use Hazelcast Enterprise Edition or Hazelcast Management Center, see the Hazelcast documentation for details on configuring those products.

  • If you need to provide access to the management node from outside your network so external clients can upload applications and perform other management tasks, you configure the mgt sub-domain in loadbalancer.conf and map the host to the IP address of the ELB. For example, you would add the mgt sub-domain to loadbalancer.conf as follows:

    loadbalancer.conf
    appserver {
  domains{
     wso2.as.domain {
        tenant_range *;
        group_mgt_port 5000;
        mgt {
                hosts management.as.cloud-test.wso2.com;
        }
        worker {
               hosts as.cloud-test.wso2.com;
        }
     }
   }
}

    You would then add the management.as.cloud-test.wso2.com port mapping in the /etc/hosts file as follows:

    /etc/hosts file
    xxx.xxx.xxx.xxx management.as.cloud-test.wso2.com 
xxx.xxx.xxx.xxx as.cloud-test.wso2.com
  • No labels