Interoperation with WebSphere Application Server

To allow SOAP/WebSphere MQ to interoperate with WAS, an APAR has to be applied to WAS. The APAR depends on the version of WAS you have installed:

Deployment of a SOAP/WebSphere MQ Web service using the supplied deployment utility generates appropriate WSDL and a URI for a standard WAS client to use directly: the only special requirement is that 'nojndi.jar' be in the classpath of the WAS client at runtime.

Normal deployment of a WAS/SOAP/JMS Web service will generate WSDL and a URI that includes JNDI (Java Naming and Directory Interface) references. WebSphere MQ transport for SOAP does not use a JNDI, whereas WAS/SOAP/JMS and other SOAP/JMS implementations generally do. To make the service available to SOAP/WebSphere MQ does not require any change to the runtime, but does require the extension of the WSDL to include a 'pure MQ' binding with a JNDI-free URI (see the description of the initialContextFactory in Specifying the URI). This binding may be a replacement for or addition to the standard JNDI-dependent binding. You must write your own deployment process to generate this new WSDL and URI.