Service Gateway for WMQ is a Message Oriented Middleware (MOM) application containing several shared tools.You use it to create, send, receive, and process messages in a network of WebSphere MQ-enabled TIBCO Object Service Broker and non-TIBCO Object Service Broker applications. This message processing can take place across supported platforms.
The interface between the rules and WebSphere MQ is controlled by the internal @MOMMAP map table and the corresponding MOM-specific table, for example, @MQSMAP. This is set up by the @MOMINIT shareable tool.
Only one MOM environment can be active in any one session at a time. The environment is owned by the transaction issuing the @MOMINIT call. The environment can be shared only with transactions executed by that transaction. You do this by passing @MOMMAP_ADDRESS.
TIBCO Service Gateway for WMQ is TCB-specific. Therefore @MOMINIT sets TCB affinity for the transaction. This means an interpreter TCB is held for the duration of the transaction. In a multi-user Execution Environment, this can require you to increase the TASKEXECNUM Execution Environment parameter.
TIBCO Object Service Broker Parameters for details on the TASKEXECNUM Execution Environment parameter.
The return code and reason code from the MOM software are stored in the map table @MQSMAP which is a shareable tool. You can check these stored codes in your rules. Refer to @MQSMAP in
TIBCO Object Service Broker Shareable Tools for more information about this tool.
The following rule moves all the messages from one queue to another. In this rule, @MOMBUFFER is a MAP table set up by the writer of the rule to describe the data being written.