What is AIA?
Oracle´s Application Integration Architecture
is an open standards based
solution that allows customers to create loosely coupled end to end business
processes across their applications, which can be continually modified and
optimized over time. The key thing here
is that it works between Oracle applications as well as non-Oracle apps.
AIA helps reduce some
of the major SOA implementation challenges associated with the complexity of the
architecture, building business connections, messaging and exception services, metadata
fragmentation, designing canonical data models and data transformation.
AIA Implementations
come in two flavors:
•
Foundation Pack – mostly used to integrate
non-Oracle applications, the Foundation Pack
consists of a SOA Toolkit with pre-built artefacts, including pre-defined best practice design patterns, utility services, templates & code samples. It provides for a consistent business and developer framework including guidelines and SOA governance pre-defined policies.
consists of a SOA Toolkit with pre-built artefacts, including pre-defined best practice design patterns, utility services, templates & code samples. It provides for a consistent business and developer framework including guidelines and SOA governance pre-defined policies.
•
Process Integration Packs (PIPs), mostly used to integrate Oracle Applications,
PIPs are composed of pre-built Oracle Applications process integrations, out of
the box, for quick implementation of
business processes (i.e. Siebel CRM to Oracle E-Business Suite)
AIA Terminology
•
Enterprise
Business Service (EBS)
–
These are
application-agnostic web services that are used by calling applications to
interface with different applications. This helps the cross-application
processes to be participating-application unaware. The EBM containing the
canonical object is the payload of the enterprise service and contains
business-specific messages.
•
Enterprise
Business Object (EBO)
–
EBOs
provide a shared semantic framework for applications to communicate through a
standard business data object definition used in the canonical data model. Enterprise business
objects contain components that satisfy the requirements of business objects
from participating application data models. Together with EBSs, they provide an
application-independent representation of key business components.
•
Enterprise
Business Message (EBM)
–
The EBM is
the payload that is paired to an EBS. The response returned by the EBS will
also be an EBM.
•
Enterprise
Business Flow (EBF)
–
EBF is a
cross-functional Business Process Execution Language (BPEL) flow used to coordinate
the flow of a single EBS operation that is complex, potentially long-lived, and
spans multiple services. These flows only interact with EBSs to keep them
agnostic of participating applications.
•
Application Business Connector Service (ABC
Service)
–
The name
for APIs developed to transform application business objects into enterprise
business objects, and vice versa. Components of this service include the ABC
implementation service and the ABC interface service.
Hi Friends,
ReplyDeleteOracle application integration architecture is the most complete integration solution for orchestrating agile, user-centric business processes across your enterprise applications. It contains very informative matter. I would like to come here again. This type of posting should go on.