WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

HTTP proxy servlet; servlet container component

The HTTP proxy servlet requires a number of components such as message flows, a proxy servlet, a servlet container, web addresses, the Broker component, and web services clients. Ensure that you are familiar with the servlet container component.

A Servlet container is the runtime environment for servlets and Java™ Server Pages (JSP). WebSphere® Application Server and Apache Tomcat are two examples of servlet containers (or web containers) that are available. The proxy servlet can be deployed in a local servlet container that is running on the same server as message broker or on a remote servlet container that is running on a remote server to message broker. The servlet container must allow the proxy servlet to configure and call the WebSphere MQ classes for Java.

The servlet container provides the SSL (HTTPS) listener support for web services applications. SSL must be configured and available in the container. The proxy servlet does not have to be configured for SSL but it enforces HTTP requests over SSL if the HTTP or SOAP input node is configured to use SSL.

When you have gained an understanding of the proxy servlet concept, read the following topics to help you install and test the HTTP proxy servlet:
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:35


Concept topicConcept topic | Version 8.0.0.7 | ac69360_