Start of change

The WebSphere MQ transport

CICS® can receive and send SOAP messages to WebSphere® MQ (WMQ) using the WMQ transport, both in the role of service provider and service requester.

As a service provider, CICS uses WMQ triggering to process SOAP messages from an application queue. Triggering works by using an initiation queue and local queues. A local (application) queue definition includes: When a message arrives on the local queue, the Queue Manager generates and sends a trigger message to the specified initiation queue. The trigger message includes the information from the process definition. The trigger monitor retrieves the trigger message from the initiation queue and schedules the CPIL transaction to start processing the messages on the local queue. For more information about triggering, see the WebSphere MQ Application Guide.

You can configure CICS, so that when a message arrives on a local queue, the trigger monitor (provided by WMQ) schedules the CPIL transaction to process the messages on the local queue and drive the CICS SOAP pipeline to process the SOAP messages on the queue.

Start of changeWhen CICS constructs a response to a SOAP message that is received from Websphere MQ, the correlation id field is populated with the message id of the input message, unless the report option MQRO_PASS_CORREL_ID has been set. If this report option has been set, the correlation id is propagated from the input message to the response.End of change

As a service requester, on outbound requests you can specify that the responses for the target Web service should be returned on a particular reply queue.

In both cases, CICS and WMQ require configuration to define the necessary resources and queues.

End of change