Service BPEL rules
|
|
Important: The rule type Rule-Service-BPEL is deprecated. As appropriate, migrate to Service SOAP 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: Before you create a Service BPEL rule, create the Service SOAP rules and Connect SOAP rules that implement the operations for the BPEL process.
Create a Service BPEL rule by selecting Service BPEL from the Integration-Services category.
A Service BPEL rule has two key parts:
Field |
Description |
| Service Package | Select the service package of the appropriate Service SOAP rules. The service package and service class together identify the Service SOAP rules to be included in this Service BPEL rule. |
| Service Class (Port Type) |
Select the service class of the appropriate Service SOAP rules. This field also identifies the Connect SOAP rules for the Service BPEL rule: those rules for which the Namespace field contains the same value as the one specified in this Service Class (Port Type) field are included in the Service BPEL rule. Enter a Service Class value that is a valid Java identifier. See How to enter a Java identifier. |
When searching for a Service BPEL 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 BPEL rules. The class hierarchy is not relevant to Service BPEL rule resolution.