' LENMAR ' power adapter, for nokia electronic

Two main reasons for Application System Integration To connect between the existing application systems  A typical Fortune 1000 company has many Mission Critical Application Systems 

Ove rvie w of Applic ation

Adapte r Te c hnology

Ke nne th Baik

April 10, 2003 ECE1770 - Expe rt To pic

Age nda

 Main reasons for EAI

 Primary objective of Application Adapter

 Typical Issues with Adapter

 Basic Functions of Adapter

 Adapter Methodology

 One of Adapter Technologies

Application System Integration

Heterogeneous Platforms ERP Systems

Two main reasons for Application System Integration

 To connect between the existing application systems

 A typical Fortune 1000 company has many Mission Critical Application Systems

 A typical large enterprise has more than 5000 major

application systems

 These systems are logically interconnected

 Corporate information is scattered in disparate and

heterogeneous application systems These application systems are called “Legacy” systems.

 Approximately 70% of corporate data resides on legacy hosts, such as mainframe and AS/400 platform

 Therefore, the most of enterprises have a mandate to integrate

Two main reasons for Application System Integration

 To connect the existing application systems with new

application systems on new platform such as Web application systems

 As the Internet gets more attention from business sectors, the requirements of connecting the legacy systems to the Web

application systems arise to the surface

 Rewriting a legacy system into Web application system does not make sense financially and technically

 There are too many risks for mission critical applications

 To provide a means of exchange for business information

flowing between business partners, legacy systems and Web application systems must be integrated.

Core component of EAI Products

 The requirement for communication between

disparate and heterogeneous application systems leads to development of Enterprise Application Integration products

 A core component of this is “Adapter”

“Application Adapter” is one of the core components of EAI product !

Definition of Adapter

depending on the context and the application architecture

objective is to facilitate integration of the application for which it has been designed

Developing an Adapter

adapters, each exposing a subset of the application

functionality

time-consuming

SAP and Siebel, off-the-shelf adapters are available that integrate the packaged application to the integration

backbone with little or no coding effort

for which such ready-made adapters are not available

development

Typical Issues with an Adapter

Many EAI vendors build an application adapter for a specific client and later package it as a product The design of such an adapter could have the following limitations:

 Limited functionality: “First customer” specific customizations and shortcuts render it ineffective in a different scenario

 Version tie-in: Tie-in to a specific version of the packaged

application (ie PeopleSoft 7, PeopleSoft 8, SAP R/3, etc.) implies substantial additional effort whenever the application version is

Basic Functions of Adapter

 When two independently written application systems

communicate each other, their datasets between two systems

do not match Therefore, there is a need for message

transformation between the originator and the recipient

 A source adapter transforms the source message to a common form while a target adapter changes the common form to that required by the recipient

 The transformed data in the source application has to be

transferred to the target application system by specific protocol such as FTP, HTTP, HTTPS, SMTP, etc

Basic Functions of Adapter

Application1

EIS

Document Specification (API)

Document Specification (API)

Data Mapping

Data Mapping

Integration-ready Appl system

 For an application system to be integration-ready, there are two requirements

 One is to isolate and expose its different points of

integration A point of integration could be a specific database table, a specific business function or a stored procedure

 The other is to isolate the integration logic from the application’s business logic, interface and database

layers In a three-tiered application architecture, the user interface, business logic and database layers each encapsulate specific application functionality

Adapter Design Methodology

 Adapters are one way for developers to isolate an application’s integration logic However,

application adapters use application-specific APIs and this is not ideal as access mechanisms, since the API will most likely be different for most

applications

 So, platform-neutral standards such as XML,

SOAP (Simple Object Access Protocol) and J2EE (the Java 2 platform, Enterprise Edition) are ideal building blocks for developers to design adapters

One of Adapter Technologies

data between two heterogeneous systems through an XML interface

 BizTalk Server Supports

and other protocols

 Mapping Between Document Formats

 Programmable Interfaces for Submitting and Receiving Documents and for Administration

 Content-Based Routing of Documents

BizTalk Server Messaging Tools

 BizTalk Editor

 BizTalk Mapper

 BizTalk Messaging Manager

map for data transformation

 BizTalk Administration Tool

BizTalk Server Group

SMTP

HTTP

FTP MSMQ

SNA

File System

DCOM

EDI IIS

Management Desk

BizTalk Editor

Channel Manager

XXX XXX

Tools

Data

XXX XXX

XML PO

SAP IDOC

Schema Editor

Channel

Channel Editor

BizTalk Mapper

Port Manager

Schema Mapper

XSL Map Port

Port Editor

BizTalk Server Group

SMTP

HTTP

FTP MSMQ

SNA Server

File System

DCOM

Management Desk

BizTalk Editor

Pipeline Manager

XXX XXX

Tools

Data

XML PO

SAP IDOC

Schema Editor

Channel

Channel Editor

BizTalk Mapper

Agreement Manager

Schema Mapper

XSL Map Port

Port Editor

Messaging Service Decrypt/Decode Parse Select Pipeline

XXX XXX

XML PO

Decrypt/Decode Parse Select Channel

SAP R/3

XML PO2

Document Interchange Example

Management Desk

BizTalk Editor

Pipeline Manager

SAP IDOC

Schema Editor

Channel

Channel Editor

BizTalk Mapper

Agreement Manager

Schema Mapper

XSL

Port Editor

External

Application

Interne

XML PO

Channel

XSL Transform Serialize to IDOC SAP Integration Component

SAP

XSL Transform Serialize to IDOC SAP Integration Component

SAP IDOC

3

Document Interchange Example

Simple Demo

 Middleware is software that sits between the back-end or database tier and the front-end or presentation tier of an application Various types of middleware perform

functions such as data access, messaging, data aggregation, data integration, and transaction management

 Application Adapter is an Integration Middleware that is used for process integration or data integration and

aggregation.

Que s tio ns

?