Service CORBA
rules
|
Create a service package data instance before creating a Service CORBA rule; the name of this data instance becomes the first key part of a collection of Service CORBA rules.
A Service CORBA 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.
For example, a service that is already exported and deployed on a client computer may be changed to call a different Process Commander activity. Because the external representation has not changed, and the IDL file hasn't changed, you do not need to redeploy and modify the application code on the client computer.
Field |
Description |
Type |
Select |
Customer Package Name |
Select a package name that groups related Service CORBA rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances. |
Customer Class Name |
Enter a name to logically group related methods. This name may or may not refer to the Process Commander class that the activity belongs to. Enter a value that is a valid Java identifier. See How to enter an identifier. |
Customer Method Name |
Enter a name that describes the Process Commander activity that the service calls. This is not a Process Commander method or a Java method, but must be a valid Java identifier. 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.
When searching for a Service CORBA 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 CORBA rules. The class hierarchy is not relevant to Service CORBA rule resolution.