Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 358

The preceding sequence is based on the custom DB model we presented earlier. However,
every entity can be presented as an OER asset or expressed using tModels in OSR. The
concrete Business Process ( 8 ) will be extracted as an XML Execution Plan in Look-
upService using the DB adapter.
1. First, the atomic entity is a Trading Partner, representing the application/service
with concrete Endpoint and Endpoints Service Contract. The TP role could be a
Sender or Receiver.
2. The TP application is a logic that handles objects, including business objects. All
business objects must be registered as Business Entities.
3. Event reflects the change in an object, so we have to maintain a Registry for all
the business events.
4. TP, Object, and Event are the key elements of the message identification (via
Message Header), and message payload is an EBO carrying a business object.
5. Composition participant, controller, subcontroller, and service providers (TP) per-
form tasks, expressed as service/components operations. Tasks' activities are
based on service engines capabilities and controlled by parameters. Message-re-
lated tasks, such as translation or transformation, will require registering
message-processing XML artifacts (XSLT, XQuery, Xpath as tModels, artifacts,
or references to the file location).
6. All operations are governed by the rules, starting from events recognition (busi-
ness/nonbusiness or basic/complex) to message routing and composition control-
ler activities. Rules are combined in rulesets and based on tasks. Rule collections
are the essence of the policies.
7. Process can be defined as a tasks assembly. In this step, we define it as an abstract
process, describing business context, rules, and conditions.
8. Process, associated with TP/Endpoints, is a business process and can be presented
as an Execution Plan, or an individual SCA, depending on factors we discussed
earlier. A completely descriptive process must be registered as a service for
runtime/design-time discovery and dynamic invocation.