See information about the latest product version
HTTP traffic handling by using the proxy servlet in an external web servlet container
Before you install and test the HTTP proxy servlet, ensure that you understand the structure of HTTP traffic handling by using the proxy servlet in an external web servlet container, such as IBM® WebSphere® Application Server or Apache Tomcat.
The proxy servlet is a Java™ servlet that produces the function of the broker HTTP listeners in an external web servlet container, such as WebSphere Application Server or Apache Tomcat. After the proxy servlet is deployed and running on the web servlet container, it uses the HTTP listener of the container to receive HTTP requests. If the web servlet container is configured to support SSL (HTTPS), web services requests are received by the message flows by using a secure communications protocol. For more information, see: HTTP proxy servlet; proxy servlet component
Components and configurations supported by the proxy servlet:
The following figures show the components and configurations that are supported by the proxy servlet, for descriptions of the components listed in these figures, see: HTTP proxy servlet; descriptions of required components
In the above figure the proxy servlet is running on the same server as the broker. The proxy servlet connects to the broker queue manager by using bindings mode (local connection) and the servlet is configured to access only HTTP nodes and therefore has been configured to access the HTTP nodes configuration file wsplugin6.conf.
In the above figure the proxy servlet is running on the same server as the broker. The proxy servlet connects to the broker queue manager by using bindings mode (local connection) and the servlet is configured to access only SOAP nodes and therefore has been configured to access the SOAP nodes configuration file soapplugin6.conf.
In the above figure the proxy servlet is running on a remote server to the broker. The proxy servlet connects to the broker queue manager by using client mode (remote connection) and the servlet can be configured to access HTTP or SOAP nodes and the HTTP or SOAP node configuration is retrieved from the SYSTEM.BROKER.WS.ACK queue.
In the above figure the proxy servlet is configured to load balance WebSphere MQ connections across multiple brokers. Network dispatchers or load balancers are required for this configuration to work.
When the proxy servlet is configured to connect to multiple brokers, the brokers must be identical clones of each other, which means that the same HTTP and SOAP flows are deployed with the same web addresses.
The proxy servlet sends the HTTP requests over the WebSphere MQ connections trying to distribute the load between the active broker connections.