Upload
rawmalu
View
227
Download
0
Embed Size (px)
Citation preview
8/3/2019 AIA Concepts
1/19
Pearson Copyright 2009
Application Integration Architecture (AIA)Concepts
Infrastructure Group
8/3/2019 AIA Concepts
2/19
Pearson Copyright 2009
AIA
Oracle AIA delivers a service-oriented foundation for adaptive integration of
applications using Oracle Fusion Middleware.
Oracles development organization relies on this architecture to implement
pre-built Process Integration Packs (PIPs) for a number of industry-specific,
out-of-the-box integrations between applications in Oracles portfolio as wellas third party applications.
Pearson can leverage concepts and best practices used in AIA
development to integrate its own applications like TPI, SMS etc.
8/3/2019 AIA Concepts
3/19
Pearson Copyright 2009
AIA Overview
8/3/2019 AIA Concepts
4/19
Pearson Copyright 2009
AIA Terminology
Enterprise Business Objects (EBO) are application independent
representations of key business entities.
Enterprise Business Services (EBS) that implement the required operations
on the EBO.
Application Business Connector Service (ABCS) that expose application
functionality in a canonical format. Common Error Handling & Resolution, a centralized approach to error
handling across applications, technologies and integration patterns.
Composite Application Validation System (CAVS) which enables integration
testing without the deployed participating applications in place.
8/3/2019 AIA Concepts
5/19
Pearson Copyright 2009
Enterprise Business Objects (EBO)
EBOs provide a canonical business language (XML Schema) for
information integration.
Supports the loose coupling of systems in AIA by eliminating the need for
one-to-one mappings of the disparate data schemas between each set of
systems.
Using an EBO means that you map each application data schema only
once to the EBO canonical data model.
Extensible to fit customer specific needs.
Based on OAGIS data models with Oracle customizations.
Examples Worker, Item, Sales Order objects etc.
8/3/2019 AIA Concepts
6/19
Pearson Copyright 2009
The EBO Advantage
CRM ERP
Billing Shipping
Enterprise Business Object
(Customer Object)
CRM ERP
Billing Shipping
Traditional Architecture AIA Architecture
8/3/2019 AIA Concepts
7/19
Pearson Copyright 2009
EBO Potential Pearson Usage
IMS schemas (person, management. group) serve same purpose as EBOs.
Establish centralized schema layer independent of the service layer.
Schema upgrades can be more easily handled with schema centralizationrather than modifying every project.
Consider using OAGIS schema definitions for objects outside IMS scope.
8/3/2019 AIA Concepts
8/19
Pearson Copyright 2009
Enterprise Business Service (EBS)
An EBS is an application agnostic service interface definition.
Facilitates loose-coupling between the requester and provider
Provides service mediation and content based routing
EBS service operations are typically CRUD operations implemented as a
light weight mediator component.
8/3/2019 AIA Concepts
9/19
Pearson Copyright 2009
EBS Mediation Layer
8/3/2019 AIA Concepts
10/19
Pearson Copyright 2009
EBS Potential Pearson Usage
Use mediation layer concept versus point to point tightly coupled web
services.
Mediation reduces need to rebuild integrations as you bring newapplications into the mix or upgrade to newer versions.
Consider schema centralization pattern for WSDLs instead of including
them in every project.
8/3/2019 AIA Concepts
11/19
Pearson Copyright 2009
Application Business Connector Service
(ABCS)
The ABCS is an application specific artifact in AIA that acts as the glue
between the EBS and a participating application that needs to be integrated.
A Provider ABCS would typically expect messages in a canonical format
and then transform this to the specific application business message (ABM)
format.
A Requestor ABCS would accept ABMs as input and transform them into
canonicals before invoking an EBS.
Although a single ABC service can be used to handle multiple activities,
Oracle recommends allowing only a single ABC service per action.
Typically leverages the VETO (validate, enrich, transform, operate) pattern.
8/3/2019 AIA Concepts
12/19
Pearson Copyright 2009
Implementation Example
8/3/2019 AIA Concepts
13/19
Pearson Copyright 2009
ABCS Potential Pearson Usage
Consider modularizing CRUD operations into different BPEL processes.
CreateUserABCS can be modified without affecting UpdateUserABCS.
New processes (for example DeleteUserABCS) can be plugged in withoutdowntime for the existing Create/Update processes.
8/3/2019 AIA Concepts
14/19
Pearson Copyright 2009
Example AIA Integration
8/3/2019 AIA Concepts
15/19
Pearson Copyright 2009
Common Error Handling (EH)
Provides a consistent and unified approach irrespective of the type of
service the error occurs in I.e. OSB or BPEL.
Errors trigger notifications issued to actor roles based on error type.
Triggers a human workflow where comments can be added, and status on
errors can be updated, and closed.
Error Logging The framework logs messages in a consistent schema in a
non-intrusive manner.
8/3/2019 AIA Concepts
16/19
Pearson Copyright 2009
EH Potential Pearson Usage
Common Async error handling process which is invoked by all processes
when an error occurs.
Common error message format populated by all processes.
Design time configuration to decide notification recipient based on error (eg.Send all TPI errors to role X with an FYI to role Y).
Common process could also initiate an human task in workflow.
TBD if OEM based error handling is sufficient or a more powerful solutionneeded.
8/3/2019 AIA Concepts
17/19
Pearson Copyright 2009
AIA Naming Conventions
Standard naming convention used throughout framework.
An ABCS would be named as
For example, a BPEL component implementing a create user operation for
TPI would be named: All namespaces follow the following pattern:
8/3/2019 AIA Concepts
18/19
Pearson Copyright 2009
Enterprise Registry
TBD
8/3/2019 AIA Concepts
19/19
Pearson Copyright 2009
Summary
Use the centralized schema pattern for XSD and WSDL documents formaximum reusability and ensuring smooth upgrades.
Ensure design is hot pluggable- so you have the ability to replace as well asadd service providers/ requestors with no disruption to other components.
Ensure design is application independent- this means that it will work withapplications that you use now and may use in the future.
Ensure design provides open standards support.