The JNDI interface for the proxy servlet requires a one time setup of the WebSphere® Application Server full profile.
The proxy servlet initialization parameters must be configured for the integration node environment that the proxy servlet is connecting to each time the proxy servlet is deployed to the servlet container. It is now possible to configure the web.xml parameters only once through the JNDI in WebSphere Application Server, regardless of how many future deployments there might be of the proxy servlet. Because the JNDI configuration parameters take precedence over the initialization parameters in the web.xml file, using this method means that you need to set up at the application server side only once for any future deployments of the proxy servlet.
These setup tasks must all be completed in the WebSphere Application Server administrative console.
Name | Value | Description | Required |
---|---|---|---|
brokerName | RRB | Integration node Name | false |
configFilePath | C:\\Documents and Settings\\All Users.WINDOWS\\Application Data\\IBM®\\MQSI\\components\\RRB\\config\soapplugin6.conf | Configuration File Path | false |
clientModeChannelName | SYSTEM.DEF.SVR.CONN | Client Mode Channel Name | false |
clientModePortNumber | 2908 | Client Mode Port Number | false |
After you complete these tasks, you must deploy the proxyservlet.war file. During the deployment, you must provide the JNDI reference name for the Resource Environment reference that is defined in the web.xml file. For example: proxyservlet/reference/MQResourceReference.
After the deployment, proxyservlet gives precedence to the values configures in the Resource Environment Entries. If there is an environment change, the values must be modified in the custom properties of the Resource Environment Entries. After you modify a value, restart the Proxyservlet application in WebSphere Application Server for the new values to take effect.