See information about the latest product version
Configuring the proxy servlet
Configure the proxy servlet with the initialization parameters that are used by the proxy servlet. These parameters need to be configured for the broker environment that the proxy servlet is connecting to before the proxy servlet can be deployed to the servlet container.
The configuration of the proxy servlet is done by editing the Web Deployment Descriptor web.xml file that is packaged in the compressed proxyservlet.war (WAR) file. The WAR file can be found in the following directory:
<WMB_runtime_install_path>/tools.
You can either use the WebSphere Message Broker toolkit to edit the Web Deployment Descriptor web.xml file, or you can extract the proxyservlet.war file, find the web.xml file and edit it using an appropriate editor, such as Notepad. Both procedures are described in this section:
- To configure the Web Deployment Descriptor web.xml file by using the WebSphere Message Broker toolkit, start the toolkit, and switch to the Java™ EE perspective.
- Click Web section, select WAR file in the list, and click Next. , expand the
- Click Browse to find the WAR file in <WMB_runtime_install_path>/tools. Where <WMB_runtime_install_path> specifies the name of your runtime installation path. For example, in C:\Program Files\IBM\MQSI\8.0\tools\proxyservlet.war.
- Set the name of the Web Project to proxyservlet.
- Click Finish. The proxy servlet is now ready for configuring by using the Java EE perspective.
- Expand proxyservlet in the Project Explorer view and double-click Deployment Descriptor to view the Web Deployment Descriptor.
- Find the Servlets and JSPs section in the Web Deployment Descriptor, and click the servlet link called WBIMBServlet to display the servlet web address mappings and initialization parameters. The same parameters in the web.xml file can be configured through JNDI in WebSphere Application Server. This alternative method means that you set up at the application server side only once for any future deployment of the proxy servlet. This operation is possible because the JNDI configuration parameters take precedence over the initialization parameters in the web.xml file. For more information about setting up the JNDI interface for the proxy servlet, see Setting up the JNDI interface for the proxy servlet
- Click the Source tab, which is found at the bottom of the Web Deployment Descriptor view. You might need to click >> (Show List) to see the Source tab option. The source of the Web Deployment Descriptor web.xml displays the proxy servlet parameters.
- Edit the proxy servlet parameters with initialization parameters; see: Proxy servlet configuration parameters For information about typical deployment scenarios, see Example proxy servlet configuration scenarios.
- When the configuration is complete, save the changes to the Deployment Descriptor web.xml file by pressing Ctrl S.
- Export the configured proxy servlet ready for deployment to Tomcat. Click Web section, select WAR file in the list, and click Next. , expand the
- Click Browse, specify a location for the configured WAR file, enter WAR file name HTTPVSR1BKproxyserlet.war, and click Save.
- Enter the Web module name proxyservlet, and click Finish. You have now configured the proxy servlet by using the WebSphere Message Broker toolkit.
To configure the Web Deployment Descriptor web.xml file directly, find and extract the proxyservlet.war file, find the web.xml file in the extracted contents, right-click the web.xml file, and select an appropriate editor, such as Notepad to edit the web.xml file with initialization parameters specified at: Proxy servlet configuration parameters.
You have now configured the proxy servlet with the initialization parameters.
In order that the proxy servlet can access the SOAPInput and SOAPReply nodes, you must enable the broker-wide listener for each execution group where message flows with SOAP nodes are deployed. See HTTP listeners and Switching from embedded listeners to a broker-wide listener.