This SupportPac contains the WebSphere MQ Service Definition specification which defines how to represent WebSphere MQ applications as Web services using IRIs and WSDL.
The WMQ Service Definition specification document and the related WMQ IRI specification document specify how WebSphere MQ (WMQ) applications should be described as services.
The documents cover five major areas:
- The IRI specification which defines the addresses of WMQ resources to be used by WMQ services (and other applications where a WMQ IRI is required).
- The properties that may be used to describe a WMQ application as a service.
- The MQI options that must be used to construct and interpret the SOAP and non-SOAP WMQ messages which communicate with a service.
- A set of examples illustrating the combinations of IRI's and service invocation messages.
- The WSDL binding that may be used to describe WMQ services
The main audience for these specifications are:
- The architects, authors, and administrators of WMQ applications who wish to catalogue their MQ assets in a standard way.
- The implementers of Web services stacks - who wish to extend a Web services stack with a WMQ message transport. These specifications will enable them to write a WMQ service implementation that will interoperate with other WMQ service implementations.
- Providers of Web services intermediary services such as routing gateways; or SOAP/HTTP to WMQ gateways. This specification does not discuss details of how such gateways should be designed and configured, but adherence to the standard will help the gateway ensure proper interoperation with WMQ clients and services.
The specifications define SOAP and non-SOAP WMQ bindings, and so can describe both traditional WMQ applications as services, and SOAP services which use WMQ as a transport.
The main purposes are:
- To allow MQ applications to be catalogued in a services registry such as the IBM WebSphere Service Registry and Repository.
- To ensure interoperability between different implementations of Web services tools that allow WMQ to be used as a Web services transport.
- To enable developers to implement their own WMQ services, and to have these interoperate with vendor provided Web services.
You can download a RedPaper for more information about using the WMQ Service Definition specifications . The RedPaper uses a scenario to show how the WMQ specifications can be used in conjunction with the WebSphere Message Broker (WMB), and WebSphere Service Registry and Repository (WSRR). It demonstrates how to describe two WMQ applications using WSDL, store those WSDL descriptions in WSRR, and then invoke the applications as HTTP services, via WMB with a dynamic endpoint lookup.
The RedPaper can be downloaded from : http://www.redbooks.ibm.com/abstracts/redp4350.html
Author: Mark Phillips, WebSphere MQ Strategy, Hursley
Current SupportPac Version: 1.0
»Please note that the version number shown in the right-hand pane is the version of the MQ or WBI product that this SupportPac applies to. The date is the last webpage refresh.
To view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|IRI Specification||30/11/2007||US English||255963||FTP|
|Service Definition||30/11/2007||US English||1198032||FTP|
Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels.
You may submit a question or offer feedback on the SupportPac but please be aware that a response is NOT guaranteed.