XI Technical Architecture Overview

Author: Paul Médaille

 Objectives
After completing this lesson, you will be able to:
z Describe the XI Architecture in detail
z Name all of the components of the XI
z Detail the functionality of each component
z Explain the role of the SAP Web Application Server
in the XI architecture
z Describe the role of Java Web Start for the XI
development environment

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

 XI Technical Architecture Overview

Contents:
•Architecture Overview
•XI Components
•System Landscape Directory
•The Integration Builder
•Integration Repository
•Integration Directory
•The Integration Server
•The Integration Engine
•Business Process Management
•The Adapter Framework
•The Partner Connectivity Kit
•Usage of the Web Application Server in XI

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

 XI Technical Architecture Overview: Business
Scenario

z Your client has decided to implement the SAP Exchange

Infrastructure.
z As a NetWeaver technical consultant, you are responsible for
the technical implementation
z In order to do this, you must understand the Architecture and
components of the XI

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

 Architecture Overview

Shared Collaboration Execute

Execute Collaborative
Collaborative Business
Business Processes
Processes
Knowledge

Central
Central Monitoring
Monitoring –– Run
Run Time
Time Workbench
Workbench
Design Configuration

Integration Server SAP

SAP
Integration
Integration Builder
Builder Systems
Systems
Business Process Engine
Marketplace/
Marketplace/
Integration Engine
Business
Business
Partner
Partner
Central Adapter Engine
Integration
Integration Integration
Integration
Repository
Repository Directory
Directory
Adapter Partner
Partner

Resource
Framework

Adapter
Connectivity
Connectivity Kit
Kit

Messaging
Queuing Application
Security Handling Techn. System
File/DB/JMS

System
System Landscape
Landscape Directory
Directory (SLD)
(SLD)
© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The XI architecture includes components that are used at design time, configuration time, and run time.
„ Information about the systems and software components used in an integration scenario are stored in the
System Landscape Directory.
„ The Integration Builder is the tool for accessing the design- and configuration-time components;
developers and configurators use it to access the Integration Repository and the Integration Directory.
„ The Integration Repository is used to work with all of the development object of the XI.
„ The Integration Directory is used to work with all of the configuration options for an integration scenario
in the XI.
„ The Integration Server provides the runtime environment for processing XI messages received by the
Exchange Infrastructure. It includes:
y The Business Process Engine for executing Integration Processes (cross-component business
processes);
y The Integration Engine for processing all XI messages for all scenarios in a consistent way;
y The Central Adapter Engine for connecting to application systems that are not based on the SAP Web
Application Server version 6.20 or higher.
„ The Runtime Workbench for central monitoring and management of the SAP XI and all of its
components.
„ All central components are installed on a Web Application Server version 6.40.
 Accessing Java-Based XI Tools

Integration
Integration Integration
Integration
Repository
Repository Directory
Directory

Central
Central Monitoring
Monitoring ––
Runtime
Runtime Workbench
Workbench

System
System Landscape
Landscape Directory
Directory (SLD)
(SLD)
© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The following XI tools are java-based and reside in the J2EE stack of the Web AS: The Integration
Repository, the Integration Directory (both of which are accessed via the Integration Builder), the System
Landscape Directory, and the Runtime Workbench.
„ To access java-based components of the XI, you can use transaction SXMB_IFR from the SAP GUI.
Alternately, you can navigate in a browser window directly to the URL
http://<server>:<port>/rep/start/index.jsp. In this case, server is the fully-qualified name of the
Integration Server, and port refers to the base http port of the J2EE engine on the Integration Server.
„ In order to access the java components for XI 3.0, you must have a J2SDK (Java 2 Software Development
Kit) version 1.4.2 installed on the front end.
„ The J2SDK installation includes the installation of Java Web Start (JWS); JWS is a caching application for
fat java clients. Because the Integration Repository and the Integration Directory applications are each
approximately 20-30 MB in size, these applications must be cached at the local machine, rather than being
downloaded each time they are called.
 The System Landscape Directory

System
System Landscape
Landscape Directory
Directory (SLD)
(SLD)

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The System Landscape Directory is a central repository of information about software and systems in the
data center expressed in a web-standard protocol called the Common Information Model (CIM).
„ The XI is technically a client application to the SLD.
„ Before development can begin, the Software Products and Components for which integration objects are
to be developed must be created in the Software Catalog of the SLD.
„ As part of the SLD installation, information about all SAP Products and Components is imported. This
information can be periodically updated via xml files downloaded from the service marketplace. In this
way the SLD can be kept aware of all currently extant versions of SAP software. The customer must
enter information about 3rd party products and components.
„ In order to completely configure a scenario, the technical and logical descriptions of the systems involved
should be entered in the System Landscape area of the SLD.
 The Exchange Profile

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The exchange profile is an XML document that is stored in the main database of the SAP Exchange
Infrastructure (XI). The parameters contained in this document define some basic technical settings. Most
of them are initialized automatically during the installation phase, but in some cases the administrator may
need to maintain them.
„ The XI provides a maintenance interface for this file. The maintenance screen for the Exchange Profile
can be accessed at:
http://<host>:<port>/exchangeProfile
„ The <host> above refers to the IS host, and the <port> refers to the base http port of the J2EE engine.
„ Settings that are maintained in the Exchange Profile include connection parameters such as hostnames,
ports, users, and passwords that allow the various components of the XI to communicate with one another.
 The Integration Builder

Integration
Integration Builder
Builder

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Builder is a java application that is used to design, edit, and configure Integration
Scenarios. The Integration Builder provides the framework for the design- and configuration-time tools of
the Exchange Infrastructure.
„ There are two instances of the framework, the Integration Repository for design-time activities, and the
Integration Directory for configuration-time activities.
„ The Integration Builder gives both tools a common look and feel.
„ Capabilities of the Integration Builder include:
y Navigation and object handling;
y Drag-and-drop editing;
y Versioning and history;
y Selection (F4) help;
y Un-docking and docking of editors;
y Editing documentation.
y Importing and exporting objects.
„ Changes are saved locally to (a) user-specific change list(s). Upon activation of the change list or a subset
of objects within it, an activation check is performed and, if passed, the objects are created in their active
version on the Integration Server and the cache of the Integration Server is updated.
 The Integration Repository

Integration
Integration Repository
Repository

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Repository is used to access development objects in the XI.

„ The Integration Repository ships with SAP-specific content. Other SAP interfaces, such as RFC’s or
IDOC’s, can be loaded into the repository via an RFC connection to a backend SAP system.
„ Other development objects can be created directly in the Integration Repository, or else uploaded from
XSD or WSDL files.
„ Development objects are organized by Software Component Version and namespace. This allows for
easier maintenance (for instance, enabling the development of new interfaces for a updated version of a
software component while the earlier version is still in productive use).
 The Integration Directory

Integration
Integration Directory
Directory

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Directory is used to access configuration objects in the XI.

„ Because the configuration always works with the concrete system landscape of the customer environment,
the Integration Directory is maintained entirely at the customer site.
 The Integration Server

The Business Process Engine is the

runtime component that executes
collaborative integration processes

Integration Server
Business Process Engine The Integration Engine is the
processing pipeline for all XI
Integration Engine
messages. All messages are
received in the special XI-SOAP
Central Adapter Engine
format and processed in the
Adapter Integration Engine in a consistent
Resource

Framework
Adapter

way.

Messaging
Queuing The Central Adapter Engine
Security Handling
connects the Integration Server to
systems not based on Web
Application Server v. 6.20 or higher.
Decentral instances of the adapter
framework can also be installed.

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Server is used primarily to process XI messages.

„ The Integration Server is built on SAP Web Application Server 6.40.
„ The Business Process Engine executes the Integration Processes, which are cross-component business
process that are created and configured in the Integration Repository and Integration Directory,
respectively.
„ The Integration Engine is the run-time engine for XI messages. The IE processes messages that are
rendered in the special XI-SOAP format.
„ Business systems based on SAP Web Application Server version 6.20 or higher can send and receive
messages in the XI-SOAP format. Other systems communicate through adapters, and the central adapter
instance hosts the resource adapters for communicating with, for instance, flat file interfaces or JMS
queues.
„ Additional, distributed instances of the adapter framework can also be installed, to keep the adapter close
(from a network/firewall perspective) to the business system.
„ Adapters for legacy SAP interfaces, such as RFC or IDOC, are also part of the central Integration server.
 The Integration Engine

„The Integration Engine consists of a configured set of Pipeline

Services through which XI messages are processed.

„A Pipeline Service is an ABAP Objects class that performs a

particular processing step on a message.

„mySAP applications based on SAP Web Application Server

version 6.20 or higher have their own local instance of the
Integration Engine. This allows for communication with the
Central Integration Engine in the native XI-SOAP format via
Proxies.

„The Integration Engine on the Central Exchange Infrastructure

system is configured as the Central Integration Engine and is
known as the Integration Server.

„All other Integration Engines are configured as Application

Systems.

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ It is important to distinguish between the terms Integration Engine and Integration Server. The Integration
Engine on the SAP system that is installed as the Exchange Infrastructure system is configured to be the
Central Integration Engine or Integration Server.
 The Integration Engine and the Pipeline

Application System

Transaction SXMB_ADM

Integration Server

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The pipeline is the set of processing steps through which all XI messages are processed once they are
received at the Integration Engine (Integration Server).
„ The processing steps include (most significantly):
y Receiver Determination (which partner system[s] shall be the recipient of the message);
y Interface Determination (to which interface[s] on the selected systems shall the message be sent);
y Technical Routing (binds the message to a particular protocol and delivery channel);
y Message Mapping (call the Mapping program[s] to format the message in the receiver’s preferred
format).
„ Transaction SXMB_ADM is used to configure pipeline settings, for instance logging and trace levels.
 Business Process Management

Integration Builder Integration Server

Business Process Engine

Integration
Process Correlation
Directory Execution Handling
Integration Process
(Configuration)

Routing Rules Process / Message Store

(References)
2
3

Message
Integration
Process Editor

4
Message

Channel
Repository Routing Mapping
Det.
Integration Process 1
(Definition)
Integration Engine
Abstract
Interfaces Adapter Engine

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ Integration Processes are Business Processes that can run across multiple systems and are expressible in
the standard web protocol for Business Process execution, BPEL4WS (Business Process Execution
Language For Web Services). You will also see Business Processes referred to as Business Process or
cross-component Business Processes in the documentation. If you are familiar with SAP Business
Workflow, then you can think of these Business Processes as workflows that run across multiple
components.
„ The Integration Server includes a built-in Business Process Engine; it includes a persistence layer (the
process/message store), the runtime for process execution, and the logic for correlation handling (Business
Processes allow you to send and receive multiple messages relating to a single document; for instance, line
items for a purchase order may be gathered from several sources. Correlations let you relate the incoming
documents to a unique key, for instance a PO number, so that incoming documents are processed only
with the master document to which they belong.)
 Adapter Framework

Installation Option Advantages Disadvatages

Adapter Engine Provides complete More resources

(J2EE engine) integration into the SAP XI
environment:
• Central Monitoring
available
• Central Configuration
available
Plain J2SE • Fewer resources needed
Adapter Engine when running in a Java
environment only
• Supports non-SAP Web
AS 6.40 platforms
needed for installing
the SAP Web AS 6.40
J2EE system (J2EE
only)
Less integration into
the SAP XI
environment due to
lack of central
configuration and
monitoring services

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ There are two instances of the Adapter Framework: the J2EE and J2SE versions. The table above
summarizes the advantages and disadvantages of each installation type.
„ The J2EE adapter framework uses JCA-based (Java Connector Architecture) adapters.
„ The J2EE adapter is always installed on the Integration Server.
„ Additional instances of the J2EE framework can be installed de-centrally, then configured and monitored
centrally.
„ The J2SE adapter engine is provided for backward-compatibility, and for connections to java standalone
systems.
„ The Partner Connectivity Kit (PCK), which is used to enable messaging with partners or subsidiaries that
have no native xml-messaging capabilities, is based on the J2EE adapter framework.
 Adapter Architecture

Integration Repository / Integration Directory / System Landscape Directory

Integration Server

Business Process Engine

Integration Engine
Partner Connectivity
Central Optional local Kit PCK Configuration
J2SE and Monitoring
Adapter Engine Adapter Engine
Adapter

Resource
Adapter

Resource

Resource
Adapter

Adapter
Engine
Adapter

Adapter Framework Adapter FW Adapter FW

IDoc

Messaging Messaging Messaging

Queuing Queuing Queuing
Adapter Security Handling Security Handling Security Handling

File
DB SAP SAP System SAP System SAP System
JMS 3rd Party Appl. 3rd Party Appl. 3rd Party Appl.
System
File/DB/JMS File/DB/JMS File/DB/JMS
Marketplaces Marketplaces Marketplaces

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Server processes messages that are received in the XI-SOAP format; systems that are capable of producing messages in this
format (e.g., mySAP components based on SAP Web Application Server v. 6.20 or higher) can communicate natively with the XI. All other
systems, including older SAP releases, communicate through adapters.

„ The Central Adapter Engine is based on the integrated SAP J2EE engine. It includes functionality for message handling, queuing, and security.
There is an included module processor which lets you extend the basic functionality of adapters by calling additional modules for processing
messages in the adapter.

„ Individual resource adapters are “plugged in” to the adapter framework. These can be delivered by SAP, or developed by partners or customers
using the Java Connector Architecture.

„ Some adapters are built into the Web Application server; for instance, the IDOC adapter is part of the ABAP layer, and all IDOC’s are processed
by the IDOC Adapter. For any IDOC’s that you wish to process at the ALE layer of the IS, you must maintain an exception table which specifies
which IDOC’s are processed in the normal way.

„ Additional adapters based on the J2EE framework can be installed de-centrally, and can be configured andmonitored centrally.

„ The Resource adapters that are available with the Adapter Framework include:

y RFC Adapter - Plain HTTP adapter

y JDBC Adapter - File/FTP Adapter

y JMS Adapter - SOAP Adapter

y Marketplace Adapter - Mail

y SAP BC (header extension for support of Quality of Service)

y RosettaNet (RNIF 2.0) Adapter

y CDIX (RNIF 1.1) Adapter

 Adapter Engine

http://<IntegrationServerURL> System Landscape Directory

IS • Holds component description
Runtime including address data
Config.
cache XI Message Adapter
OK / Error
Framework
Adapter Engine in SAP J2EE
Integration
Integration Repository
Repository Adapter
Module Processor
•• Holds
Holds Adapter
Adaptermetadata
metadata http://<AdapterEngineURL>
Channel
Sender E
I
Q Adapter
Receiver
S
Integration Builder / Directory: ´Messaging

... Receiver determination

• Party->Service->Action Configuration Tracing
cache Logging Adapter-
... Channel Definition: Security
Specific
Component
• Adapter Engine Services
• Adapter Type Monitoring Administration
• Message Protocol
• Transport Protocol
Configuration
• Security Master
• Channel Configuration Runtime Workbench
End-to-End Monitoring • Uis for adminstration,
(Sender / Receiver Agreement: Message flow over all XI monitoring
• Party/Service/Action <-> Channel components / applications

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The individual components of the SAP Adapter Engine (AE) are detailed above. It is not important to
master all of the details at this point, but to get a feel for the role of the Adapter Engine in the XI
Architecture.
„ The XI, and the Adapter Engine, support Synchronous and Asynchronous delivery; in XI terms, these are
described with a Quality of Service (QoS) descriptor. The XI supports QoS Best Effort (BE), Exactly-
once (EO), and Exactly-once-in-order (EOIO). These are equivalent to RFC types Synchronous RFC
(sRFC), Transactional RFC (tRFC), and Queued RFC (qRFC), respectively.
„ EO and EOIO are both guaranteed delivery protocols; this provides protection against transitory failures
by retrying failed calls and insuring one-time execution of each interface call. The queuing mechanism of
the Adapter Engine provides support for guaranteed delivery.
„ The messaging layer (sometimes referred to as 'messaging system' is deployed as a service of the Java
engine and communicates with the Integration Engine using the XI message protocol (SOAP with
attachments) over HTTP. Because the messages are persisted locally, messages processed through the AE
are visible (in their various versions) in the Runtime Workbench (in the same way the messages on the IS
can be viewed in transaction SXI_MONITOR)
„ The Module Processor allows for extending the functionality of the resource adapters by allowing the AE
call additional modules.
„ The AE includes functionality for Administering and Monitoring the AE and the resource adpaters.
 Industry Standard Support and B2B

Integration Integration
Standard Repository Directory
scenarios
Business Scenarios
Application Routing Rules
Business Processes
↔
standard Mappings Collaboration Agreements Business
Partner
Business Message Interfaces Collaboration Profiles
Document
Schema

SAP Integration Server

Industry Solution
Business Process Engine
(e.g. High Tech)
IDoc/ Integration Engine
Proxy

Adapter Engine
Messaging Industry to
3rd Party Resource
Adapter
Queuing Standard Business
Application Security Handling Adapter
Partner

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ XI 3.0 includes extensive and growing B2B support for communication with business partners using
industry standards such as RosettaNet, CIDX, PIDX, and UCCNet.
„ Collaboration agreements in the Integration directory configure B2B scenarios, including aspects such as
certificate handling, partner ID, etc.
 Partner Connectivity Kit

• Purpose: Open an XI landscape to partners without XI,

but the need to use adapters
Firewall
Runtime Workbench Adapter
End-to-End • Uis for administration, Framework
Monitoring monitoring
PCK in SAP
Adapter J2EE
Engine in SAP J2EE B
Module Adapter a
XI Sender
Channel Processor c
IS https://<IntegrationServerURL> Message Adapter k
Runtime Q Recv. e
https://<AdapterEngineURL> n
Conf. ´Messaging d
cache
Configura Tracing Adapter-
tion Logging Specific
Conf Master Security Compone
nt
Integration Builder / UI Services
Monitoring Administration
Directory:

Mon. UI Adm. UI
... Receiver
Configuration
determination Master
• Party->Service->Interface

...
System Landscape Dir.
• component description
including address data
© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Partner Connectivity Kit (PCK) can be used to extend XI functionality to partners and subsidiaries
without XI, but with the need to use adapters.
„ The PCK is installed in an instance of the SAP Web Application Server, J2EE only version.
„ The PCK is an instance of the Adapter Engine that is configured as a PCK (the same software is used as a
decentral adapter engine, but configured as such).
 Central Monitoring

Message PMI
Monitoring

Component
Monitoring CCMS
Runtime System
Workbench Performance Landscape
Analysis Directory
Message Alerting Alerting Framework

Integration Server
(SAP Web AS ≥ 6.40)

Business Process Engine

Integration Engine (local) J2SE

SAP Application
Adapter Adapter
SAP Web AS ≥ 6.40 Engine Engine
Adapter Engine
using XI proxies

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Central Monitoring tools permit the administrator to get a central view on all components and
messaging of the Exchange Infrastructure.
„ Architectural components include the Computing Center Management System (CCMS), the Process
Monitoring Infrastructure (PMI), and the Alerting Framework.
„ The Runtime Workbench allows an administrator to access central monitoring information for all
components, as well as configuration for the monitoring architecture.
 XI 3.0 components in SAP Web AS 6.40

HTTP(s)

HTTP(s) ICM
Central Monitoring

J2EE ABAP
XI Tools
Integration Builder Business Process
(IR, ID) Engine
Runtime Workbench
JRFC
Mapping runtime
Integration Engine
Adapter Engine

SLD

OpenSQL OpenSQL
For Java for ABAP

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ As the slide shows, some XI components belong to the ABAP layer of the Web AS, and some components
run at the J2EE layer.
„ Both layers use database-independent programming via OpenSQL (for Java or ABAP as appropriate).
The RDBMS has separate schemata for the objects used by each runtime stack.
„ The J2EE layer provides a very nice interface for doing design- and configuration-time activities, while
the full power of the ABAP stack is brought to bear on the challenge of processing a (potentially) heavy
load of messages passing through the XI.
 Usage of the Web Application Server in XI (I)

The SAP Exchange Infrastructure is

installed on top of a Unicode-enabled
Web Application Server v. 6.40 (ABAP +
J2EE). Installation options include
Central System installation, Standalone
DB with Central Instance on separate
hosts, and Central Instance with
multiple Dialog Instances

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The following installation types are supported: Central System (Central Instance and Database Instance on one host),
Standalone Database System (Central Instance and Database Instance on separate hosts), Dialog Instances for ABAP
and Java
„ For the table above, please note the following:
** Automatically installed with the SAP Exchange Infrastructure
*** SAP J2EE only (SAP Web AS 6.40 SAP J2EE system) is a prerequisite
**** For none SAP J2EE Web AS Java environments
„ The Exchange Infrastructure is comprised of the following components:
y Integration Server
y Integration Builder
- Includes the following components: Integration Directory and Integration Repository.
y Runtime Workbench
y Adapter Engine
„ The Adapter Engine is to be installed on the central instance of a SAP Web AS 6.40 J2EE system (J2EE only) and
includes the Java Proxy Runtime and Java Proxy Server that enable Java application business system to exchange
data using Java proxies. The Adapter Engine includes the following adapters:
y File Adapter - JMS Adapter
y JDBC Adapter - SOAP Adapter
y Marketplace Adapter - RNIF Adapter
y Java Proxy Server - Java Proxy Runtime
 Usage of the Web Application Server in XI (II)

SICF

http://<host>:<port>/sap/xi/engine?type=entry

SMICM

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ The Integration Server is installed on top of the SAP Web Application Server version 6.40.
„ The entry point for the pipeline is an Internet Communication Framework (ICF) service. The ICF
provides the link between http calls and the ABAP stack of an SAP Web Application Server. ICF services
are accessed via a URL; the entry point of the XI pipeline has the URL:
y http://<server>:<port>/sap/xi/engine?type=entry
„ In this case, the <port> above refers to the http listener port of the Internet Communication Manager
(ICM) of the Web AS. To find out the number of this port, go to transaction SMICM and choose
GotoÆServices (or Shift-F1).
„ The query string at the end of the URL would be different for other pipeline entry points; for instance, if a
document was sent from the Integration Server to the pipeline on an Application System, the URL would
be
y http://<server>:<port>/sap/xi/engine?type=receiver (this is mentioned for
„ After installation of the XI on Web AS, all of the appropriate ICF services (for instance, for enabling the
full functionality of the monitoring architecture) must be activated in transaction SICF. For more
information on enabling these services, refer to the units on installation and monitoring.
„ Because the pipeline is based on ABAP Objects technology, the Exchange Infrastructure inherits the
robustness, flexibility, scalability, and power of the SAP Application Server (also known as SAP Basis).
 Usage of the Web Application Server in XI (III)

Transaction SXI_CACHE
© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille

„ Configuration Objects from the Integration Directory are cached at the Web Application Server for fast
access at runtime.
„ The cache can be viewed and managed in transaction SXI_CACHE.
„ For instance, a cache refresh (either a delta or a full refresh) can be started inside this transaction.
„ Connection Data for configured Adapter Engines are also cached; to see this information, from the menu
in SXI_CACHE choose GotoÆAE Cache.
 Summary

You should now be able to:

z Describe the XI Architecture in detail
z Name all of the components of the XI
z Detail the functionality of each component
z Explain the role of the SAP Web Application Server
in the XI architecture
z Describe the role of Java Web Start for the XI
development environment

© SAP AG 2004, XI Technical Architecture Overview, Paul Médaille