Skip to main content

Fronting WSO2 AS worker/manager cluster with Nginx

This Blog describes how to configure Nginx as a load balancer with WSO2 Application Server cluster

Nginx 1.4.1
WSO2 Application Server 5.2.1

Setup WSO2 AS Cluster


This cluster consist of 3 WSO2 Application Server instances, as 3 worker nodes and 1 manager node, where 1 node work as both worker and manager. Nginx performs load balancing with this cluster by distributing incoming requests to the worker nodes via HTTP/S on port 80/443.

All admin requests can be sent to the manager node directly via HTTPs on port 9444 or through the Nginx via 443 port depending on how we configure the manager node.
Click here to see how to setup WSO2 Application Server cluster

Setup Nginx load balancer
* Install Nginx
$sudo apt-get install nginx
* Locate the http{} block of the /etc/nginx/nginx.conf file and add the following
# load balancing among the worker nodes - HTTP
upstream wso2.as.com {
            server as.wso2.com:9764;
          server as.wso2.com:9765;
          server as.wso2.com:9766;
}

server {
          listen 80;
          server_name as.wso2.com;
          location / {
                      proxy_pass http://wso2.as.com;
          }
}

# load balancing among the worker nodes - HTTPS
# To configure load balancing for HTTPS instead of HTTP, just use “https” as the protocol.
upstream ssl.wso2.as.com {
          server as.wso2.com:9444;
          server as.wso2.com:9445;
          server as.wso2.com:9446;
}

server {
          listen 443;
          server_name as.wso2.com;
          ssl on;
          ssl_certificate /etc/nginx/ssl/server.crt;
          ssl_certificate_key /etc/nginx/ssl/server.key;
          location / {
                      proxy_pass https://ssl.wso2.as.com;
          }
}

# access the management console via HTTPS
server {
          listen 443;
          server_name mgt.as.wso2.com;
          ssl on;
          ssl_certificate /etc/nginx/ssl/server.crt;
          ssl_certificate_key /etc/nginx/ssl/server.key;
          location /carbon {
              proxy_pass https://mgt.as.wso2.com:9444;
          }
}
* Mapping the host names to the IP
Update the “/etc/hosts” file
<IP-of-worker>    as.wso2.com
<IP-of-manager>    mgt.as.wso2.com
* Restart the Nginx
$sudo /etc/init.d/nginx restart

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