The ABCs of AIA

A non-technical introduction to Oracles Application Integration Architecture A hit t Michael Butler Rolta TUSC
FLOAUG Annual Tech Event September 17-18 17-

Goals and Objectives

Integration O ti I t ti Options Optimal Integration Approach Overview of AIA Implementing AIA Getting Started Summary

Copyright 2009 by Rolta TUSC

Integration Options
I t Integration methods ti th d
Manual E-mail E il Flat File Point-to-Point Point to Point Web Services

Why havent things changed?

Age old conflict: doing it fast vs. doing it right

Typical Integration Architecture

Requesting Application

Responding Application

What Does That Lead To?

What is a better approach?

Trends in Software Integration

Increased use of Best of Breed applications is Best-of-Breed creating more and more integration points More packaged solutions means more upgrades p g pg and system interdependence Need for real-time analysis requires replacement of slower batch integration methods Constant quest for cost reductions requires q q maximum efficiency for system maintenance and new system development

Trends

(continued)

Greater complexity of integration scenarios (e.g. workflow orchestrations; real-time error handling that crosses application boundaries) Greater need for master data management

Overall Impact
Real time number of integration Real-time points complexity master data management issues = escalating cost and risk Constant opposing pressures Business need to upgrade/swap in best-of-breed vs. cost and risk

Optimal Integration Approach

What if you could

Maximize re use of business technology re-use components to minimize maintenance and development costs? Support the ability to use/swap-out applications to take advantage of best-ofbreed breed with the least risk to the applications environment (Applications Unlimited)? Create an environment that minimizes the cost and time of regression testing in support of upstream and downstream application changes?

What if you could

(continued)

Create an agile environment that can rapidly adapt to changing business and regulatory requirements? Evolve to this environment over time, with low risk?

How Do You Achieve It?

Establish a loosely coupled application loosely-coupled integration approach Adopt a strategy that allows the organization p gy g to evolve away from tightly-coupled point-topoint integrations rather than requiring a bigbang replacement effort Establish and leverage cross-industry standards where possible Build the integrations on an architecture that is application-neutral R Re-use i t integration components where possible ti t h ibl

How Do You Achieve It?

(continued)

Adopt an integration strategy that can address packaged software, custom legacy systems, as well as 3rd party applications Build a framework of re-usable features that are common to all integrations such as security and error handling Incorporate a robust testing scenario capability to ensure high-quality deployments Take advantage of off-the-shelf, pre-built integrations where possible

How Would You Build This?

Start with an application-neutral buffer zone application neutral Place industry-standard data models and business flows in the buffer zone Place an application neutral interface on each application-neutral side of the buffer zone Use connectors to link the buffer zone to each application Build the buffer zone on a service-oriented architecture

How Would You Build This?

(continued)

Keep track of all the integration components in a repository which makes them easy to find, re-use, and extend when needed Use the repository for impact analysis when a component needs to be changed Build an automated test system with built-in test cases that lets you validate that each component change has a benign affect on the existing integrations Build a framework that has built-in error handling and security

How Would This Look?

Start with an Application Neutral Buffer Zone

Add Industry-Standard Object Definitions & Business Flows

Add Translators for Each Application

Build It on an Application-Neutral Framework

Application-Neutral Buffer Zone

Requesting Application

Responding Application

Translator

Industry Standard Data Layouts and Business Flows

Translator

Service Oriented Architecture

Organize the Components in a Searchable Repository

Add Automated Testing Capability

Application-Neutral Buffer Zone

Requesting Application

Responding Application

Automated Testing Framework and Suite of Test Cases Repository

Translator

Industry Standard Data Layouts and Business Flows

Translator

Service Oriented Architecture

Add Infrastructure for Error Handling & Security

Application-Neutral Buffer Zone

Requesting Application

Responding Application

errorhandling & security

Automated Testing Framework and Suite of Test Cases Repository

errorhandling & security

Translator

error-handling & security

Industry Standard Data Layouts and Business Flows

error-handling & security

Translator

Service Oriented Architecture

Weve Just Described Oracles AIA

Application-Neutral A li ti N t l Buffer Zone

Requesting Application

Responding Application

ABM

ABM AIA Error Handling & Security

ABM

AIA Composite Application Validation System (CAVS) AIA Business Service Repository (BSR)

ABM AIA Error Handling & Security

Application Business Connector (ABC) Services

EBM AIA Error Handling & Security EBM

AIA Enterprise Business Objects/Services (EBO and EBS)

EBM AIA Error Handling & Security EBM

Application Business Connector (ABC) Services

Oracle SOA Suite

Overview of AIA
Terminology T i l Building Blocks Foundation Pack Pre-built Integrations Extensibility

AIA Terminology
Architecture Components Enterprise Business Objects (EBO) Enterprise Business Services (EBS) Application Business Connector Services (ABC) Enterprise Business Messages (EBM) Application Business Messages (ABM) B i Business Services Repository S i R it Composite Application Validation System

Start with an Application Neutral Buffer Zone

Enterprise objects & services based on industry standards

Application Business Connectors

Built on best-of-breed SOA infrastructure

Application-Neutral Buffer Zone Requesting Application
Responding Application

ABM

ABM

ABM

ABM

Application Business Connector (ABC) Services

EBM EBM

AIA Enterprise Business Objects/Services (EBO and EBS)

EBM EBM

Application Business Connector (ABC) Services

Oracle SOA Suite

Infrastructure for visibility, testing and error handling

Application-Neutral Application Neutral Buffer Zone Requesting Application
Responding Application

ABM

ABM AIA Error Handling & Security

ABM

AIA Composite Application Validation System (CAVS) AIA Business Service Repository (BSR)

ABM AIA Error Handling & Security

Application Business Connector (ABC) Services

EBM AIA Error Handling & Security EBM

AIA Enterprise Business Objects/Services (EBO and EBS)

EBM AIA Error Handling & Security EBM

Application Business Connector (ABC) Services

Oracle SOA Suite

Implementing AIA
Foundation Pack AIA infrastructure Toolkit for building your own AIA-compliant AIA compliant integrations Available in generic or industry-specific form Process Integration Pack (PIP) Pre-built collection of integration components Direct Integration (DI; industry-specific)

AIA Foundation Pack

AIA i f infrastructure t t
Pre-built Enterprise Business Objects (EBO)
Best-in-class data object definitions

Pre-built Enterprise Business Services (EBS)

Best-in-class web-service definitions for performing standard business tasks

Business Service Repository (BSR)

Visibility to all AIA integration components Facilitates impact analysis and component re-use

AIA Foundation Pack

(continued)

AIA infrastructure (continued) Composite Application Validation System (CAVS)

Testing framework End-to-end integration scenarios

Oracle AIA Common Error Handler Toolkit for building your own AIA-compliant integrations Available in standard or industry-specific form Communications, Insurance, and Utilities Cross-industry standard

Foundation Pack Components

Process Integration Pack (PIP)

Pre built integration between two Oracle Pre-built Enterprise Systems Built using Foundation Pack components g p Includes ABCs and ABMs for specific applications PIPs available f many integration for scenarios Oracle CRM On Demand to EBS Agile PLM to EBS Etc.

Foundation Pack + PIP

Foundation + PIP Components
Application-Neutral Buffer Zone Oracle Participating Application Oracle Participating Application

ABM

ABM AIA Error Handling & Security

ABM

AIA Composite Application Validation System (CAVS) AIA Business Service Repository (BSR)

ABM AIA Error Handling & Security

Application Business Connector (ABC) Services

EBM AIA Error Handling & Security EBM

AIA Enterprise Business Objects/Services (EBO and EBS)

EBM AIA Error Handling & Security EBM

Application Business Connector (ABC) Services

Oracle SOA Suite

Partial Hybrid PIP Use

AIA Extensibility
All AIA integration artifacts are user extensible user-extensible EBOs EBSs ABCs EBMs ABMs Extensions are stored separately Designed to survive upgrades

AIA Extensibility
Application-Neutral Buffer Zone

Requesting Application

Responding Application

ABM

Custom Exten nsions

ABM

Custom Exte ensions

ABM

ABM

AIA Composite Application Validation System (CAVS) AIA Business Service Repository (BSR)

Application Business Connector (ABC) Services Custom Extensions

EBM Custom Extensions EBM

AIA Enterprise Business Objects/Services (EBO and EBS) Custom Extensions Oracle SOA Suite

EBM Custom Extensions EBM

Application Business Connector (ABC) Services Custom Extensions

Getting Started
Identify integration scenarios that can be implemented quickly by leveraging the Foundation Pack components Pursue an evolutionary vs. big bang approach Start with a PIP if appropriate to get a head start on development

Get Started: Foundation Pack Proof of Concept

Install the AIA Foundation Pack and the Oracle SOA Suite Start small and design one integration scenario: g g
New or updated customer data in EBS is pushed to a CRM System

Use the AIA Enterprise Business Object (EBO) for customer Write the EBS-side ABC (that translates the EBS customer data to the EBO definition) and publish it to the AIA Business Services Repository Repository.

Get Started: Foundation Pack Proof of Concept

Write the CRM side ABC (that translates the CRM-side EBO definition to the custom CRM systems version of customer data) and publish it to the AIA Business Services Repository. Set up testing scenarios using the AIA Composite Application Validation System (CAVS) Insert/update customer data in EBS and it will be sent to the CRM system via AIA Test and put into production.

Value
Enables your applications to evolve and remain agile over time Provides the governance and tools to reduce g both costs and risks associated with crossapplication integration Increases as AIA becomes the enterprise enterprisewide standard and the multitude of point-topoint, tightly-coupled, possiblyundocumented, disparately-designed integrations are migrated to AIA

Summary
AIA addresses many of the key integration challenges facing organizations today AIA provides a world-class infrastructure for p building enterprise-wide, loosely coupled, reusable, scalable integrations Can be leveraged now for an evolutionary approach to establishing a SOA-based system integration platform AIA will be the standard architecture for future Oracle Fusion Applications

Contact Info:
www.tusc.com t Mike Butler: butlerm@tusc.com