WebSphere MQ server adapter processing

The processing associated with the WMQ server adapter depends on what is specified for the adapter service and what is passed in the message header from the service requester.

A WMQ PUT server adapter is always generated. The different types of PUT server adapter processing can be specified by the settings of the MsgType field in the WebSphere® MQ MQMD structure of the request message header. Depending on what value is specified, a WMQ GET server adapter might not be generated. See WebSphere MQ node (PUT) properties for details of the settings for the MsgType field.

If you specify a value of 2 for the MsgType field, the Navigator does not:

The WebSphere MQ-enabled application that is the target for the server adapter could be the service requester that issued the original request, or simply an application that performs some work as required as part of the server adapter processing. Whatever role the WebSphere MQ-enabled application plays, it does not need to issue any response to the server adapter. If the target application is the service requester, the MQPUT command from the server adapter would be considered an early reply to the request.

The CICS® Service Flow Runtime always issues a reply, even when an early reply has been sent from the PUT server adapter. This system reply message could contain only header information, but the application issuing the original request must account for this reply message and retrieve it from the queue. The Navigation Manager only issues replies if you are processing in asynchronous mode and the necessary fields are loaded in the DFHMAH structure.