Skip to main content

WSO2 AS worker/manager cluster without WSO2 ELB

This blog describes how to setup WSO2 Application Server worker/manager cluster without using WSO2 Elastic Load Balancer and later we can use this cluster for configure different 3rd party load balances

WSO2 Application Server - 5.2.1

1. Use Cases

Each use case consist of 3 WSO2 AS instances form worker/manager cluster fronting with load balancer.

Use Case 1:
Requests direct to worker node cluster through LB
No access to admin console through LB


 Use Case 2:
Requests direct to worker node cluster through LB.
Allows to access admin console through LB.




Use Case 3:
Requests direct to worker node cluster through LB.
Allows to access admin console through LB.
Additionally manager node also serve requests. (Here manger node work as both worker and manager)






Manager/Worker3
Worker1
Worker2
offset
1
2
3
localMemberPort
4100
4200
4300
http
9764
9765
9766
https
9444
9445
9446


2. Tips to configure 3rd party load balancer

In order to configure the load balancer, need to consider the following
  1. Load balancer ports are http 80 and https 443
  2. Direct the http requests to the worker nodes with load balancing as http://as.wso2.com/<service> via http 80 port
  3. Direct the https requests to the worker nodes with load balancing as https://as.wso2.com/<service> via https 443 port
  4. Access the management console as https://mgt.as.wso2.com/carbon via https 443 port

In WSO2 AS cluster worker nodes server requests on http 9763 and https 9443 ports and can access the management console https 9443 port.



3. Configure the Manager node

1. Unzip the WSO2 AS

2. Setting up the cluster configurations
Edit “<AS_HOME>/repository/conf/axis2/axis2.xml” file as follows

*** Enable clustering for this node:

<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" enable="true">
<parameter name="membershipScheme">wka</parameter>
<parameter name="domain">wso2.as.domain</parameter>
<parameter name="localMemberHost">mgt.as.wso2.com</parameter>
<parameter name="localMemberPort">4100</parameter>

*** Specify the well known member
Here, the well known member is a worker node

<members>
  <member>
        <hostName>as.wso2.com</hostName>
        <port>4200</port>        
  </member>
</members>

3. Configuring the port offset and host name
Edit “<AS_HOME>/repository/conf/carbon.xml” file as follows

<Offset>1</Offset>
<HostName>as.wso2.com</HostName>
<MgtHostName>mgt.as.wso2.com</MgtHostName>


4. Mapping the host names to the IP
Update the “/etc/hosts” file

127.0.0.1    as.wso2.com
127.0.0.1    mgt.as.wso2.com


5. Allow access the management console only through LB

Configure the HTTP/HTTPS proxy ports to communicate through the load balancer
Edit “<AS_HOME>/repository/conf/tomcat/catalina-server.xml” file as follows

<Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
              port="9763"
              proxyPort="80"

<Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
              port="9443"
              proxyPort="443"


4. Configure the worker node


1. Unzip the WSO2 AS

2. Setting up the cluster configurations
Edit “<AS_HOME>/repository/conf/axis2/axis2.xml” file as follows

*** Enable clustering for this node:

<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" enable="true">
<parameter name="membershipScheme">wka</parameter>
<parameter name="domain">wso2.as.domain</parameter>
<parameter name="localMemberHost">as.wso2.com</parameter>
<parameter name="localMemberPort">4200</parameter>



*** Specify the well known member
Here, the well known member is manager node

<members>
  <member>
        <hostName>mgt.as.wso2.com</hostName>
        <port>4100</port>        
  </member>
</members>



3. Configuring the port offset and host name
Edit “<AS_HOME>/repository/conf/carbon.xml” file as follows

<Offset>2</Offset>
<HostName>as.wso2.com</HostName>


4. Configure the HTTP/HTTPS proxy ports to communicate through the load balancer
Edit “<AS_HOME>/repository/conf/tomcat/catalina-server.xml” file as follows

<Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
              port="9763"
              proxyPort="80"

<Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
              port="9443"
              proxyPort="443"


5. Create the worker2 node
Get a copy of worker1 node and change the following in axis2.xml and carbon.xml

<parameter name="localMemberPort">4300</parameter>

<Offset>3</Offset>

5. Testing the cluster


1. Restart the configured load balancer

2. Start the manager node
sudo <AS_HOME>/bin/wso2server.sh

3. Start the worker1 and worker2 nodes
sudo <AS_HOME>/bin/wso2server.sh -DworkerNode=true

4. Check member joined messages in all consoles

5. Access management console https://mgt.as.wso2.com:9444/carbon

6. Access management console through LB https://mgt.as.wso2.com/carbon

7. Testing load distribution - http://as.wso2.com/sample or https://as.wso2.com/sample


Labels:

Comments

Post a Comment

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
Post a Comment
Read more

Tips on using environment variables in WSO2 Integration Cloud

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables U se
Post a Comment
Read more

VFS access SFTP with special character password

Learn WSO2 ESB VFS Transport https://docs.wso2.com/display/ESB481/VFS+Transport When we need to access the FTP server using SFTP, VFS connection-specific URL need to be given as : <parameter name="transport.vfs.FileURI">vfs:sftp://username:p@ssword@ftp.server.com/filePath?vfs.passive=true</parameter> When the password contains a special characters (eg: p@ssword), it gives the following error. 2015-03-27 13:06:03,766  [-]   [PassThroughMessageProcessor-5]  ERROR VFSTransportSender cannot resolve replyFile org.apache.commons.vfs2.FileSystemException: Invalid absolute URI "sftp://username:***@ftp.server.com/filePath?vfs.passive=true". Solution 1: Replace the special characters with the respective hex representation. <parameter name="transport.vfs.FileURI">vfs:sftp://username:p%40ssword@ftp.server.com/filePath?vfs.passive=true</parameter> Char Hex Code ------- -------- [space] %20 &
Post a Comment
Read more