1. SAP Exchange Infrastructure
Dr. Sven Leukert
Product Manager, SAP AG

2. SAP NetWeaver and SAP XI
SAP XI Overview

3. Today’s Integration Challenge
Document Mgmt
Integration costs are high
Lots of heterogeneous systems
Long integration projects
IT environments become increasingly rigid
Pressure on IT increases
Must leverage existing investments
Must show quick results
Must reduce total cost of ownership (TCO)
Market Analysis
Call Center
SCM
ERP
Trading
e-Sales
Technical systems
E-Procurement
PLM

4. How to Lower TCO Reduce complexity Reduce custom integration
Document Mgmt
Reduce complexity
Minimize the number of connections - using hubs
Use only 1 platform to integrate all people, information, and systems
Reduce custom integration
Deliver .NET and J2EE interoperability
Deliver adaptors for ISV products
Deliver products, not projects!
Increase company performance
Increase ease of use, scalability and adaptability
Increase business process flexibility by using an Enterprise Services Architecture
Market Analysis
Call Center
SCM
ERP
Trading
e-Sales
Technical systems
E-Procurement
PLM

5. SAP NetWeaver™ The total integration and application platform for lower TCO
Unifies and aligns people, information and business processes
Integrates across technologies and organizational boundaries
A safe choice with full .NET and J2EE interoperability
The business foundation for SAP and partners
Powers business-ready solutions that reduce custom integration
It’s Enterprise Services Architecture increases business process flexibility
SAP NetWeaver™
Composite Application Framework
People Integration
Life Cycle Management
Multi-Channel Access
Portal
Collaboration
Information Integration
Business Intelligence
Knowledge Management
Master Data Management
Process Integration
Integration Broker
Business Process Management
Application Platform
J2EE
ABAP
DB and OS Abstraction
DB and OS Abstraction …
.NET
WebSphere

6. SAP Solutions Powered by SAP NetWeaver™ Open integration on all levels for the mySAP Business Suite
SAP R/3 Enterprise
mySAP SRM
mySAP SCM
SAP NetWeaver
People Integration
Strategic Sourcing
Multi-Channel Access Portal Collaboration
Information Integration
Knowledge Mgmt Business Intelligence Master Data Mgmt
Process Integration
Integration Broker, Business Process Mgmt
Demand/
Source of Supply
Supplier Evaluation
Application Platform
J2EE ABAP, DB and OS Abstraction
R/3
SRM Backbone
SCM Backbone
3rd party Solution

7. SAP xApp Resource and Program Mgmt
SAP Solutions Powered by SAP NetWeaver™ Orchestrating new, cross-functional business processes
SAP NetWeaver
SAP xApps
People Integration
Multi-Channel Access Portal Collaboration
SAP xApp Resource and Program Mgmt
Project Portfolio Mgmt
Project Execution
Staffing Resource Assignmt
Advanced Skills
Mgmt
Information Integration
Knowledge Mgmt Business Intelligence Master Data Mgmt
Process Integration
Integration Broker, Business Process Mgmt
Application Platform
J2EE ABAP, DB and OS Abstraction
PLM
3rd party HR
Project System
Microsoft Office
3rd party FI

8. SAP NetWeaver in Detail
SAP Mobile Infrastructure
Tight coupling and alignment with SAP business solutions
SAP Enterprise Portal
Business packages
Collaboration
SAP Business Information Warehouse
Business content
Open architecture (Crystal, Ascential)
Master Data Management
Coming in 2003
SAP Exchange Infrastructure
Proxy generation and mapping tools
Integration directory
SAP Web Application Server
Proven, scalable, comprehensive toolsets
Leverage existing infrastructure/skillsets
DB and OS Abstraction
People Integration
Composite Application Framework
Process Integration
Integration Broker
Business Process Management
Information Integration
Business Intelligence
Knowledge Management
Life Cycle Management
Portal
Collaboration
J2EE
ABAP
Application Platform
Multi-Channel Access
SAP NetWeaver™
Master Data Management
Integration Broker
Business Process Management
Business Intelligence
Knowledge Management
Portal
Collaboration
J2EE
ABAP
Multi-Channel Access
DB and OS Abstraction
Master Data Management

9. SAP NetWeaver and SAP XI
SAP XI Overview

10. The Solution – Key Design Elements
Web services
Application functions become Web services
Self-contained, modularized functionality that can be described, published, discovered, and accessed through open internet standards
In addition, all kinds of services that are relevant for „classical EAI and remote communication“ (via adapters)
Open syndication of Web services
Regardless of location
Web-centric Architecture
XML and message based infrastructure for open collaboration supporting open standards and leveraging Java, ABAP and .Net
Central Integration Repository and Directory capturing shared Collaboration knowledge
Open for mySAP.com e-business solutions and 3rd party components
All customer touchpoints based on open XML and Java technology

11. The Solution – Shared Business Semantics
Shared Integration Knowledge
Business scenarios, business processes, Web services, interfaces, mappings, routing rules, ...
For a common understanding of how collaborative business processes work
Enabling distributed execution
Shared classification and discovery of businesses and services
Support for UDDI (Universal Description, Discovery and Integration)
Lose coupling via XML messaging
Asynchronous communication as far as possible
Synchronous communication where required
Evolution
Allow easy and non-disruptive addition of new services and processes
Integration of existing and new SAP components
Integration of existing customer and 3rd party components

12. Overview Exchange Infrastructure 2.0
Share d
Collaboration
Execute Collaborative
Knowledge
Business Processes 3 rd
Party and
Messaging Systems D
esign C
onfigur
ation
Runtime
SAP Systems
Integration Server
Integration Server
Integration Engine
Integration
Integration
Integration
Integration
Business
Additional
Marketplaces
Process
Integration
Repository
Repository
Directory
Directory
Engine
Services
SOAP
Plain HTTP
Partner Eco -
System
System Landscape Directory
System Landscape Directory
Runtime Workbench
(additional 3rd Party
Adapters and Industry
Standards)

13. Integration Repository
Integration Content provided at Design Time
Already contains Integration knowledge for mySAP solutions
Open for Partner and Customer to add collaboration knowledge of non-SAP systems
Content can be filled from different sources using open standard descriptions (e.g. WSDL)
XML and Java based tools
Business Processes
Mapping Objects
Interface Objects
Business Scenarios
Imported Objects
Components (SLD)
Integration Repository

14. Integration Repository – Business Scenarios
Provide overview of business semantics of an integration scenario
Show involved communication partners and their roles
Outline choreography of message exchange
Provide central access to all involved design time objects (like interfaces, mappings)
Provide input for configuration
Support top-down and bottom-up modeling
SAP standard business scenario
“Supplier Managed Inventory …”

15. Integration Repository - Interfaces
Global interfaces and types
Central place to define and catalog global and component-specific interfaces
Interfaces assigned to components
Tracks different interface versions
Descriptions of all existing BAPI, IDOCs and RFCs
Includes message types and data types for high reusability
Based on WSDL (Web Service Description Language, W3C)
Outbound and inbound interfaces
Synchronous and asynchronous interfaces
XML Schema to describe data types
Basis for Proxy generation
populate
populate
Application developer designs a new interface

16. Proxy Generation – Key Benefits
Separation of Business Application from technical Exchange Infrastructure
Platform and programming language independent principles
Generation of proxies in Java, ABAP and .NET platform
Using interface description (WSDL) of Interfaces in the Integration Repository
Design time activity
Proxy connects to (local) Integration Engine
Executes shared integration knowledge (Integration Directory)
Integration Engine
Application
System
Proxy
Business Function

17. Integration Repository - Mappings
Contains preconfigured information for
Structural transformation
Value mapping
Interface Mappings register mappings for interface pairs
Message Mappings are used to implement mappings
Message Mapping definition in the Integration Repository
Graphical Mapping Editor
Import schema (XSD, XML)
Import IR message types
Import archives (zip or jar)
Import RFC, IDoc
Write own Java functions
Mappings are stored in the Integration Repository, selected for business processes in Configuration Time, executed by the Integration Engine at runtime

18. Integration Directory
Integration Content provided at Configuration Time
Contains productive integration knowledge at customer site
Can be derived from Integration Repository during installation and configuration
Open for Customer to add collaboration knowledge relevant to non-SAP components
XML and Java based tools
Business Scenarios
Business Processes
Receiver Determinations
Interface Determinations
Web Services
System Landscape (SLD)
Business Partners
Integration Directory

19. Message Flow within the Integration Server
The Integration Server retrieves required Collaboration Knowledge on Routing, Mapping and Address resolution from the Integration Directory
SAP
3.x
Logical
Routing
Technical
Routing
SAP
4.x
Market- place
SAP Adapter
Mapping
Firewall
Business Partner
Third Party System
mySAP.com
Solution*
Business Partner
3rd Party Adapter
Business Partner

20. Stateless Processing Model
Determination of technical
Transformation of sender
connectivity information
format and values into
Logical receiver and interface
(address, transport protocol,
receiver format and values
determination based on
adapter, ...)
business level rules
Integration Server
XML Message
XML Message
XML Message
XML Message
Envelope:
Envelope :
Envelope :
Envelope :
application systems or adapters
- Sender
- Receiver
- Receiver
- Receiver
- Sender I F
- Receiver I F
- Adress +
Adress + ...
application systems or adapters
- ...
Logical
- ...
Physical
- ...
Mapping
- ...
Address
Payload:
Routing
Payload :
Resolution
Payload:
Payload:
Sender
Sender
Sender
Receiver
Document
Document
Document
Document
FROM TO
Integration
Receiver Determination
“Web Services”
Interface Determination
Directory
Integration
Repository
Mappings

21. Adapters Overview Connection to existing SAP systems
RFC adapter
IDoc adapter
Connection to 3rd party and messaging systems
File adapter
Database (JDBC) adapter
Java Messaging Service (JMS) adapter
SOAP adapter
Plain HTTP adapter
Connection to marketplaces
MarketSet adapter
Adapter framework for selected partners
Adapters provided by partners
For application systems like Siebel, JDE, Oracle, …
For industry standard protocols like RosettaNet, CIDX, … 3 rd
Party and
Messaging Systems
Runtime
SAP Systems
Marketplaces
Integration Server
SOAP
Plain HTTP
Adapter Framework -
Partner Content
(additional 3rd Party
Integration
Repository
Adapters and Industry
Standards)

22. Capturing Shared Knowledge at Design/Config Time
Integration Repository
To be used at design/development time
At SAP, partner, and customer site
Shipped along with content
Integration Directory
To be used at configuration time
At customer site
Content partially derivable from Integration Repository by configuration tools
Integration Engine
To be used at runtime
Relies on content of Integration Directory
Integration Engine

23. SAP XI Release Schedule
Pilot program throughout 2002 (approx. 18 customers)
Part of SAP Supplier Relationship Management (SRM) 2.0
XI 2.0
Restricted shipment (ramp-up) – Dec. 2002
Unrestricted shipment – May 2003
XI 3.0
Restricted shipment (ramp-up) – planned to begin in Dec. 2003
Other SAP
solutions
SRM 2.0
Ramp-up
(using XI 1.0)
SRM 3.0
Ramp-up
(using XI 2.0)
Other SAP
solutions
XI 1.0
Pilot projects
Restricted Shipm.
XI 2.0
Ramp-up
Restricted Shipm.
XI 2.0
Unrestricted
Shipment
XI 3.0
Ramp-up
May ‘02
Dec ‘02
May ‘03
End 2003

24. Major Objectives for SAP XI 3.0
Enhance the functional scope of XI
B2B
Industry Standards support
BPM
Enhance Web Services Functionality
Enhance operational aspects
Performance
High availability
Lower the TCO of XI
Design time
Enhancement concept for interfaces
Import of meta data

25. 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.

26. Copyright 2002 SAP AG. Alle Rechte vorbehalten
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der 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 und Informix® Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Ländern.
ORACLE® ist eine eingetragene Marke der ORACLE Corporation.
UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.
Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.
HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.
JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie.
MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One.
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com und weitere im Text erwähnte SAP-Produkte und -Dienst-leistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.