XI

[Former Member]

Dear Gurus

can any 1 tel me what is XI

[Former Member · Accepted solution]

Dear Ronan XI is Nothing But Xchange Infrastructure..which will provide u to exchange datas between SAP and any other Interface,,..

Regards

venkat

[Former Member]

Hi,

XI is the integration platform, a part of the Netweaver Stack that enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other.

SAP Exchange Infrastructure is based on an open architecture, uses open standards (in particular those from the XML and Java environments).

XI is middleware by SAP for integration. Mainly it is used if one is any SAP system and other end can be any system.

Exchange Infrastructure (XI) is an Integral part of SAP Net weaver. Position of XI is in the process integration layer of Net weaver stack.

The aim of XI is to integrate different versions of both SAP and non-SAP systems implemented on different platforms (Java, ABAP, and so on). XI enables you to implement cross-system business processes.

XI is based on an open architecture, makes use of open standards and offers services that are essential in a heterogeneous and complex system landscape: namely a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between the sender and receiver systems.

The application-specific contents are transferred from the sender to the receiver in a freely defined XML schema (XML: extended Markup Language) using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.

The central concept is that, during the design phase, all interfaces required are initially developed independently of a platform and made available in the form of a WSDL description(WSDL: Web Service Description Language). Using this description you can, for example,

define mappings between interfaces without this having an effect on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, the configuration phase, you can

select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes, and assign them to each other in logical routing. The data resulting from this configuration process is saved in the

Integration Directory and you can call and evaluate it from the runtime of the Exchange Infrastructure.

***********************************

Regards,

Irfan

Note: Reward points if found suitable.