Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.
Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This information identifies the key parts and options that apply to the record type that you are creating.
Create a Service Package data instance before creating a Service Java rule; the name of the service package is the first key part of a collection of Service Java rules.
Create a Service Java rule by selecting Service Java from the Integration-Services category.
A Service Java rule has three key parts:
Field |
Description |
| Customer Package Name |
Select the name of the service package (instance of the Data-Admin-ServicePackage class). The service package must exist before you can create the service rule. 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 the name of the service class. This name is an arbitrary identifier; it is not an instance of Rule-Obj-Class but must be a valid Java identifier. See How to enter a Java identifier. The service package name and service class name group service rules. |
|
Identifier |
Enter an identifier for the service method. This name is a string; it is not an instance of the Rule-Method class. The service method named describes what the service rule does. See How to enter a Java identifier. |
When searching for a Service Java 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 Java rules. The class hierarchy is not relevant to Service Java rule resolution.