Service JMS rules
Completing the New or Save As form
|
|
Create a Service JMS rule by selecting
Service JMS from the
Integration-Services category.
Create a Service Package data instance before creating a Service JMS rule; the name of the service package becomes the first key part of a group of related Service JMS rules. The class and method name key parts are considered "external" and unrelated to Process Commander class and methods, for flexibility.
A Service JMS rule has three key parts:
Field |
Description |
| Customer Package Name |
|
| 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 Process Commander class that the activity belongs to, but must be a valid Java identifier. See How to enter a Java identifier. BUG-1604 |
| Customer Method Name |
Enter an identifier that describes the Process Commander activity being called. See How to enter a Java identifier. BUG-1604 |
For general information about the New form, see Completing the new rule dialog box. For general information on the Save As form, see How to enter rule keys using Save As.
When searching for a Service JMS rule, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions.
Circumstance-qualified and time-qualified resolution features are not available for Service JMS rules. The class hierarchy is not relevant to Service JMS rule resolution.
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