xi

[Former Member]

hi all.............i m new to work on xi................plz fwd sm..................notes regarding it.................

thanks

[Former Member]

hi all.............i m new to work on xi................plz fwd sm..................notes regarding it.................

thanks

[Former Member]

Hi,

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.

ADAPTERS:

Technical Adapter:

File,

HTTP,

SOAP,

JDBC,

Mail,

JMS

Application Adapters:

SAP Application Adapters:

RFC

IDoc.

Non-SAP Application Adapters:

BAAN

Oracle,

Seibel,

PeopleSoft,

QAD MFG/PRO

Industry Standard Adapters:

CIDX Adapter by SAP

EDI Standard Adapters By SEEBURGER:

SAP XI is an integration technology and platform for

1. SAP and Non-SAP systems,

2. A2A and B2B scenarios,

3. Synchronous and Asynchronous communication,

4. Cross component Business Process management and it include built-in engine for designing and executing integration process (Business process).

5. The goal of SAP XI is to provide single point of integration of all systems inside and outside the corporate boundary across technologies and organizational boundaries.

6. The important feature of XI is openness, flexible and transparency to the integration process. It is based on ESA and SOA.

7. The overall key concept of SAP XI is to drive integrated business process across heterogeneous and highly dynamic landscapes in a more manageable cost effective way.

8. The basic idea is to provide runtime infrastructure which allows heterogeneous systems to be tied together with fewer connections and at the same time, in order to connect those applications and let messages flow from one application to other, have a centralized storage of integration knowledge.

XI Advantages over other Middleware Tools

• Pre-Delivered integration content

(Def:-SAP solutions bring their integration Meta data like CRM, SRM,SCM, xRPM, etc.) As Delivered with the integration repository of XI

Benefit:-

A) Out-of-the-box of integration solution

B) Simplified upgrade of SAP solutions

C) Versioning and modification management of integration of Meta data.

• Openness and interoperability

(Def:-Connect to existing integration solutions) like

Through JMS messaging (e.g MQ series) and SOAP.

Use open, XML standards for integration

Incorporate existing functionality in to new process (Adapters (JCA), web services(WSDL)).

Check these Links,

Definition :

/people/sap.user72/blog/2005/12/22/new-to-xi

Welcome to XI,

http://help.sap.com/saphelp_nw04/helpdata/en/80/8e3841e26cef23e10000000a155106/frameset.htm

https://www.sdn.sap.com/irj/sdn/developerareas/xi?rid=/webcontent/uuid/a680445e-0501-0010-1c94-a8c4a... [original link is broken]

This might help you

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Further, this thread deals with everything that is needed for a starter on XI. Do check them out,

/message/527697#527697 [original link is broken]

And after you are done with the documentation probably you can go through this scenario,

Also check the following threads which might help you a little more,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/13926f23-0a01-0010-149c-c11...

/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i

/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii

/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii

and once you are through ...follow the following links to weblogs which explain all the basic scenarios in XI

Following are the links to weblogs which will help to develop the basic scenarios.

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File

/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File

/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC

/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy

/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 - File to File Part 1

/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 - File to File Part 2

/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] - File to Mail

/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i - Dynamic File Name Part 1

/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii - Dynamic File Name Part 2

/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address - Dynamic Mail Address

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi - Message Flow in XI

/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM

/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM

/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM

/people/michal.krawczyk2/blog/2005/08/22/xi-maintain-rfc-destinations-centrally - Maintain RFC destination centrally

/people/sravya.talanki2/blog/2005/08/18/triggering-e-mails-to-shared-folders-of-sap-is-u - Triggering Email from folder

/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party - Handling different partners for IDoc

/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi - Modeling Integration Scenario in XI

/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible - Testing of integration process

/people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects - Authorization in XI

http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm - Authorization in XI

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config

/people/sameer.shadab/blog/2005/09/21/executing-unix-shell-script-using-operating-system-command-in-xi - Call UNIX Shell Script

/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi - Transport in XI

/people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping - Using ABAP XSLT Extensions for XI Mapping

/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure - Mail Adaptor options

/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File

/people/sap.user72/blog/2005/11/17/xi-controlling-access-to-sensitive-interfaces - Controlling access to Sensitive Interfaces

/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14 - The same filename from a sender to a receiver file adapter - SP14

/people/prasad.illapani/blog/2005/11/14/payload-based-message-search-in-xi30-using-trex-engine - Payload Based Message Search in XI30 using Trex Engine /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i - XI : Configuring CCMS Monitoring for XI- Part I

/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter - XI: HTML e-mails from the receiver mail adapter

/people/sap.user72/blog/2005/11/22/xi-faqs-provided-by-sap-updated - XI : FAQ's Provided by SAP

Thanks,

Reward If Helpful.

[Former Member]

XI - EXCHANGE INFRASTRUCTURE

SAP Exchange Infrastructure (SAP XI) 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), and offers those services that are essential in a heterogeneous and complex system landscape: A runtime infrastructure for message exchange, configuration options for managing collaborative processes and message flow, design and execution of cross-component business processes, B2B support, and options for transforming message contents between sender and receiver systems.

The following graphic is a simple overview showing how SAP XI is positioned withinSAP NetWeaver. The important components and concepts of SAP XI are shown on the right-hand side. These are described in more detail in the Overview section.

SAP XI is based on general standards so as to enable external systems to be integrated. At the center of the infrastructure is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in user-defined XML (eXtensible Markup Language) schema from the sender to the receiver using the Integration Server.

In the above graphic, Integration Broker is a requirement profile that supports SAP XI. The Integration Server, on the other hand, is an XI runtime component.

Senders and receivers that exchange messages using the Integration Server are separated from one another. This separation makes it easier to connect systems that are technologically different. Every system that can exchange messages with the Integration Server can also exchange messages with all other systems that are connected to the Integration Server. SAP XI supports the following methods of communication with the Integration Server:

· Direct communication using proxies, which you generate in the application systems using a description in WSDL (Web Service Description Language).

· Communication using adapters. In this case, you create interfaces for message exchange in the application system, or use existing interfaces.

Communication using the Integration Server is oriented towards asynchronous communication. Synchronous communication is supported, should it be required.

Simple message processing on the Integration Server is stateless. This means that the Integration Server does not know of any semantic connections between various messages. You use cross-component business processes, which are executed on the Integration Server, to describe logical dependencies between messages and define additional conditions for the message flow. You use SAP XI to model and maintain these cross-component Business Process Management processes centrally.

As with cross-component business processes, you save the entire integration knowledge of a collaborative process centrally in SAP XI: Objects at design time in the Integration Repository and objects at configuration time in the Integration Directory. In this way, SAP Exchange Infrastructure follows the principle of shared collaboration knowledge: You no longer need to search for information about a collaborative process in each of the systems involved, but can call this information centrally instead. This procedure considerably reduces the costs for the development and maintenance of the shared applications.

pLEASE REWARD IF HELPFUL.