About Service JMS
rules
|
|
| New | Service | Request | Response | History | More... |
The JMS integration interface supports interactions between your Process Commander application and other systems through the Java Message Service (JMS). Process Commander supports JMS through both services and connectors. JMS services can receive (consume) messages from a JMS topic or queue and produce responses to those messages.
This facility supports both point-to-point and publish/subscribe messaging models. It supports durable subscriptions, automatic acknowledgment, and, if Process Commander is deployed as an enterprise application, transaction-based processing.
To provide a JMS service,
your Process Commander system must be able to function as a
JMS client. So if Process Commander is deployed on a
non-J2EE application server like Apache Tomcat, follow the
vendor's documentation for that application server and
configure the Process Commander system as a JMS client.
JMS services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured response while the calling application waits. However, you can configure JMS 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 JMS 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.
Use the Integration slice (
) to list the Service JMS rules in
your application. Use the Rules by Type Explorer to list all
the Service JMS rules available to you.
For a description of the development process, see the
following 
Pega Developer Network
articles:
Service JMS rules belong to the Integration-Services category. A Service JMS rule is an instance of the Rule-Service-JMS class.
|
How to unit test a Service JMS rule |
|
Atlas — Standard Service JMS rules |
Home