About Connect MQ rules
Use Connect MQ rules to define connector interfaces that use the IBM WebSphere MQ messaging standard. The interface uses two MQ message queues, one for the outgoing message and one for the incoming message.
If you configured an alias queue for Connect MQ rules in earlier versions of Pega Platform, after a upgrade to Pega Platform 8.6, Connect MQ rules do not work. To resolve this issue, create the following dynamic system settings and set the corresponding default values:
- "mq/pmo" = 0
- "mq/gmo" = 0
- "mq/oo_request" = 1040
- "mq/oo_response" = 16
For more information, see Creating a dynamic system setting.
Pega supports Websphere MQ versions up to and including version 9.
The following tabs are available on this form:
To list the Connect MQ rules in your application, use the Application Explorer or click.
To list all Connect MQ rules that are available to you, use the Records Explorer.
This service can use the IBM MQ-CICS Bridge to work with applications that use the IBM Customer Information and Control System. For example, a flow can call a legacy IBM customer master file based on CICS to verify an account number or update a balance.
Each Connect MQ rule references an MQ Server data instance, which defines how Pega Platform finds and connects to a WebSphere MQ server.
See Creating JMS and MQ Connectors on the Pega Community, for a step-by-step instructions on developing and testing Connect MQ rules.
To debug your application, you can simulate an MQ connector when the external system is unavailable or lacks a test environment. See Creating Connector Simulations.
Connect MQ rules can be referenced in an Integrator shape of a flow rule.
A Connect MQ rule is an instance of the Rule-Connect-MQ rule type. Connect MQ rules belong to the Integration-Connectors category.