Service EJB rules
|
|
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 may copy data instances but they do not support specialization as they are not versioned.
Based on your use case, the Create, Save As, or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields
This
NOTE: Create a Service Package data instance before creating a Service EJB rule; the name of the Service Package data instance is the first key part of a collection of Service EJB rules.
Create a Service EJB rule by selecting Service EJB
from the Integration-Services
category.
A Service EJB 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 is an arbitrary text value that is a Java identifier, not an instance of the Rule-Obj-Class class. The service package name and service class name group service rules. See How to enter a Java identifier. |
Identifier |
Enter the name of the service method. This name is an arbitrary identifier; it is not related to a Rule-Method instance. The service method named describes what the service rule does. See How to enter a Java identifier. |
When searching for a Service EJB 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 EJB rules. The class hierarchy is not relevant to Service EJB rule resolution.