Service MQ rules - Completing the Create, Save As, or Specialization form
Service MQ rules - Completing the Create, Save As, or Specialization form
Create a Service MQ rule by selecting
Service MQ
from the
Integration-Services
category.
A Service MQ rule has three key parts:
Field | Description |
Customer Package Name | Select the name of a service package (instance of the Data-Admin-ServicePackage class); this package groups related Service MQ rules. Choose a name already defined through a Service Package data instance. 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 a class name to logically group related methods. This name may or may 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 a Java identifier that describes the Pega Platform activity being called. See How to enter a Java identifier. |
Previous topic Service MQ rules Next topic Unit testing a Service MQ rule