Documentation

##### WSO2 WSAS 2.2-RC1

- Release Notes
- Contents
- Home

##### Downloads

- Releases

##### Documentation

- User Guide
- FAQs
- Installation Guide
- Source
- Running Behind a Proxy
- Data Services Guide
  - RDBMS Data Source
  - CSV Data Source
  - Excel Data Source
  - JNDI Data Source
- EJB Guide
- Clustering Guide
- JMX Guide
- XKMS Guide
- Changing Keys

##### Samples

- Chad
- Commodity Quote
- Data Services
- Flickr
- Javascript
- Jaxws
- JiBX
- Mtom
- STS
- Trader
- Tiny URL
- Metadata Exchange
- WS-Transfer
- XML Key Managment Specification
- Cluster Management

##### API Documentation

- Java Docs

##### Tools

- Code Generation
- Change Password
- Eclipse IDE Integration
- TCP Monitor
- WSDL2Code
- WSDL View
- Try It
- AAR Validation
- MAR Validation

##### Resources

- News

##### Get Involved

- Mailing Lists
- Integration

##### Project Information

- Project Team
- Issue Tracking
- License

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

# Running behind an Apache HTTPD Proxy

In a production environment or the network is under certain constrains, it is sometime necessary to run WSO2 WSAS behind a proxy or a firewall. Though WSAS should be behind a proxy or firewall, the ultimate end user should not see this information.

WSAS has been designed to run on top of Embedded Tomcat or in Servlet containers such as Tomcat, JBoss, Web Logic etc. Thus, WSAS has two mode of operations.

1. As an embedded server on top of Embedded Tomcat.
2. In a Servlet container.

When WSAS has been configured to run on prior modes, it will be give two different axis2.xml by default. This section describes the configuration of theses axis2.xmls, when WSAS is running behind a proxy or a firewall. Lets assume you have enabled mod_proxy

### Mode 1:

axis2.xml is available in "conf" directory, where WSAS is installed. Find the elements that has the tag name transportReceiver. You will be able to find a commented parameter named "proxyPort". Uncomment this one and your WSAS instance is ready for accept request coming through the proxy. You should uncomment the @proxyPort parameter in both http and https listeners.

### Mode 2:

axis2.xml is available in the location where you have give as the WSAS home. By default this will be $USER_HOME/.wso2wsas. Find the elements that has the tag name transportReceiver. You will be able to find a commented parameter named "proxyPort". Uncomment this one and your WSAS instance is ready for accept request coming through the proxy. You should uncomment the @proxyPort parameter in both http and https listeners.