About Service MQ
rules
|
|
| New | Service | Request | Response | History | More... |
Use a package of Service MQ rules to let external systems and users access Process Commander 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 Process Commander, which runs the activity and then may return an output MQ message.
When
Process Commander 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 Process Commander 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 object 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, Pega Developer
Network articles 
PRKB-25074 Using
the Service Accelerator. See also:
Use the Integration slice (
) to list the Service MQ rules in your
application. Use the Rules by Type Explorer to list all the
Service MQ rules 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.
|
message-driven bean |
|
Unit testing a Service MQ rule |
|
Atlas — Standard Service MQ rules |
Home