Interoperability

WebSphere MQ transport for SOAP does not guarantee interoperability between different host environments such as Apache Axis or .NET. This is because there are many different standards for SOAP and many implementations of SOAP environments, and it is those implementations that determine the specifics of each SOAP message. In addition, there are various different options for formatting the details of a service within a particular implementation (for example, RPC, DOC, or Literal). WebSphere MQ transport for SOAP delivers the message content, but cannot ensure that the content is meaningful to the service that receives it.

It is the responsibility of the service provider or developer to identify the SOAP implementations within which the service is to be supported and to ensure that the formatting style is compatible with those implementations. This process is, however, independent from WebSphere MQ; when interoperability is established over HTTP, then it will also be established if WebSphere MQ transport for SOAP is used in place of HTTP.

There are preferred SOAP options for interoperability as defined by the WebServices Interoperability group (WSI, http://www.ws-i.org/). The samples provided with SOAP/WebSphere MQ reflect these options.

WebSphere MQ transport for SOAP uses the same message and URI formats as WebSphere Application Server (WAS) and CICS and so allows interoperability with those products. The message format is described in and the URI format in Specifying the URI. For more information, see Interoperation with WebSphere Application Server and Interoperation with CICS.