The SAP Exchange Infrastructure consists of the following components:

1.

System Landscape Directory

2.

Integration Repository

3.

Integration Directory

4.

Integration Server

5.

Integration Adapters

6.

Integration Clients

Applications need the following proxy components to use the SAP Exchange Infrastructure directly and without adapters.
-Proxy Framework
-Proxy Generator
-Proxy Runtime
Integration Server (IS):
The Integration Server is the central part of the SAP Exchange Infrastructure. It receives messages from the sender
applications and then 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 but it is the specific configuration
that activates its role as a central Integration Server.
Integration Adapters (IA):
Integration Adapters are used to convert various protocols and data formats into the Integration Servers XML based
message objects and vice versa. The Integration Server comes with some built in adapters but most adapters are additional
components.
Integration Repository (IR):
The Integration Repository provides collaboration knowledge available at design time, for example, mappings,
interfaces, and components. 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
execution.
Integration Directory (ID):
The Integration Directory contains detailed collaboration knowledge about the current system landscape around the
SAP Integration Server. It is a description of routing rules, active services, executable mappings and the specific system
landscape. The Integration Directory details the information from the Integration Repository that is specific to the
configuration.
The goal of the Integration Directory is for the customer to configure the sender.Once Integration content has been created
in the Integration repository, scenarios are configured in the Integration Directory.

Integration Repository and Directory:

The Integration Repository and Directory require specific Java client software which is stored on the Integration
Server and will be automatically installed on the client side using Java Web Start. This client software can be used during
design time to develop new interfaces and mappings and to configure services, routings and mappings.
On the client side this java application provides the user interface for working with XI Objects. On the server side it offers
services for authentication, lock management, import and export of interface objects, versioning and change management
System Landscape Directory (SLD):
The System Landscape Directory is composed of the Component Repository and the Landscape Directory. The
Component Repository includes a description of all SAP Components whereas the Landscape Directory includes a complete
description of the actually installed SAP system landscape.The System Landscape Directory can be accessed using a
standard internet browser.
Proxy Framework:
The Proxy Framework consists of the Proxy Generator and the Proxy Runtime. The Proxy Framework for ABAP (generator
and runtime) is part of the SAP Web Application Server and no specific installation is needed.

Proxy Generator for Java:

The Proxy Generator for Java is used to generate proxies (Java Classes) for application programming. It makes use of the
Integration Repository which contains all interface definitions.
Java Proxy Runtime:
The Proxy Runtime for Java is mandatory for all Java programs to exchange messages with the SAP Integration Server. In
doing so the proxy runtime converts the used java classes into XML messages. These XML messages are sent to the
Integration Server using http protocol.
Integration Server:
The Integration Server can be accessed using the standard SAP GUI frontend.

Icon Meaning
Element with more than 1 occurance
Element
Attribute
Icon Colors :
White : Optional attribute or element not assigned
Red : Attribute or element must be assigned to complete the Mapping
Yellow : Attribute or element has already been assigned but the corresponding mapping in the data-flow editor is not
complete
Green: Mapping to target field complete.

Function Categories:
Arithmetic: add, substract, equalsA, abs, sqrt, sign, sqrt, etc.
Boolean: And, Or, Not, Equals, notEquals, if, ifWithoutElse
Constants: Constant, CopyValue, sender, receiver
Conversions: FixValues, Value mapping
Date: currentDate, DateTrans, DateBefore, DateAfter, CompareDate
Node Functions: createIf, removeContexts, replaceValue, exists,
SplitByValue, collapseContexts
Statistic: sum, average, count
Text: substring, concat, equalsS, indexOf, lastIndexOf, compare, etc.
Mapping Types:
1) Message mapping:
- Graphical Design and test environment
- Queue based model allows handling of very large documents
- Extensible via Java user defined functions
2) XSLT mapping:
- Open standard
- Portable
- Extensible via java user defined functions
- Memory overhead for very large documents
3) JAVA mapping:
- Flexibility of java programming language
- Java mapping program is responsible for parsing/rendering XML
4) ABAP mapping:
-Leverage existing ABAP base
- ABAP mapping program is responsible for parsing/rendering XML
What is global container and where we use it?
Global Container enables you to cache the values that you want to read again when you next call any user-defined function
in the same message mapping. Note that the sequence in which user-defined functions are called is predefined. It depends
on the position of the target fields that the function was assigned to.
What is alert?
Alerting is a function of Runtime Workbench along with Message archiving, End-to-end monitoring, Performance Monitoring,
Cache monitoring.
Through Runtime Workbench we can access alert inbox, alert configuration.
In Process Integration with Central SAP Monitoring Infrastructure, we Drill down to individual process steps and Use SAP
Web AS Alert Framework.
Transaction ALRTCATDEF.
Alert Inbox:
The alert inbox is user-specific and displays all the alerts for each alert server that have been generated based on the alert
configuration.

An alert can be delivered to you by e-mail, fax, or SMS. In each case, you will also find the alert in your alert inbox,
irrespective of the delivery method.
Transaction ALRTINBOX.

Activities
You can execute the following activities in your alert inbox:
-

Confirm alerts and start a follow-up action

Confirmed alerts disappear from the inbox. You can also confirm alerts by e-mail, fax, or SMS. This also causes them

to disappear from your alert inbox.

-

Forward alerts to another user

Refresh the alert display

Subscribe or unsubscribe to the alert categories that you are permitted to use, in order to receive or not receive the

corresponding alerts.
-

Personalize alert delivery to meet your requirements

You can choose the type of delivery you want to use and a representative.

Transaction Codes For SAP XI:

1.SXMB_IFR -> Start Integration Builder
2.SXMB_MONI -> Integration Engine - Monitoring
3.SXMB_ADM -> Integration Engine - Administration
4.SXMB_MONI_BPE -> Process Engine - Monitoring
5.SXI_MONITOR -> XI: Message Monitoring
6.SXI_CACHE -> To Access IS runtime cache
7.IDX1-> Port Maintenance in IDoc Adapter
8.IDX2-> Meta Data Overview in IDoc Adapter
9.IDX5 -> Monitor IDoc Adapter
10.IDXP - > to monitor the message packages.
11.IDXPW - > to activate the IDOC message package
12.SMQ1-> qRFC Monitor (Outbound Queue)
13.SMQ2-> qRFC Monitor (Inbound Queue)
14.SMQR - > to register the queue
15.SMQS - > to register the destination in QOUT scheduler
16.ST03 -> workload.
17.ST06 -> stato della macchina cpu memory filesystem machine status - cpu,
18.ST22 -> dump abap (analisi di eccezioni)
19.SCC4 -> visualizza mandanti del sistema
20.SALE - ale settings
21.RZ10 - edit system profile
22.RZ70-> SLD Administration
23.SU01 -> users maintenance
24.AL08 -> list all logged users(user login logon)
25.SE01 -> manage change requests
26.SE09 -> Change Request

27.SE10 -> Change Request

28.SE11 -> ABAP Data dictionary
29.SE16-> Data Browser
30.SE24-> Class Builder
31.SE37 -> mantain funcion modules
32.SE38 -> ABAP Editor
33.SE80 -> Object Navigator
34.SE93-> Maintain Transaction Codes
35.SICF -> http server configuration
36.SMGW -> trace, alzare livello di trace.
37.PFCG -> Roles
38.TSTC -> SAP transactions codes table
39.TSTCT -> transaction descriptions table
40.STMS -> transports management
41.SPAM -> apply ABAP support packages
42.SPAU -> manage objects after apply support packages
43.SLDCHECK -> Test SLD Connection
44.SLDAPICUST-> SLD API Customizing
45.ST22 -> ABAP dump analysis
46.SPROXY-> ABAP Proxy Generation
47.ABAPDOCU -> ABAP Documentation and Examples
48.SM02-> System Messages
49.SM21 -> Online System Log Analysis (log sistema XI)
50.SM30-> Call View Maintenance
51.SM58-> Asynchronous RFC Error Log
52.SM59-> RFC Destinations (Display/Maintain)
53.SMICM-> ICM Monitor (J2EE administration)
54.BD64 -> mantain distribution model (modelli di distribuzione)
55.BD87-> Status Monitor for ALE Messages
56.WE02-> Display IDoc
57.WE05-> IDoc Lists
58.WE09-> Search for IDocs by Content
59.WE19-> IDoc Test tool
60.WE20-> Partner Profiles
61.WE21-> Port definition in XI
62.WE60-> Documentation for IDoc types
63.SWXF_PBUILDER -> for Detail BPM Process
64.WEOUTQUEUE - > to start the queue processing
SAP Exchange Infrastructure (SAP XI): XI is open & flexible. It uses web standard such as "web services description
language" (WSDL), "XML Schema Definition Language" (XSD) & "Simple Object access Protocol "(SOAP) Messaging for
describing objects & Communicating with other systems. It runs on the Application Server (SAP WEB APPs). XI is not a
single Component, But rather a collection of components that work together flexibly to implement integration scenario. SAP
XI supports internal company scenarios and cross-company scenarios.
Exchange Infrastructure can be used as a Middle ware Engine to communicate in a distributed environment. The
heart of XI is Integration Engine that is used for integrating different technologies using Standard Messaging techniques e.g
XML. Different mapping tools are available for mapping the distributed system which can be mapped without having any
expertise of Technical Details. As a real world example, XI can be helpful in integrating different banks with SAP R/3. XI

Engine also support previous releases of SAP R/3 like 4.6C and have many more adapters to communicate with legacy
systems.