<!--
  ~ Copyright 2005-2007 WSO2, Inc. (http://wso2.com)
  ~
  ~ Licensed under the Apache License, Version 2.0 (the "License");
  ~ you may not use this file except in compliance with the License.
  ~ You may obtain a copy of the License at
  ~
  ~ http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing, software
  ~ distributed under the License is distributed on an "AS IS" BASIS,
  ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  ~ See the License for the specific language governing permissions and
  ~ limitations under the License.
  -->

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
       "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<body>
<p>[<a
href="http://dist.wso2.org/products/wsas/java/@wso2wsas_version@">Download</a>]
| [<a href="index_docs.html">Documentation Home</a>] | [<a
href="release_notes.html">Release Note</a>]</p>
    <h1>Running behind an Apache HTTPD Proxy</h1>

    <p>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.</p>
    <p>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.</p>

    <ol>
        <li>As an embedded server on top of Embedded Tomcat. </li>
        <li>In a Servlet container. </li>
    </ol>
<p>
    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.
</p>

    <p>Lets assume you have enabled
        <a href="http://httpd.apache.org/docs/2.0/mod/mod_proxy.html">mod_proxy</a>
    </p>

    <h3>Mode 1:</h3>

<p>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.</p> 


<h3>Mode 2: </h3>

<p>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.</p>
</body>
</html>