model driven legacy integration - OMG › news › meetings › workshops › WebServ... ·...

Model DrivenLegacy IntegrationTM

OMG Web Services Workshop 2003

Rüdiger Schilling, CEODelta Software Technology GmbH

[email protected]

Model Driven Legacy Integration © 2003 Delta Software Technology GmbH

Model Driven Legacy Integration

Overview

The Task

From MDA to MDLI

Generated PSM and Code

Tool Support

Summary



The Task


MDA™ Seminar Series Webcastby Richard Soley www.omg.org


!

MDA™ Seminar Series Webcastby Richard Soley www.omg.org


Func. Data

Model Driven Legacy IntegrationThe Task

RemoteApplications

LocalApplications

WebServiceApplications

??

??

Mission CriticalApplication Portfolio

InternetApplications

“Legacy”


Func. DataFunc. DataFunc. Data

Model Driven Legacy IntegrationThe Task

Func. Data


Mismatch ofFormatsGranularityBehaviour“Culture”


??Quality Aspects

PerformanceSecurityData Integrity

“Legacy”


The TaskMismatches to Overcome

FormatsMapping of data types and data formatsFlattening of groups, overlay structures and arraysVarious message formatsVarious middleware APIs

GranularityConventional function and call interfaces with coarse grain interfaces sometimes more than 100 KB per callFine grain OO interfaces set/get methods(R)DBMS interfaces with insufficient encapsulationNo single perfect interface"Multi-grain" interfaces for Web Services


The TaskMismatches to Overcome

BehaviourTransactions vs. sessions

Stateful servers vs. stateless clients and middle tier

Tightly vs. (very) loosely coupled systems

“Culture”Client developers and server developers (on legacy platforms) think in different concepts and languages

A Java programmer hardly accepts a bean that looks like COBOL …

… and vice versa


The TaskQuality Aspects to Observe

PerformanceMission critical, enterprise class applications with high transaction volumes

No impact on existing users of systems allowed

SecurityIntegration into existing security architectures

Auditing, Logging

Data IntegrityManaged access to data

No J/ODBC to production database



From MDA to MDLI


Platform Independent Model

Platform Specific Model

Multi-PlatformTransformation

PSM'

PSM

From MDA to MDLIMDA Transformation Pattern

PIM

PSM

Directto Code

AdditionalData etc.

Transformation

PSM

Transformation

AdditionalData etc.

Transformation (Mapping)Automatic, using generatorsOptionally controlled by additional data (marks, parameters etc.)

Different transformation conceptsTemplates, patterns ...Generator technology itself is not part of the standards process

Multi-platform transformation

Direct transformation

PIM/PSM to Code


Integration Model

??

From MDA to MDLIIntegration PIMs and PSMs (1)

ModelPSM

Implementation "System A"

Interface Model"System A"

PIM

Composition

Productionvia Generators

Runtime

Composition ModelInterfaces & Services

PIM

ModelPSM

Interface Model "System B"

PIM

Generated"Adapter A"Generated"Adapter A"

Generated"Adapter B"Generated"Adapter B"

PSMPSMAdapter

"B"Adapter

"B"

PSMPSMAdapter

"A"Adapter

"A"Implementation

"System B"

Mapping"A" "B"

Discovery

“Horizontal”integration

e.g. of two application

systems


Integration Model

??

From MDA to MDLIIntegration PIMs and PSMs (2)

ModelPSM

Legacy System Implementation

Interface ModelLegacy System

PIM

Composition

Productionvia Generators

Runtime

Composition ModelInterfaces & Services

PIM

Model (WSDL)PSM

Interface Model Web Services

PIM

Generated Proxy

Generated Proxy

PSMPSMAdaptive

ProxyAdaptive

ProxyWeb Services

Platform

GeneratedLegacy Adapter

GeneratedLegacy Adapter

PSMPSMLegacyAdapterLegacyAdapter

MappingFunction ⇔ Service

Discovery

“Vertical”integration

e.g of a legacysystem into aWeb Services

Platform

Alternativeapproach


From MDA to MDLI Platform Independent Integration Model

Based on OMG Standard EDOC-ECA/CCA

Enterprise Distributed Object ComputingEnterprise/Component Collaboration Architecture

That defines how“… classes, collaborations and activity graphs are used to modelat varying and mixed levels of granularitythe structure and behaviour of the components that comprise a (distributed) system … ”

Well suited for Integration PIMsService Oriented Architectures (SOAs), e.g. Web Services


From MDA to MDLI OMG-Standard EDOC-ECA/CCA

ECA as the normal form

EDOC-ECA

Web Services(WSDL)

ebXML(BPSS)

J2EE(Java RMI)

CORBA

MOM(MQ-Series)

The standard way to model and tool for multiple technologies

MDAMappings

Source: Data Access Technologies, Inc.


CustService

checkCustomer()checkCredit()

<<Interface>>

CheckCustomer(from OrderValidation)

<<ProtocolPort>>

checkOrder(from OrderValidation)

<<FlowPort>>

acceptOrder(from CheckCustomer)

<<FlowPort>>

Order(from BuySell)

<<CompositeData>>

OrderValidation<<ProcessComponent>>

OrderDenied<<CompositeData>>

reject(from OrderValidation)

<<FlowPort>>

<<initiates>>

<<responds>>

<<initiates>>

<<initiates>>

Order Validation Component

UML Class Diagram

CCA Notation

checkOrder

rejectacceptOrder

CheckCustomer

success failure

Order Validation Choreography

Choreography(Activity Diagram)

From MDA to MDLIEDOC-CCA Modelling of Components


From MDA to MDLIEDOC-CCA Modelling of Collaborations

Seller : Sells

Validate : OrderValidation

: checkOrder

: reject

: acceptOrder

: CheckCustomer

Process : OrderProcessing

: doOrder

: ProcessedOrder

CustBean : CustomerComponent

: SendOrder

: GetDenied

: GetConfirmation

: EnqStatus

Seller Composit ion

1: checkCustomer(order : Order)

UML CollaborationDiagram

CCA Notation


From MDA to MDLI Integration PIM – Contents

Interfaces of involved (legacy) components Methods or functions, parameters, data elementsData base structures – object based view

Composition of services to be providedPorts, protocols and messagesComponents, compositions and (external) interfacesChoreography:“… specifies the intended external behavior of a component …"

Mapping between encapsulated functions and servicesData elements and parametersInternal choreography: function calls, sequences, conditionsManaged access to data bases



GeneratedPSM and Code


Generated PSM and CodeMultiple Layers

“Separation of Concerns” by multiple layers

Adaptive ProxyClient representation of service

Technology AdapterTechnical transformationsConnection to middleware

Application AdapterTransformation from legacy architecture to service architectureParadigm mapping

Target Dev.Environment integrationDeployment dataLegacy Application

and Data Base

Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy

Client or Middle-TierApplication

Application Server, Middleware etc.

• Target dev.env.integration

• Deploymentdata


Generated PSM and CodeApplication Adapter

Mapping of service interfaces to legacy functionsMove data, activate functions, evaluate results

Object-relational mappingEncapsulated and managed access to data bases

Implementation of choreographiesFollowing application logicEnforce operation completeness and data integritySession logic vs. transactions

State managementDepending on server transaction logic and correlation of choreographies (external vs. internal)

Support different message versions at runtime

Legacy Applicationand Data Base

Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy




• Deploymentdata


Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy


Application Server, Middleware etc.Application Server, Middleware etc.


• Deploymentdata


Generated PSM and CodeTechnology Adapter

Transformation of formatsData types and structuresMessage formats and encoding

Pack and unpack compound messagesPre-fetch and cache management

Connection to MiddlewareCall and respondHandle events and exceptions

Connection to local operating systemPhysical transactionsWork space implementation for state management


Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy




• Deploymentdata


Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy




• Deploymentdata


Generated PSM and CodeAdaptive Proxy

Interfaces, Classes and MethodsGenerated as defined PIMJava, EJB, C#, C++ etc.

Opaque representation of serviceHiding legacy server and middleware

Acts like a class locally implemented and instantiatedNo specific data types, objects or operationsNo “culture clash” for client or middle-tier programmer

Seamless integration into target development environment

Deployment data as necessary


Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy




• Deploymentdata


Application Adapter

Technology Adapter

Technology Adapter

Adaptive Proxy




• Deploymentdata



Tool Support

SCORE®

Integration Suite


Tool SupportSCORE Integration Suite

RepositoryRepository

Composition

Discovery Prod

uctio

nIntegrated Development Platform


Tool SupportSCORE Integration Suite

Discover application function and parameters

Discover data store models and access paths

Discover external services with UDDI, WSDL, IDL …

Reuse existing modelelements (PIM + PSM)

Composition repository based on XML and MOF standards

Discovery

Transform PIM to platform-specific model (PSM) and from the PSM to source code

Client, middleware and server

Native code generation

New platform only a click away

Production

CompositionCreate and refine PIM

Interface rightsizing, operations, methods, data stores, data mapping, complex business rules …

Transformation attributes


Application Adapter

Legacy Function

Tool SupportProduction of Web Services

Java Proxy (Web Service)

Technology Adapter

Web Services Platform

Java Classes or EJBs generated as Web Services for WS Platform (incl. WSDL)

Running on the same or a remote platform (e.g. a Mainframe)

Web Service Client:Java, HTML, .Net, ...

e.g. Cape Clear 4 Server

Technology Adapter


Tool SupportFrom Legacy to Web Services

WSDLIntegration

Model(Composition)

SCORE Integration SuiteComposition Manager

Composition

LegacyInterfaces

Discovery Production

Java Proxy(Web Service)

Platform Toole.g. Cape Clear 4 Studio

Platform Toole.g. Cape Clear 4 Studio

Package and Deploy to Web Services Platform



Summary

Integration in MotionTM


Integration in MotionThe Task - Revisited

Func. Data

RemoteApplications

LocalApplications


??

??



“Legacy”


Integration in MotionAdaptive Services for Integration

Func. Data

RemoteApplications

LocalApplications



AdaptiveServices

Service-BasedIntegration Architecture


“Legacy”


Integration in MotionThree Aspects of Adaptive Services

Act intelligently

Focus on business needs

Manage technical details

Sessions, transactions, data mapping, object-relational, composite services and applications, business logic …

Service AgilityInterface Intelligence

Service QualityMission critical applications

Experience counts - creating tools, diverse platforms, large applications, real projects

Non-invasive integration, managed data access, audit, security, high performance …

Thrive in a changing world

Intelligently absorb changes

Ensure consistency

Interface definitions, merging, versioning, concurrent platform support …



More about Cape Clear 4www.capeclear.com

More about EDOC-CCA and toolswww.enterprise-component.com

All about Model Driven Legacy Integration

andSCORE Integration Suite

www.d-s-t-g.com

model driven legacy integration - OMG › news › meetings › workshops › WebServ... ·...

Documents

Transcript of model driven legacy integration - OMG › news › meetings › workshops › WebServ... ·...