SAP XI - Interoperability with EAI Products · SAP AG 2002, SAP XI Interoperability withother EAI...

SAP Exchange Infrastructure

SAP XI - Interoperabilitywith EAI Products

SAP AG

SAP AG 2002, SAP XI Interoperability with other EAI vendors, Wolfgang Fassnacht 2

Introduction

Interoperability Options

Summary


XI in a Nutshell

The SAP Exchange Infrastructure is an integration platformFor SAP and non-SAP applicationsFor A2A and B2B communicationFor Business Process ManagementBased on industry and Web services standards

XI XI

BPMBPM

RoutingRouting MappingMappingAppAppApp/BP

App/BP

Adap-ter

Adap-ter AppApp

App/BP

App/BP

IntegrationBuilder

IntegrationBuilder

Moni-toringMoni-toring


Key Principles of SAP Exchange Infrastructure

Shared integration knowledgePre-packed integration content delivered with SAP solutionsFor a common understanding of how collaborative processes work

OpennessIntegration of SAP and non-SAP applications via adaptersStrict usage of standards

Loose coupling via XML messagingAsynchronous communication as far as possibleSynchronous communication where required

FlexibilityAdoption of scenarios by configuration – no coding requiredAllows easy and non-disruptive addition of new services and

processesLower TCO

Centralized design, configuration, execution and monitoringXI comes as integral part of SAP NetWeaver


SAP Applications Using XI

More and more SAP applications are making use of SAP Exchange Infrastructure and introducing XI to a customerlandscape. The following applications now use XI:

xApps (such as xRPM, Resource and Program Management)MDM (SAP Master Data Management)SRM (SAP Supplier Relationship Management)SCM (SAP Supply Chain Management)BI (SAP Business Intelligence, for Global Spending Reporting)R/3 Enterprise (for Industry Standard Support)CRM (SAP Customer Relationship Management, for Extended Order Management)SBO (SAP Business One)


Situation in Customer Landscapes

There are various reasons for installing SAP Exchange Infrastructure is installed at a customer´s site:

The customer has chosen XI as his strategic integration solution.An SAP solution is introduced to a system landscape and dependson functionality which is provided by XI.

In certain cases the customer already has an EAI product (forexample, from BEA, IBM, Microsoft, SeeBeyond, Tibco, Vitria etc.) in place when XI is installed. This can happen when

Different country organizations or divisions within a group usedifferent integration solutions.A company has used another integration solution until now.A group buys a new company which relies on different softwareproducts.


Two Integration Solutions in One System Landscape

In all the above-mentioned cases it is necessary for different integration solutions to interact. So the question is:How does XI interoperate with EAI products?

RuntimeServer of

other vendor?SAP XIIntegration

Server


Introduction


Summary


Option 1: Exchange of Metadata

IntegrationRepositoryIntegrationRepository

IntegrationDirectory

IntegrationDirectory

ConfigurationDesign

System Landscape DirectorySystem Landscape Directory

Shared CollaborationKnowledge

Exchange of Files (WSDL,

BPEL etc.)

The SAP Exchange Infrastructurestrictly uses open standards for itsShared Collaboration Knowledge.

SAP XI allows you to export und import metadata, which are storedwithin the Integration Repository.

This applies with minor restrictionsto:

Interface descriptions (WSDL)Business Process descriptions(BPEL)

So as a first option an interoperability of SAP XI with EAI products can be supported throughthe exchange of metadata.


Three Ways to Interoperate on a Messaging Level

There are three XI adapters that are ideally suited to interoperatingout-of-the-box with the runtime environment of other integrationsolutions.

There are therefore three ways to interoperate:Via JMS (Java Messaging Service)Via SOAP (Simple Object Access Protocol)Via HTTP (Hypertext Transfer Protocol) or

HTTPS (Hypertext Transfer Protocol over Secure Socket Layer)


Option 2: Interoperability Via JMS Adapter

The JMS Adapter connects JMS enabled messaging systems to the Integration Server. The advantages are:

Secure asynchronous delivery

Connection to all JMS enabled messaging systems (such as MQSeries or Sonic MQ)

JMSAdapter

JMSAdapter

SOAP withattachmentsand headerextensions„XI Protocol“SAP XI

IntegrationServer Runtime

Server withnative JMScapabilities

or

Networkprotocol

JMS enabledmessagingsystem Runtime

Server ofother

vendor

Networkprotocol


XI Java Messaging Service (JMS) Adapter

Supported Features

XI messaging (message parsing and serialization, guaranteeddelivery)

Technical transformation

Services (centralized configuration, monitoring and errorhandling)

The JMS Adapter allows bi-directional messaging (access to and from connected systems)

Supported Quality of Service in Messaging

Guaranteed exactly once delivery (EO)

Guaranteed exactly once in order delivery (EOIO)


Option 3: Interoperability Via SOAP

SOAP withattachmentsand headerextensions(„XI Protocol“)

RuntimeServer of

other vendorSOAP

AdapterSOAP

AdapterSAP XI

IntegrationServer

The SOAP adapter allows connectivity via SOAP protocol.

Advantages:Secure synchronous delivery

Secure asynchronous delivery (requires guaranteed messagingcapability)

SOAP


XI SOAP Adapter

Supported FeaturesThe SOAP adapter enables the exchange of SOAP messagesbetween the Integration Server and remote clients or providers of Web Services. The SOAP inbound adapter runs on the Integration Server. You canconfigure and maintain the SOAP outbound adapter on theIntegration Server or on another host.The SOAP adapter allows bi-directional messaging (access to and from connected systems)

Supported Quality of Service in MessagingBest effort delivery (BE)Guaranteed exactly once delivery (EO) (if appropriate parameters aretransferred in the URL or in the message header)


Option 4: Interoperability Via HTTP(S)

The HTTP Adapter allows connectivity via HTTP(S) protocol.

Advantages:Secure synchronous delivery

Secure asynchronous delivery (requires guaranteed messagingcapability)

SOAP withattachmentsand headerextensions(„XI Protocol“)

HTTPAdapterHTTP

Adapter

SAP XIIntegration

Server

RuntimeServer of

other vendor

HTTP(S)


XI "Plain HTTP" Adapter

Supported FeaturesThe plain HTTP adapter enables application systems to communicate with the Integration Server and to exchange business data via HTTP without a SOAP envelope around the HTTP payload (plain HTTP). The external systems are connected using the Internet Communication Framework of the SAP Web Application Server.The plain HTTP adapter allows bi-directional messaging (access to and from connected systems).You can send the payload in HTML form using HTTP post. Thepayload is enhanced correspondingly.

Supported Quality of Service in MessagingBest effort delivery (BE)Guaranteed exactly once delivery (EO) (if appropriate parameters aretransferred in the URL or in the message header)


Introduction


Summary


Several interoperability options

The interoperability of the SAP Exchange Infrastructure and EAI products can be supported on the one hand through the exchangeof metadata using open standards.

On the other hand XI provides adapters that enable out-of-the-boxinteroperability between SAP XI and the runtime environment of other EAI products.

A secure asynchronous and synchronous exchange of messages isguaranteed.Various features (such as bi-directional messaging) and different Qualities of Services are supported.

All these interoperability options apply to EAI products such as BEA WebLogic Integration, IBM Websphere Business Integrator, Microsoft Biztalk, SeeBeyond E*gate Integrator, Tibco ActiveEnterprise, Vitria BusinessWare etc.


Copyright 2002 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.

SAP XI - Interoperability with EAI Products · SAP AG 2002, SAP XI Interoperability withother EAI...

Documents

Transcript of SAP XI - Interoperability with EAI Products · SAP AG 2002, SAP XI Interoperability withother EAI...