Service JMS rules
Completing the New or Save As form

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.

A Service JMS rule has three key parts. The class and method name key parts are considered "external" and unrelated to Process Commander class and methods, for flexibility.

Field	Description
Type	Select Service JMS from the Integration-Services category.
Package Name	Select a package name that groups related Service JMS 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 Package Name value as key.
Customer Class Name	Enter 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 an identifier.
Customer Method Name	Enter an identifier that describes the Process Commander activity being called. See How to enter an identifier.

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.

Rule resolution

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.

About Service JMS rules