Configuring CICS to use the WebSphere MQ transport
To use the WebSphere® MQ transport with SOAP web services in CICS®, you must configure your CICS region accordingly.
About this task
Note: You cannot use the Websphere MQ transport for JSON
web services.
Procedure
- Include the WebSphere MQ library thlqual.SCSQAUTH in the STEPLIB concatenation in your CICS procedure. Include the library after the CICS libraries to ensure that the correct code is used. thlqual is the high-level qualifier for the WebSphere MQ libraries.
- Include the following WebSphere MQ libraries in
the DFHRPL concatenation in your CICS procedure.
Include the libraries after the CICS libraries
to ensure that the correct code is used.
- thlqual.SCSQCICS
- thlqual.SCSQLOAD
- thlqual.SCSQAUTH
- Install an MQCONN resource for the CICS region. The MQCONN resource specifies the attributes of the connection between CICS and WebSphere MQ, including the name of the default WebSphere MQ queue manager or queue-sharing group for the connection. For more information, see Setting up an MQCONN resource.
- Specify the CICS system initialization parameter MQCONN=YES to start the CICS-WebSphere MQ connection automatically at CICS initialization. For details, see MQCONN system initialization parameter.
- If you are using the CICS-WebSphere MQ adapter in a CICS system that has interregion communication (IRC) to remote CICS systems, ensure that the IRC facility is OPEN before you start the adapter, by specifying the CICS system initialization parameter IRCSTRT=YES. The IRC facility must be OPEN if the IRC access method is defined as cross-memory; that is, ACCESSMETHOD(XM).
- Ensure that the coded character set identifiers (CCSIDs) used by your queue manager and by CICS, and the UTF-8 and UTF-16 code pages are configured to z/OS® conversion services. The CICS code page is specified in the LOCALCCSID system initialization parameter.
- Update your CICS CSD as follows:
- If you do not share your CSD with earlier releases of CICS, remove the groups CSQCAT1 and CSQCKB, and any copies of those groups or of items from those groups, from your CSD. You must also delete the CKQQ TDQUEUE from group CSQCAT1. The definition for CKQQ is now supplied in the CICS CSD group DFHDCTG.
- If you do share your CSD with earlier CICS releases, ensure that CSQCAT1 and CSQCKB, and any copies of those groups or of their content, are not installed for CICS TS 4.1 or CICS TS 3.2. You must also delete the CKQQ TDQUEUE from group CSQCAT1. The definition for CKQQ is now supplied in the CICS CSD group DFHDCTG. For CICS TS releases earlier than CICS TS 3.2, install the CSQCAT1 and CSQCKB groups as part of a group list, after installing DFHLIST, to override group DFHMQ and correctly install the required definitions.
- Update the WebSphere MQ definitions for the dead-letter queue, default transmission queue, and CICS-WebSphere MQ adapter objects. You can use the sample CSQ4INYG, but you might need to change the initiation queue name to match the default initiation queue name in the MQINI resource definition for your CICS region. You can use this member in the CSQINP2 DD concatenation of the queue manager startup procedure, or you can use it as input to the COMMAND function of the CSQUTIL utility to issue the required DEFINE commands. Using the CSQUTIL utility is preferable because you do not then have to redefine these objects each time that you restart WebSphere MQ.
- The WebSphere MQ transport
CICS can receive and send SOAP messages to WebSphere MQ using the WebSphere MQ transport, both in the role of service provider and service requester. - Defining local queues in a service provider
To use the WebSphere MQ transport in a service provider, you must define one or more local queues that store request messages until they are processed, and one trigger process that specifies the CICS transaction that will process the request messages. - Defining local queues in a service requester
When you use the WebSphere MQ transport for outbound requests in a service requester, you can specify in the URI for the target web service that your responses should be returned on a predefined reply queue. If you do so, you must define each reply queue with a QLOCAL object. - The URI for the IBM MQ transport
When communication between the service requester and service provider uses IBM MQ, the URI of the target is in a form that identifies the target as a queue and includes information to specify how the request and response should be handled by IBM MQ. - Configuring CICS to support persistent messages
CICS provides support for sending persistent messages using the WebSphere MQ transport protocol to a web service provider application that is deployed in a CICS region. - Persistent message processing
When a web service request is received in a WebSphere MQ persistent message, CICS creates a unique BTS process with the process type DFHMQSOA. Data relating to the inbound request is captured in BTS data-containers that are associated with the process.
dfhws_configureMQ.html |
Last updated: Sunday, 4 June 2017