Use a package of Service MQ rules to let external systems and users access the Pega 7 Platform data and processing using the IBM WebSphere MQ middleware messaging standard. Each Service MQ rule identifies an activity providing the service. The external system passes an MQ message to the Pega 7 Platform, which runs the activity and then may return an output MQ message.
When the Pega 7 Platform is deployed as an enterprise application, you must use a message-driven bean (MDB) as the listener for message-based service rules (JMS and MQ). As a result, although you can use WebSphere MQ as a JMS service provider, use JMS MDB listeners with JMS service rules, rather than MQ listeners with MQ service rules, when the Pega 7 Platform is deployed as an enterprise application.
MQ services generally process service requests synchronously. That is, they immediately perform the requested processing and return a configured response while the calling application waits. However, you can configure MQ services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous MQ services to check for specific error conditions that you expect will be temporary — work item locks, for example — and then queue service requests that fail for those reasons for another attempt at a later time.
For information about creating MQ services, see the following PDN articles:
Use the Application Explorer to see Service MQ rules in your application. Use the Records Explorer to list all Service MQ rules that are available to you.
Service MQ rules belong to the Integration-Services category. A Service MQ rule is an instance of the Rule-Service-MQ rule type.
|
|
Unit testing a Service MQ rule |
|
|
Standard Service MQ rules |
Integration-Services category