APPLICATION INTEGRATION ARCHITECTURE CONCEPTS(INTEGRATION IS THE KEY)

EBM CONCEPTS :

->Structured XML message for message interchange between applications and services.
->Specific content of an EBO that is needed to perform specific activity
->EBM payload is restricted view of EBO content.It includes only the content that is necesary to perform the specific operation.
->EBM includes -header and data area.Header = message metadata.Dataarea=defines the action verb and contetnt payload.
->EBM messaging model is based on OPEN APPLICATIONS GROUP INTEGRATIONS ->SPECIFICATIONS,BUSINESS OBJECT DOCUMENT.

What is EBM header?

Tracking important information
Auditing
Source and target systems
Error handling

Contents of EBM metadata(header) :

EBMID,EBMName,EBOName,and CreationDatetime


EBM Data Area:

AIA verb: Create,update,delete,query(single),query(list)sync,validate,process

Payload :Complete EBO(Create),Unique identifier(delete) etc etc.


What is differenece between single and List EBM:

There are distinct operations and payloads for processing a single object as compare dto multiple instances.

Examples -
CreateSalesOrderEBM - processes single object
CreateSalesOrderListEBM- multiple instances of object

EBS(ENTERPRISE BUSINESS SERVICES):

They provide an integration to the customer's choice at backend.Simply they are routers.
They provide loose coupling of requesters and providers.
EBS are generally coarse grained and typically perform a business activity :creating account in billing system
Operate only on Application indepenedent cannonical objects.Deal with EBMS not ABMS.

Process are as follows (EBS):

EBS receives the message from calling application.
Sends the EBM to the appropriate ABCS.
ABCS transforms EBM to ABM and sends ABM to the praticipating applications.
After response comes back,EBS receives the response and returns EBM to the calling application

Responsibilities (EBS ):

Receive request from calling application
Evaluate the routing rules.
Identify the service provider
Enrich the EBM with service provider details.
Route the message to relevant service provider
Receive the response in request response pattern

 Advantage:

•Business driven

•Location Transparency

•Single purpose

•Loosely coupled

•Reusable

•Composable

•Standards based

•Technology neutral

 


EBS types :

1> Entity services :

Entity services expose operations that act on specific EBO.
Entity services are routed as mediator routing services.
Entity services receive and return messages in form of EBM'S.
Example entity EBS includes Customer,Party,ITEM,Sales.

2> Process Services:

Each enterprise business flow has enterprise business services.
EBF orachestrates multiple EBS to implement certain business function.EBF are not long running processes,they are short lived.
Process services are implemented as mediator.
Process services receive and return messages in form of EBM's.


EBO(ENTERPRISE BUSINESS OBJECTS)

-> Oracle has developed many standard objects and services called Enterprise Business Objects.
->AIA foundation pack provides standard Enterprise Business Repository where all the objects and services are stored.
->With AIA one can build own custom business process integrations

Components:

->A library of common objects and services
->A integration management infrastructure
->A proven methodology based on yrs of exp.
->Infrastructure components
->Prebuilt reference.

AIA advantages :

Minimize risk
Reduce costs
Application design and not technology.



What is PIP?

A PIP is a collection of multiple Pre-build processes based on Service Oriented Integration. It combines multiple services, applications, or systems