HTTP proxy servlet overview

By using the HTTP proxy servlet in a servlet container, you can support high availability, load distribution, access to the integration node from multiple IP addresses and ports, and a larger number of concurrent HTTP sessions.

The HTTP proxy servlet is a Java™ servlet that you can use in a servlet container, such as WebSphere® Application Server Liberty Profile or Apache Tomcat, or in a web server such as IBM WebSphere Application Server. The HTTP proxy servlet receives HTTP requests from web services client applications and replaces the support that is provided by the integration node and embedded (integration server) HTTP listeners.

The HTTP proxy servlet supports SSL (HTTPS) secure protocol when it is deployed in a servlet container that is configured to support SSL.

If you are deploying a web browser-based JavaScript application that uses the JavaScript client API to call an IBM Integration Bus integration service, then you must deploy the proxy servlet on the same web application server as your JavaScript application. For more information about the JavaScript client API, see Integration service JavaScript client API.

You cannot use the HTTP proxy servlet if you configure your integration node environment to use multi-instance WebSphere MQ queue managers because the HTTP proxy servlet cannot connect to the standby queue manager when it becomes active.

For a detailed description of the HTTP proxy servlet, see HTTP proxy servlet operation.

Before you install and test the HTTP proxy servlet, ensure that you understand the following concepts:
When you have gained an understanding of the HTTP proxy servlet concepts, read the following topics to help you configure, install, and test the HTTP proxy servlet: