Service JMS rules - Completing the Create, Save As, or Specialization form
Create a Service JMS rule by selecting
Service JMS
from the
Integration-Services
category.
A Service JMS rule has three key parts:
| Field | Description |
| Customer Package Name | Select the name of the service package (instance of the Data-Admin-ServicePackage class); this service package is used to group related Service JMS rules. The service package must exist before you can create the service rule. See About Service Package data instances. If your application is to process requests from this service asynchronously through a background agent, define a Service Request Processor data instance ( Data-Admin-RequestProcessor-Service class) with this Customer Package Name value as key. |
| Customer Class Name | Enter the name of the service class. This is an arbitrary identifier to logically group related methods. This name need not refer to the Pega Platform class that the activity belongs to, but must be a valid Java identifier. See How to enter a Java identifier. |
| Identifier | Enter an identifier that describes the Pega Platform activity being called. See How to enter a Java identifier. |
Previous topic Service JMS rules Next topic Service JMS form - Completing the Service tab