Application Integration Architecture is the latest buzz word around companies who are integrating their legacy systems with Oracle products. Lets learn the basics of this technology and deleve deeper into this technology. We will take a look at the various PIPS offered by Oracle and look at an integration scenario where I will show you one integration. This forms the basics of other PIP Integrations.
Lets get started. To begin with lets learn the basics around AIA
1. Two or more applications are used for the integration. The source is called the Requester Participating Application and the Provider is the end application that provides the services for integration.
2. RequesterABCS - Application business connector server is the first point of contact for the requester application. Its a BPEL process which has the code that utilizes the Adapters to talk to database or other ERP systems. The ABCS also has code for validation,Transformation, Security and error handling.
3. ProviderABCS - The same logic applies for the ProviderABCS. It is a BPEL process which has the code that utilizes Adapters to talk to database or Other systems.
4. Now both the Request and provider needs to communicate in a protocol thats understandable by each other and thats where the EBS comes into picture. The EBS is the foundation block of AIA. They represent the application or implementation independent webservice definition for performing a business task. Each EBS contain multiple opreations each operation identified by a VERB. The VERB's usually define the CRUD operations on the routing service that resides on Oracle ESB that handles the message transporation between endpoints. The following are some of the documented CRUD verbs in AIA 2.5 - Create, Update, Delete, Query and Sync. Each activities uses the EBM that represents the activity as input and output. The EBS process services has filter conditions as to when and where the data needs to be routed based on the calling application rules.
5. Now the interesting part is the Data transformation. This code is usually handled in the BPEL process called the Impl Code. The transformation transforms data from ProviderABCS to RequestorABCS and call the ESB that routes the transformed data to the destination.
