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.
Because Service Gateway for WMQ is packaged as an external routine, it must have routine and argument table entries. To create these entries, if you did not do so at installation time, make sure you are using a level‑7 TIBCO Object Service Broker user ID and then run the @MOMSETUP rule.
The interface between the rules and the WebSphere MQ software is controlled by the internal @MOMMAP map table and the corresponding MOM-specific table, for example, @MQSMAP_PORT. This is set up by the @MOMINIT shareable tool.
Prior to an @MOM... call, you must define a local variable called @MOMMAP_ADDRESS, to be available to all subsequent @MOM... calls.
Only one WebSphere MQ 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.
The return code and reason code from WebSphere MQ are stored in the map table; refer to @MQSMAP in
TIBCO Object Service Broker Shareable Tools for more information about this table.You can check these codes in your rules.
The rule that follows 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.