See information about the latest product version
Installing the proxy servlet
The installation of the proxy servlet is made up of a number of tasks. Use this topic to complete each of the tasks to then move onto testing the proxy servlet.
The proxy servlet proxyservlet.war (WAR) file is part of the runtime environment in WebSphere Message Broker Version 6.1 Fix Pack 3 (6.1.0.3) and above, and can be found in the following directory:
WMB61_runtime_installation_path/tools. Where WMB61_runtime_installation_path specifies the name of your runtime installation directory.
Supported operating systems
The proxy servlet runs on any operating system that is supported by the servlet container. The documentation in this section describes the installation on Windows, but the proxy servlet can be installed on other operating systems.
Prerequisites
- WebSphere Message Broker Version 7.0 or later.
- A supported version of WebSphere MQ. For the latest details of all supported levels of hardware and software, visit the WebSphere Message Broker Requirements website.
- A servlet container and web server, such as WebSphere Application Server Version 6, or Apache Tomcat Version 6.
To install the proxy servlet:
- Install and customize a web servlet container, such as WebSphere Application Server or Apache Tomcat. For more information, see Installing and customizing a web servlet container for the proxy servlet.
- Configure the proxy servlet with the initialization parameters that are used by the proxy servlet. For more information, see Configuring the proxy servlet.
- Enable the broker-wide listener for each execution group where message flows with SOAP nodes are deployed, so that the proxy servlet can access the SOAPInput and SOAPReply nodes. See HTTP listeners and Switching from embedded listeners to a broker-wide listener.
- Deploy the proxy servlet in the web servlet container. For more information, see Deploying the proxy servlet in a web servlet container.
You are now ready to test the proxy servlet. For information about how to complete this task, see Testing the proxy servlet.