Understanding Enterprise Business Services 3-3
integrations are using web services, and message-oriented integration scenarios still exist that may require the processing action to be identified within the message.
Verbs are also critical to define the semantics of the operation to be performed and to provide a consistent, unambiguous framework for naming operations and operation
payloads.
For more information about verbs and how to use them, see Constructing the ABCS in the Oracle Fusion Middleware Developers Guide for Oracle Application Integration
Architecture Foundation Pack.
3.4 EBS Types
AIA supports two categories of EBS, entity-based services and process-based services.
3.4.1 Entity Services
All of the standard activities that need to be performed using an EBO are brought together under an entity service. Hence, every EBO has a corresponding EBS, which
has definitions for performing standard activities such as Create, Update, Delete, Query, and so on. Sample EBSs include Customer, Party, Item, Sales Order, and
Installed Asset.
The standard activities in an entity-based EBS are:
■
Create To create an object instance
■
Update To update an object instance with only the changes that occurred
■
Delete To delete an object instance
■
Query To retrieve details about an object
■
Sync To send a current snap shot
Each of the activities uses the relevant EBM that represents the activity-specific view of the EBO as input and output.
Entity services expose operations that act on a specific EBO. Entity services have the following characteristics:
■
Each of the business object entities has a corresponding EBS; all of the actions that can be performed on this object are exposed as service operations and are part of
this EBS.
■
The entity operations consist of standard Create, Read, Update, and Delete CRUD operations that are similar across services as well as any specialized
operations that are specific to the EBO.
■
Entity services are implemented as Mediator routing services.
■
Entity services receive and return messages in the form of EBMs.
3-4 Concepts and Technologies Guide for Oracle Application Integration Architecture
■
Entity services leverage the context-based routing rules to delegate the request to the appropriate application-specific Application Business Connector Service
ABCS containing the actual implementation.
Figure 3–1 illustrates the EBS logical components and EBS physical implementation of
entity services.
Figure 3–1 Entity Services
3.4.2 Process Services
All of the business activities that need to act upon a particular business object to fulfill a specific business process are brought together under a process service. For example,
an EBS like OrderProcessOrchestration, Employee On Boarding might exist. The Employee On Boarding EBS might have operations such as Hire Employee, Terminate
Employee, and so on that you might not find in Person EBS.
These interfaces are described using an implementation-agnostic approach. For the interface to be application-independent, the EBS expects an EBM to be passed as the
input. In cases in which the EBS is expected to return a response, it sends a relevant EBM as the response. Hence, these interfaces are participating-application agnostic.
Process services expose operations related to an enterprise business process. Process services have the following characteristics:
■
Each EBF has a corresponding EBS; all of the actions that can be performed on this flow are exposed as service operations and are part of this EBS.
■
Process services are implemented as Mediator routing services.
■
Process services receive and return messages in the form of EBMs.
■
Operations exposed on the EBS initiate cross-functional Enterprise Business Flows EBFs that coordinate complex long-lived flows that span multiple services.
These flows can interact only with EBS services. This way both the Process EBS and the related business flows are completely application-agnostic.
Understanding Enterprise Business Services 3-5
■
Unlike Entity Services, a Process Service can act on more than one EBO. Figure 3–2
illustrates the EBS logical components for process services.
Figure 3–2 EBS Logical Components for Process Services
Figure 3–3 illustrates the EBS physical implementation of process services.
Figure 3–3 EBS Physical Implementation of Process Services
3.5 EBS Architecture
