Configuration has yet to be fully verified, Kemp Support will gladly assist if your WSO2 traffic is not flowing as expected.
1 Introduction
WSO2 is an Application Server, you can easily share business logic, data, and process across the entire IT ecosystem. The WSO2 Application Server is cloud native, providing a firm foundation for hosting shared, multi-tenant, elastically scaling SaaS applications.
1.1 Document Purpose
This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested
This specific configuration will ensure that your WSO2 servers are highly-available, scalable, and secure.
Configuration has yet to be fully verified, Kemp Support will gladly assist if your WSO2 traffic is not flowing as expected.
2 Configuration
2.1 Global Configuration
No Changes Required
2.2 Virtual Service Configuration
One virtual Service is required that will listen on port 443, where traffic will be forwarded on port 9443. If required, a second virtual service will be used to redirect port 80 traffic to port 443.
Port 80 Redirect
When 443 Virtual Service is created, navigate to Modify VS --> Advanced Properties --> Add a Port 80 Redirector VS
2.3 Create VS
> New Virtual Service
> Enter IP Address
> Port = 443
> Name = WSO2
> Add New Virtual Service
2.4 Standard Options
> Persistence = Super HTTP (You will need to enable "SSL Acceleration" in SSL Properties in section 2.5)
> Timeout = 1 Hours
> Scheduling Method = Least Connection
2.5 Enable SSL Acceleration & Tick Reencrypt
> Assign Certificate
2.6 Real Servers
> Checker Parameter Type = HTTPS
> Checked Port = 9443
> url: = /store
> Add New
> Enter Real Server IP Address
> Port = 9443
> Forwarding Method = NAT
If you have successfully Load Balanced your Horizon WSO2 by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you
0 comments