Service MQ rules Completing the New or Save As form
About  New  Service  Request  Response  History  More...

Create a Service MQ rule by selecting Service MQ from the Integration-Services category.

Create a Service Package data instance before creating a Service MQ rule; the name of the service package becomes the first key part of a group of related Service MQ rules. The class and method name key parts are considered "external" and unrelated to PRPC class and methods, for flexibility.

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 PRPC class that the activity belongs to, but must be a valid Java identifier. See How to enter a Java identifier.
Customer Method Name	Enter a Java identifier that describes the PRPC activity being called. See How to enter a Java 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 MQ 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 MQ rules. The class hierarchy is not relevant to Service MQ rule resolution.

About Service MQ rules