Daniel HefeleSoftware AG

wie Web Services und andere XML basierte Integrationsansätze effizientere System-Integration ermöglichen

XML und Integrationsaufgaben

2

Agenda

Allgemein

Web Services

XML Mediation

Q&A

3

Platforms

OS/390, VSE, BS2000, Unix,OS/400,OpenVMS, etc.

Data-Integration

Application-Integration

Process-Integration

Programatic-Integration

Configurable-Integration

Integration approaches

4

XML based Integration

Overcomes the challanges of traditional EAI

Uses open internal communication

Uses open standards (SOAP, WSDL, HTTP,XML,...)

Interacts/integrate via open interfaces (e.g. WS)

Provides quick Return on investment

5

XML Driven Integration

Current immature use of XML for integration

NOT just a data serialization format (integration projects still failing in large numbers).

NOT just a new data format.

NOT just replace SQL column name "Amt" with XML element "Amount"

6

XML driven integration

XML makes information more usable

XML provides context:

to legacy information so it can be used more effectively by other applications.

for integration rather than act as the interim carrier of information between systems.

XML defined data can be used to answer questions like:

"What does that amount mean to System A relative to System B?"

"What other systems contribute to the creation of this amount?"

7

Why XML as data format

XML makes Data portable, (Similar to Java, which makes Applications portable)

Yet the XML standard does not specify how to write programs to take advantage of all XML benefits

Web Services are the “Thought-, Programming-, and Architecture-Model” for XML

Web Services are the killer application for XML(similar to the Browser which was the killer application for the Internet)

8

XML as Integration Standard

Morgan Stanley CIO Survey, January 2002 (The survey yields a total of 225 responses from IT executives of the Fortune 1000.)

Over 70% of respondentsrate XML as strategic or very strategic as integration standard

60% of respondents areevaluating Web services

Gartner Group(Gartner Predicts 2002: What's Ahead for Software Infrastructure, January 2002)

... we believe that Web services will emerge, becoming unavoidable invaluable

By 2004, Web services will represent the dominant mode of deployment for new application solutions for Fortune 2000 companies (0.8 probability).

10%

19%

44%

27%

0% 5% 10% 15% 20% 25% 30% 35% 40% 45% 50%

Very strategic

Strategic

Not at allstrategic

Uncertain

How strategic is XML as integration standard for your organization?

9

Integration Costs - Traditional and SOI Solutions

Custom Integration

Traditional EAI. B2BiService-Oriented Integration

Rel

ati

ve

Co

sts

Initial Costs Configuration Maintenance Upgrades

Copyright © 2002 ZapThink, LLC

10

Impact of Web Services on EAI

What impact will Web services have on EAI software?

2%

Eliminate need

16%

Significantly reduce need

33%

Somewhat reduce need

Marginally impact need

24%

No impact on need

13%

2%

Eliminate need

12%

Don’t know

Note: 500 Respondent Source: 2002 Infoworld Application Integration Survey

11

Web Services

Web ServiceBroker

Web ServiceProviderUse Service based on

Service Description

SOAP

Publish Service DescriptionUDDI WSDL

Discover ServiceUDDI

Web ServiceRequester

Get Service Description

UDDI WSDL

Client Server

"Yellow pages"

12

Phases of Web Services Implementation

Phase I: Internal usage, improve application integration, 1st trusted partner integration

Phase II: Infrastructure for Web services, reposi-tory usage, combined service usage

Phase III: Dynamic service discovery and composition, internal and external usage

13

Web services & standards

Internet Protocols HTTP, TCP/IP, ...

Device-IndependentLanguage

XML

Message Deliveryacross the Internet

SOAP

Service Desc.& Discovery WSDL,UDDI

HighLevelAccessTo be

defined

Source: IDC 2002

e.g. WSFL, BPML4WS

14

What is XML Mediation?

Offers coupling of systems based on document exchange

Business rules based document routing and aggregation

External enterprise view through business documents

Partner independence regarding architecture and formats

Embraces open industry standards (XML, XSLT, HTTP, SMTP)

XML Mediation manages and controls the flow and behavior of XML document exchange

15

If both Checks are OK, Pass on for Approval

If Approved, extract information from order and enter data into Order Entry System

If both Checks are OK, Pass on for Approval

If Approved, extract information from order and enter data into Order Entry System

WHERE DOES IT GOForwarding: Rule-based Routing: To multiple targets

WHAT FORMATTransformation: Translate XML doc content and structure using XSLT style sheet

HOW IS IT TRANSPORTEDIntegration: Gateways to various systems (HTTP, SOAP, EntireX)

Combine response data from systems into one answer document

CONTENT HANDLINGReplication & Aggregation: combine multiple XML documents

Check customer’s credit

Check stock levels for order volume

DEFINE THE NEXT ACTIONSComposition: Build doc flow with SequencerLogging:Log and store fornon-repudiation

How does XML Mediation work?

What is it?

What do I do with it?

Where & who do I send it to?

Order comes in from the web

Verify type of order and validity of it

IDENTIFY THE DOCValidation: check XML documentsDiscovery: Inspection and extraction of XML document structure and data

16

Sequencer – Example

<sequence> <block on_error="errorsequence.xml"> <step component="SagLogger" logmessage="initial message object" /> <step component="SagEmerger" xbd.emerger.modelSourceURL="poemergermodel.xml" xbd.emerger.modelName="PurchaseOrder" /> <step component="SagLogger" logmessage="after emerger" /> <if property="private.name.present" relation="exists"> <block> ... </block> ... </block></sequence>

17

Sequencer – Statements

Traditional programming primitives if-then-else while switch Invoke

Mediator specific statements step replicate branch set, delete abort, reply on_error attribute

18

Sequencer – Visualization of Steps

Discover document attributes

Decision based on rules and attributes – direct approval/disapproval

Replication to keep original request document for later merging

Response document back to requester

Log request before it‘s processed

Back-end request processing, e.g. Workflow

Log request after it‘s been processed

Aggregation of back-end responses and original request document

A visualization of the earlier Order Entry

scenario

19

eMerger (1)

Creates message properties

Uses RDF-based rules

Rules are based on XPath statements

<sequence> ... <step component="SagEmerger" xbd.emerger.modelSourceURL="poemergermodel.xml" xbd.emerger.modelName="PurchaseOrder" /> ... Emerger

model name

Emerger definition (source)

20

eMerger (2)

<emergent-model rdf:ID='PurchaseOrder'><evaluates>

<rule rdf:ID='CheckForPO' /></evaluates>

<defines><rule rdf:ID='CheckForPO' >

<when>/purchaseOrder</when><then>

<rule rdf:ID='CheckCustomerInfo' /> </then>

</rule><rule rdf:ID='CheckCustomerInfo' >

<when>/purchaseOrder/customerInfo/name</when><then>

<property rdf:ID="private.name.present"><set-to>"true"</set-to>

</property> </then></rule>

</defines></emergent-model>

Emerger model name

Property name and value to be eMerged

XPath expression

Chained rule

21

Style Sheet Transformer

22

Aggregation

<aggregation rdf:ID='pomodel'> <produces> <document rdf:ID='pooutput' > <aggregate-of> <document rdf:ID='originaldoc' /> <document rdf:ID='custinfo' > <cut>/customerInfo/*</cut> <paste>/purchaseOrder/customerInfo</paste> </document> </aggregate-of> </document> </produces></aggregation>

Aggregation model name

Document ID

Cut and paste XPath expressions

23

XML Mediation: Go with the flow!

XML Document arrives through HTTPS gateway

XML Document arrives through HTTPS gateway

Send responseto sender

Send responseto sender

XML Document becomes a ‘Message’ and flows through a Sequence

XML Document becomes a ‘Message’ and flows through a Sequence

Parallel pathsand multiplecopies

Parallel pathsand multiplecopies

TransformationTransformation

Send e-mailswith an SMTPgateway

Send e-mailswith an SMTPgateway

Log and persist to Tamino

Log and persist to Tamino

Compile new documents

Compile new documents

24

XML Document

HTTP Client

Web Server with XML Mediator Code Base

XML Mediator HostExternal Systems

XML Mediator Codefor Host Execution

XML Mediator: A Web Services Application

XML Document

Easier maintenance of individual components

Components can be stopped and refreshed ‘on the fly’

Establishes a basis for a scalable, distributed architecture used to implement load balancing

GUITools

25

Existing EnterpriseApplications

CommunicatorXML Mediator

ServiceWrapperServiceWrapper

WebService

WebService

Standard

Apps.

Standard

Apps.

ServiceWrapperServiceWrapper

Gateway

T/F

Communication hub for distributed applications

Communication hub for distributed applications

XML document repository & management

XML document repository & management

XML document exchange management

XML document exchange management

26