WSO2 AppServer 4.1.2

• Release Notes
• Contents
• Home

Downloads

• Releases

Documentation

• User Guide
• Architecture Guide
• Installation Guide
• Building Source
• Running Behind a Proxy
• Clustering Guide
• Changing Keys
• JMX Monitoring
• WebApp Deployment
• Data Services
• Carbon Apps
• Security Scenarios
• Class Loading

Samples

• Chad
• Commodity Quote
• Flickr
• JAXWS
• JiBX
• MTOM
• Mail
• STS
• Trader
• Tiny URL
• Metadata Exchange
• WS-Transfer
• XKMS
• JSON
• Client API
• WebApp

Resources

• Library
• Features

Get Involved

• Checkout Source
• Mailing Lists
• Issue Tracking

Project Info

• License
• Dependencies

[Download] | [Documentation Home] | [Release Note]

Running behind an Apache HTTPD Proxy

In a production environment or if the network is under certain constrains, it is sometimes necessary to run WSO2 AppServer behind a proxy or a firewall. Even though AppServer should be behind a proxy or firewall, the ultimate end user should not see this information.

Lets assume you have enabled mod_proxy. Steps to enable proxy mode are as follows.

• Open CARBON_HOME/repository/conf/axis2.xml file.
• Find the "transportReceiver" elements for 'http' and 'https' transports.
• Uncomment the "proxyPort" parameter in both 'http' and 'https' transport receivers. For example:

                  <parameter name="proxyPort">80</parameter>
              

AppServer has been designed to run on top of Embedded Tomcat or in Servlet containers such as Tomcat, JBoss, WebLogic etc. Thus, AppServer has two mode of operations. In any case, find the axis2.xml in CARBON_HOME/repository/conf directory and follow the above steps.