WSO2 Mashup Server 2.3.2

• Release Notes
• Contents
• Home

Downloads

• Releases

Documentation

• User Guide
• Administrator Guide
• Quick Start Guide
• Installation Guide
• Source

Administrative Tasks

• Managing Services
• Securing Mashups
• Managing Users
• Running Behind a Proxy
• Clustering Guide
• Changing Keys

Writing Services

• Writing a HelloWorld Service
• Automatically Generated Resources
• Javascript Web Service Annotations
• Javascript Data Binding
• Writing RESTful Services
• Service Lifecycle Support
• E4X Quick Started Guide
• Productivity Tools

Consuming Services

• Hello World Client
• Using Stubs
• Hosted Objects
  • APP
  • Email
  • Feed
  • File
  • HttpClient
  • IM
  • Registry
  • Request
  • Scraper
  • Session
  • System
  • Sparql
  • WSRequest

Get Involved

• Checkout the Source
• Mailing Lists

Project Information

• License

Other References

• Mooshup.com
• WSO2 Mashup Server Reference
• WSO2 Oxygen Task Library
• Mashup Server Community Forum

[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 Mashup Server behind a proxy or a firewall. Though Mashup Server should be behind a proxy or firewall, the ultimate end user should not see this information.

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

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

When Mashup Server 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 Mashup Server 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 Mashup Server 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 Mashup Server 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 given as the Mashup Server home. By default this will be $USER_HOME/.wso2mashup. 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 Mashup Server instance is ready for accept request coming through the proxy. You should uncomment the @proxyPort parameter in both http and https listeners.