An MQ Service defines the interaction
between IBM® Integration Bus and WebSphere MQ applications. You can create an MQ Service for each queue manager. An MQ Service
definition is created for each MQ Service that you discover, and has the
extension .service. The MQ Service
definition specification describes the
resources that you discover. This specification also explains how
to represent WebSphere MQ applications as web services
by using IRIs and WSDL. For more information, see 
SupportPac MA93: WebSphere MQ - Service Definition
specification.
You can use an MQ Service to configure the properties of an MQ node. You can reuse an MQ Service across multiple MQ nodes, which simplifies the MQ connectivity within your message flows.
An MQ Service contains:
- A WSDL file that contains connection information about the Queue Manager and resulting Queue names. The WSDL file is compliant with the IBM MQ Service definition specification (MA93).
- An XSD file for the input message, and an XSD file for the output message, if any are specified in the MQ Service editor. The XSD files contain XML structures that describe service input and output.
- An XML file that contains metadata that is used during the discovery process. The IBM Integration Toolkit uses this file to store state information from the MQ Service editor, and perform iterative discovery of previously discovered artifacts.
To create an MQ Service, complete
the following actions in the MQ Service editor:
- Connect to a local or remote queue manager. The MQ Service editor connects to the specified queue manager, either locally or remotely, to discover all the existing queues that belong to it.
- Define whether the MQ Service is one-way or request-response.
- Identify the queue or queues that you need, depending on whether the MQ Service is one-way or response-request.
Last updated Friday, 21 July 2017