IBM Software Group

SAP integration workshop

Introduction to SAP Exchange Infrastructure

2007 IBM Corporation

Updated November 13, 2007

This presentation introduces the SAP Exchange Infrastructure component as part of the SAP integration workshop.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 1 of 37

IBM Software Group

Agenda
How does SAP XI fit in SAP NetWeaver ? SAP XI architecture
Components overview SAP XI process engine SAP XI adapter engine

SAP XI usage scenarios

2 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This presentation will first introduce how the SAP XI fits into the NetWeaver strategy over all, then highlight more specifically the SAP XI architecture in different aspects. Finally there will be some discussion on different use scenarios with SAP XI and IBM technology.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 2 of 37

IBM Software Group

SAP NetWeaver SAP Exchange Infrastructure

SAP NetWeaver
PEOPLE INTEGRATION Multi channel access Composite application framework Portal Collaboration Life cycle management

INFORMATION INTEGRATION Bus. intelligence Knowledge mgmt

The SAP Exchange Infrastructure is built on top of the SAP Web AS SAP XI is the backend unification layer of SAP NetWeaver

Master data management PROCESS INTEGRATION Integration broker Business process mgmt

APPLICATION PLATFORM J2EE ABAP

DB and OS abstraction

3 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The SAP XI is the integration broker implementation from SAP. It is placed in this diagram as part of the process integration box. SAP XI leverages the application platform as a runtime environment.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 3 of 37

IBM Software Group

SAP Exchange Infrastructure Why ?

For both internal and external process integration (with SAP and non-SAP)
SAP Enterprise Service Architecture

Prepackaged collaboration knowledge

Integrated business content

SAP Exchange Infrastructure cross-component BPM

Key unification layer of SAP NetWeaver

Other ERP

R/3

CRM

SRM

Other HR

Major control point in the business integration area

Like portal in the people integration area
4

Introduction to SAP Exchange Infrastructure

2007 IBM Corporation

The goal of the SAP XI is to provide a platform for internal and external process integration. It gets delivered with prepackaged collaboration knowledge and offers a major control point for business integration. SAPs goal is to centralize cross-system integration in one place within SAP XI in traditional SAP implementations this is achieved using ALE technology or other EAI tasks like flat file exchange. SAP XI includes also a BPEL engine which enables not only simple message routing between systems, but also more intelligent system integration scenarios. This BPEL capability is not going to replace the existing SAP Business Workflow capabilities that are still included within any ABAP based SAP instance like CRM, SRM or R/3.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 4 of 37

IBM Software Group

Section

SAP XI architecture: Components overview

5 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This section on architecture is in three parts; the first covers an overview of the components

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 5 of 37

IBM Software Group

SAP NetWeaver `04 SR1 PAM: SAP XI 3.0

X Available for DB and APP Neither supported nor planned

Windows (*8) Server 2003 on x64 64bit Server 2003 on IA32 32bit Server 2003 on IA64 64bit

AIX 11.23 on PA-RISC 64bit 11.11 on PA-RISC 64bit 5.2, 5.3 64bit

HP-UX 11.31 on PA-RISC 64bit 11.23 on IA64 64bit 11.31 on IA64 64bit

Solaris 9, 10 on SPARC 64bit 10 on x64 64bit +/+(*16)

Linux: SUSE SLES9, SLES 10, Red Hat EL 4, 5 (SLES9 only on System z 64bit x86_64 64bit Power 64bit IA64 64bit IA32 32bit

i5/OS V5R3, V5R4 64bit

z/OS 1.6, 1.7, 1.8 64bit

TRU6 4

Unicode/Non-Unicode

+/+ (*12) (*12)

+/+ X X X X X X -

+/+ X (*9) X X X X APP APP -

+/+ X X X X APP -

+/+ +/+ X X X X X X X -

+/+ X X -

+/+ X X X X -

+/+ X (*11) X -

+/+ (*12) X X X -

-/+ X (*12) (*12) (*12) -

+/+ X X X X -

+/+ X X X X APP (*6) -

+/+ X X X X APP -

+/+ APP -

+/+ X -

-/HA(*1) DB -

+/+ -

Oracle 10.2 (*3) SQL Server 2000

X X -

SQL Server 2005 (*10) (*12) DB2 LUW 8 (*13) DB2 LUW 9 (*13) MaxDB 7.6 DB2 for i5/OS V5R3, V5R4 (*4) DB2 for z/OS (*12) (*12) (*12) APP

Informix
APP DB HA x64

APP V8, V9 (*5) -

Not for DB server. Application server with whole SAP NetWeaver stack only, Database server only High available solution only X64 and x86_64 represent the same hardware

SAP XI 3.0 supports Unicode platforms only Follow-on DB/OS releases will be released as usual JDK Versions are specified in the installation guides
6 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows the platform availability matrix.

Since SAP XI is running on top of the SAP Web Application Server 6.40 and later, it is supported on the same platforms. An SAP XI specific difference is that is supported on Unicode platforms only.
SAP XI is one of the first new SAP middleware components that is using both personalities of an SAP Web Application Server the Java and the ABAP part. Check the attached notes for the detailed description of the legend. Legend: (*1) See SAP note 821904 Separating SCS instances for ABAP and J2EE (*3) See SAP note 720886 Oracle Database 10g: Integration in the SAP environment. For Double-Byte code pages see SAP note 858869 Desupport of multibyte character sets as of Oracle 10g. All availability information applies to new installations of SAP Solution Manager 4.0 too. For Information about the upgrade to SAP Solutions Manager 4.0 please refer to http://service.sap.com/pam (*4) For upgrade start system on ASCII or Unicode required (*5) Non Unicode available only (*6) Linux SLES and Linux RHEL 5 (not RHEL 4) available. (*8) English version only. See SAP note 362379 Localized Windows & MUI Support for SAP Software on Windows. (*9) DB server 32-bit only (*10) See SAP note 905634 Release planning for Microsoft SQL Server 2005 for more details (*11) Planned availability with DB2 for LUW 9 FP3 (*12) Rapid Installer available (*13) DB2/UDB renamed to DB2 Linux Unix Windows (LUW) (*14) Planned for SAP NetWeaver SR2 (*16) Non-Unicode: Dialog Instances only

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 6 of 37

IBM Software Group

SAP XI architecture
Collaborative business process runtime

7 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This is the general architecture from SAP XI. As you see there are two main blocks. The shared collaboration knowledge area contains the business packages and business process templates. They can be built and changed with the Integration builder. To build them, you can access data from the SLD and export it to the runtime environment. In the collaborative business process runtime part, the built business processes get connected to different systems in the SLD and really runs in this environment. Another perspective is to separate between the design, configuration and runtime environment. As you can see in this slide, the runtime environment can access other SAP systems and other systems using SAP XI adapters.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 7 of 37

IBM Software Group

Integration builder
Integration builder:
The integration builder can be understood as the client component that is be used to connect to the integration repository and the integration directory. It uses Java Web Start technology and requires a Java 1.4 environment on the client machine. It is used during design time to develop new interfaces and mappings and during configuration time to configure services, routings and mappings.

8 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The Integration Builder can be understood as the client component that is be used to connect to the integration repository and the integration directory. It uses Java Web Start technology and requires a Java 1.4 environment on the client machine. It is used during design time to develop new interfaces and mappings and during configuration time to configure services, routings and mappings. The Integration Builder is the main tool to develop integration artifacts for SAP XI Scenarios and to configure how packages are finally deployed on the SAP XI .

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 8 of 37

IBM Software Group

Integration repository
Integration repository
The integration repository provides collaboration knowledge available at design time, for example, business scenarios, business processes, mappings, interfaces. It is built in Java and follows Java 2 Enterprise Edition (J2EE) standards. The information in the integration repository is used by the integration directory, which adds configurationspecific information that is needed for routing.

9 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The Integration Repository provides collaboration knowledge available at design time, for example, business scenarios, business processes, mappings, interfaces. The IR can be understood as the storage where all integration relevant artifacts are stored. It is built in Java and follows Java 2 Enterprise Edition (J2EE) standards. The information in the Integration Repository is used by the Integration Directory, which adds configuration-specific information that is needed for routing.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 9 of 37

IBM Software Group

Integration directory
Integration directory
The integration directory contains detailed collaboration knowledge about the current system landscape around the SAP Integration Server. It is built in Java and follows Java 2 Enterprise Edition (J2EE) standards. It is a description of routing rules (receiver and interface determinations), collaboration profiles (parties, services and channels) and collaboration agreements. The integration directory details the information from the integration repository that is specific to the configuration.
10 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The integration directory contains detailed collaboration knowledge about the current system landscape around the SAP integration server. It is built in Java and follows J2EE standards. It is a description of routing rules, collaboration profiles, and collaboration agreements. The integration directory details the information from the integration repository that is specific to the configuration.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 10 of 37

IBM Software Group

Integration builder and interface repository

11 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows how the Integration Builder (IB) is used to access the Integration Repository (IR). Within IB there are several editors which enable a developer to create and change integration artifacts like scenarios, processes, mappings and interfaces. All these artifacts are then stored within the IR in dedicated projects. The IR is also leveraging data stored in the System Landscape directory to make the development cycle easier and more meaningful.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 11 of 37

IBM Software Group

Integration builder and interface directory

12 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows how the integration builder is used to access the integration directory. The part of integration builder which is used to access the integration directory is heavily wizard driven. This means wizards are used to deploy specific integration scenarios into the existing system landscape. There are several editors that enable the administrator to adjust existing deployments by changing routing rules, collaboration agreements and profiles. All these runtime behaviors are then stored within the integration directory and later on accessed by the Integration Server runtime to determine how the specific integration component runs.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 12 of 37

IBM Software Group

Integration server
Integration server
The integration server receives messages from the sender applications, applies routing and mapping rules to these messages and finally sends them to the receiving application. Each SAP Web Application Server has the integration server software built in. The specific configuration of the particular SAP WebAS activates its role as a central integration server.

13 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The integration server receives messages from the sender applications, applies routing and mapping rules to these messages and finally sends them to the receiving application in a simple scenario. In a more enhanced scenario maybe a BPEL process is triggered which then can also trigger more enhanced tasks. Each SAP Web Application Server has the Integration Server software built in. The specific configuration of the particular SAP WebAS activates its role as a central Integration Server.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 13 of 37

IBM Software Group

Integration Engine & Business Process Engine

Integration engine
One central part of the integration server Offers main services for processing messages:
mapping and routing guaranteeing quality of service like exactly-once delivery of messages

Business process engine

To support cross component Business Process Management (ccBPM) the Integration Server of SAP XI also contains a Business Process Engine. This component takes care of the running and persistency of cross-component integration processes.
14 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The integration engine is one central part of the integration server. It offers the main services for processing messages, like mapping and routing, and guaranteeing quality of service like exactly-once delivery of messages. To support cross component Business Process Management, or ccBPM, the integration server of SAP XI also contains a business process engine. This component takes care of running and persistency of cross component integration processes. The SAP Business process engine is able to run BPEL compliant process that use WSBPEL 1.1

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 14 of 37

IBM Software Group

Integration directory and interface server

15 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows that the integration server is the runtime for the integration component. It uses configuration data that is stored in the integration directory.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 15 of 37

IBM Software Group

Runtime workbench
Runtime workbench
The runtime workbench is used to test and monitor the individual components of the SAP Exchange Infrastructure including business systems defined in the system landscape directory. Furthermore, it tracks the processing of messages (from end to end) through all involved components of the infrastructure and helps in error analysis of faulty messages and in troubleshooting. The runtime workbench provides a browser based UI which consumes BSP applications which are located on the SAP XI server.
16 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The runtime workbench is used to test and monitor the individual components of the SAP Exchange Infrastructure, including business systems defined in the system landscape directory. Furthermore, it tracks the processing of messages from end to end through all involved components of the infrastructure and helps in error analysis of faulty messages and in troubleshooting. The runtime workbench provides a browser-based UI which consumes BSP applications that are located on the SAP XI server.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 16 of 37

IBM Software Group

Central monitoring
SAP runtime workbench provides: Component monitoring Message Monitoring (End-to-End monitoring) Performance monitoring Alert framework

No business level monitoring !

17 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

There are different aspects in a central monitoring. The end-to-end message monitoring is the monitoring of the technical process of the message flow - monitoring the message processing on one specific component, and relevant only for message processing components. The component monitoring has a smooth integration with CCMS, for Monitoring of ABAP and Java components and Monitoring of all XI components - including non message processing components. Performance analysis is used to enhance performance statistics, measuring of throughput and latency, selection and aggregation of performance data by XI component and time range and message attributes. Message alerting is based on Alerting Framework. Active monitoring produces alerts being sent by e-Mail or SMS, and CCMS-alerts and message-oriented alerts

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 17 of 37

IBM Software Group

Section

SAP XI architecture: SAP XI process engine

18 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This second of three architecture sections covers the process engine.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 18 of 37

IBM Software Group

Integration processing
Integration directory
Scenarios Business processes
Receiver determination

Integration server
Inbound handling (also in adapters)

Routing rules
Receiver determination rules Interface determination Rules (including mapping assignment) Interface determination Channel determination Mapping Business process

Business process engine

Collaboration agreements
Security Outbound handling (also in adapters)

Collaboration profiles
Parties and services channels

Integration engine

19 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The slide also shows that it is not mandatory to incorporate a BPEL process into an integration task. Currently most of SAPs prepackaged integration content consists only of native message routing and transformation, and protocol adjustment.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 19 of 37

IBM Software Group

Cross component business process management Design, run and monitor processes
across applications and systems Provides process control in the central technology layer Contains a graphical modeler Integral part of XI
Modeling enables linkage to XI design objects: interfaces, mappings BPM runtime is embedded in the integration server runtime

Adheres to standards
Industry standard support (BPEL4WS) Import and export of process definitions

Technical process monitoring

Integrated with general technical monitoring of XI Graphical process monitoring
20 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The business process engine is able to run WS-BPEL 1.1 processes. While the integration server is responsible to run the BPEL process, within the integration builder there is an editor available to create a BPEL process from scratch using existing interfaces that are available in the integration repository.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 20 of 37

IBM Software Group

Integration builder BPEL editor panes

21 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows the BPEL editor within the integration builder. It is the counterpart to the BPEL editor IBM offers within WebSphere Integration Developer. SAPs editor is divided in different areas that shows information from various objects dependent upon what is selected.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 21 of 37

IBM Software Group

ccBPM Process step types

22 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

These are the standard nodes that can be used within a SAP BPEL process most of these icons are borrowed from the SAP Business Workflow, which is an SAP-proprietary workflow dialect that is included within any SAP ABAP system.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 22 of 37

IBM Software Group

SAP ccBPM
ccBPM is integrated with the business workflow (WebFlow Engine). An integration process can send messages to a workflow and, conversely, messages from a workflow can be processed in an integration process. Can import, export and run WS-BPEL 1.1 compliant processes.

23 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The new ccBPM capability that is a core part of SAP XI is an enhancement of the existing SAP Business Workflow, also known as the WebFlow engine.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 23 of 37

IBM Software Group

Section

SAP XI architecture: SAP XI adapter engine

24 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This third architectural section covers the adapter engine.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 24 of 37

IBM Software Group

SAP adapter engine

25 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

SAP XI is using adapters to connect any backend system to the integration server. The adapter portfolio is fairly rich because SAP is partnering with major adapter development business partners like Seeburger and iWay to use their adapters together with an SAP XI broker. The slide also highlights the capability to address scaling requirements by being able to install multiple adapter engines that work together. If no adapter is available for a more exotic backend, the partner connectivity kit can be used to create a new custom adapter that reflects the special needs of a dedicated backend system.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 25 of 37

IBM Software Group

SAP J2EE adapter engine

The J2EE adapter engine is the central configuration tool for adapters used with SAP XI. It is based on the adapter framework, which itself is JCA-compliant and is based on the SAP J2EE engine (as part of the SAP Web Application Server). The adapter framework provides interfaces for configuration, management, and monitoring of adapters. It also has its own queuing and logging services. The adapter engine can run temporarily without a connection to the integration server and still providing guaranteed messaging to and from connected application systems. The configuration of the adapter engine is done centrally in the integration directory, using meta-data about the adapters stored in the integration repository. The adapter engine can also be monitored by the runtime workbench.
26 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide lists many key attributes of the adapter engine of SAP XI.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 26 of 37

IBM Software Group

SAP XI Adapter Engine

The integration server comes with two built-in adapters the IDoc and the HTTP adapter By default, a J2EE adapter engine is installed centrally on the integration server. If needed, additional adapter engines can be installed non-centrally. All these J2EE adapter engines are configured centrally in the integration directory of XI. The SAP PCK offers an easy way to exchange messages between an application system and SAP XI, without sophisticated services (like routing and cross-component BPM) and design of collaboration knowledge. Configuration and administration of the PCK are always done locally.

27 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide also lists adapter engine attributes.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 27 of 37

IBM Software Group

SAP XI adapters by SAP

Adapters connect the integration engine to existing SAP systems and to other systems. These adapters are developed by SAP:
Application adapters
RFC Adapter IDOC Adapter

Technical adapters
File/FTP Adapter Database (JDBC) Adapter Java Messaging Service (JMS) Adapter Plain HTTP Adapter SOAP Adapter Mail Adapter SAP Business Connector Adapter MarketPlace Adapter

Industry standard adapters

CIDX Adapter RNIF Adapter

28 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

You can see here the core adapters provided by SAP.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 28 of 37

IBM Software Group

SAP XI adapters from other vendors

29 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

These are some of the major adapters SAP is leveraging from their two key partners in the adapter area, Seeburger and iWay.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 29 of 37

IBM Software Group

SAP XI adapter by SAP

30 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

The table on this slide highlights various technical details of the most popular SAP XI adapters.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 30 of 37

IBM Software Group

Proxy generation and proxy runtime

The proxy generation allows to generate proxies (classes) into application systems for communication. An application program can only exchange messages using these proxies if the proxy runtime is installed in the application system. Proxies connect to the Integration Server using the SOAP-based XI message protocol. The XI message protocol is based on SOAP with attachments communication, using HTTP or HTTPS as transport protocol. The proxy generation supports target languages ABAP and Java.
31 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

Between SAP XI and new SAP business systems that have an SAP Web Application Server runtime of release 6.40 and higher, a new communication style is supported. SAP enabled these new business systems to be connected with an SAP XI system, and to use existing interface definitions to generate ABAP or JAVA based proxy objects in the target business system. This proxy can then be used by the business system to send data or by the integration server to send data to the business system depending if it is an inbound or outbound proxy. The protocol used to do this is SOAP/HTTP with custom SAP SOAP headers which are used to run enhanced logic on top of this carried control information. This proxy approach hides the real business function from the connecting integration broker and delivers therefore an abstraction layer to decouple integration logic from business logic.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 31 of 37

IBM Software Group

Section

SAP XI usage scenarios

32 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This last section discusses two usage scenarios for the SAP XI software.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 32 of 37

IBM Software Group

Adapter based backend integration

33 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

This slide shows how the integration server can be used to access any backend using adapters and to provide to the external world a so-called enhanced Web Service. This means more intelligent integration logic is run in between. The lower layer shows that also any Web service client can be used to call using SOAP/HTTP business functions directly in any SAP business system that already has the new Web Services Framework included. This framework is from the SAP Web Application Server 6.40 and higher. This is then named basic Web service.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 33 of 37

IBM Software Group

Synchronous peer-to-peer shortcut in XI using Web services

Without routing, mapping, business process management capabilities Joint use of Web Services Framework of SAP XI and SAP Web AS Synchronous XI inbound proxies can be used natively as Web services in SAP Web AS like Remote Function Modules Unified programming model and proxy generation for XI and Web services in SAP Web AS
34 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

Finally this slide shows that new business systems can do native peer-to-peer communication using their existing Web service capabilities. Whenever more extensive communication is required, a broker based integration needs to be evaluated. SAP created a dedicated XI protocol that can be used to leverage an SAP XI instance in the communication. This special protocol is SOAP/HTTP Web services but with additional SAP specific headers; for example, for routing information.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 34 of 37

IBM Software Group

References
Web
SAP Exchange Infrastructure http://www.sap.com/xi

35 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

For more information on the SAP Exchange Infrastructure, go to the address listed here.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 35 of 37

IBM Software Group

Feedback
Your feedback is valuable
You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback.

Did you find this module useful?

Did it help you solve a problem or answer a question?

Do you have suggestions for improvements?

Click to send e-mail feedback:

mailto:[email protected]?subject=Feedback_about_P04_SAP_NW_Exchange_Infrastructure.ppt

36 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

You can help improve the quality of IBM Education Assistant content by providing feedback.

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 36 of 37

IBM Software Group

Trademarks, copyrights, and disclaimers

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: AIX DB2 i5/OS IBM Informix System z z/OS SQL Server, Windows, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. J2EE, Java, JDBC, JDK, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements or changes in the products or programs described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (for example, IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp.

37 Introduction to SAP Exchange Infrastructure 2007 IBM Corporation

P04_SAP_NW_Exchange_Infrastructure.ppt

Page 37 of 37