3-2 Concepts and Technologies Guide for Oracle Application Integration Architecture
interface description is composed of all details required for a client to independently invoke the service.
These services expose coarse-grained, message-driven interfaces for the purpose of exchanging data between applications, both synchronously and asynchronously. The
request-specific and response-specific payload for each of the services is defined as an Enterprise Business Message EBM. The EBM typically contains one or several
instances of a single Enterprise Business Object EBO, which forms the crux of the message, the action to be performed, and the metadata about the message specified in
the message header section.
For more information see Section 2.2.1, EBM Architecture
. EBS components do not presuppose a specific back-end implementation of that
service. They simply provide an integration layer for your choice of a back end. Regardless of the choice, you can still achieve the seamless interaction experience in
the prebuilt integrations that are delivered by AIA. Any back-end implementations that can support the interface standards defined by an EBS can automatically be
considered as service providers.
For more information about EBS see Designing and Developing Enterprise Business Services in the Oracle Fusion Middleware Developers Guide for Oracle Application
Integration Architecture Foundation Pack.
3.2 EBS Operations
An operation is a unique action that has a specific payload and results in a clearly defined, repeatable outcome.
■
Each EBS contains multiple operations. A standard set of operations is defined for all Entity services. Additionally, each
Entity service may have one or more nonstandard operations.
■
Operations are categorized based on the Verb associated with the operation.
Every operation must have a Verb identified. The Verb helps to precisely define the scope, payload, and name of the operation.
■
An EBS may have synchronous and asynchronous versions of the same operation. By default, the behavior of a service operation synchronous or asynchronous is
predetermined by the Verb associated with the operation. For more information see
Section 3.3, Verbs .
AIA makes an explicit distinction between operations that can process a single instance of a payload versus operations that can process multiple instances of a
payload. Distinct operations are provided for both cases. Only the standard operations have this distinction implemented.
3.3 Verbs
Every operation has a Verb to identify the action to be performed by the operation. The concept of a verb was originally introduced by the Open Applications Group
Integration Specification OAGIS in their business object document BOD definitions and has been adopted with some modifications in the EBO definition.
Strictly speaking, the significance of a verb to identify the action to be performed by an operation is not applicable in a service-oriented web services environment because the
operation definition of a web service assumes this responsibility. However, not all
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
