cancel
Showing results for 
Search instead for 
Did you mean: 

XI - what`s it all about?

Former Member
0 Kudos

When installing auto-id there is XI required.

Is there no possibility to communicate between mit R/3 and the Netweaver (AII) without XI?

What does the XI do?

I think it bases on all the message types and basic types and imho there should be a way without XI to work properly?

Which job does XI have in this scenario and why is it obligatory?

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos
former_member193376
Active Contributor
0 Kudos

Hi

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:

● Modeling and design of messages, transformations, and cross-component integration processes

● Configuration options for managing collaborative processes and message flow

● Runtime for message and process management

● Adapter Engine for integrating heterogeneous system components

● Central monitoring for monitoring message flow and processes

SAP XI supports internal company scenarios and cross-company scenarios.

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.

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.

Simple message processing on the Integration Server is stateless. This means that the Integration Server does not know of any connections between various messages. Cross-component integration processes, on the other hand, describe related processes, which can use the knowledge about messages that have already been processed to further control the process (for example, waiting for the corresponding response for a message in order to start further actions). You can use SAP XI to model, change, and manage these cross-component integration processes centrally. These processes are executed on the Integration Server and are included in message processing by configuration.

As with cross-component integration 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.

This link may help you

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

Hope this clears your doubts

Thanks

Saiyog

Former Member
0 Kudos

HI

A Middleware solution that provides out of the box integration scenarios eliminates the need to hard code point to point connections between applications or businesses.

A successfully integrated enterprise can reward your organization with significant cost, resource, and time savings. Enterprise Applications Integration (EAI) connects existing and new systems to enable collaborative operation within your entire organization.

A successfully integrated system allows information to work harder and smarter, increasing the speed of business reaction time, and facilitating seamless, straight-through transaction processing

Sap XI

XI is well suited for connecting SAP systems with each other and with non-SAP. SAP XI provides an integrated workflow engine that allows defining adapters to non-XML protocols and mappings to convert data content from source to target format.

XI comes handy particularly incase of SAP - Non SAP interfaces where you can import standard integration content. Also XI has got sophisticated open standard adapter framework which is very easy to implement and custom logic can be implemented using Adapter module programming.

Advantages

u2022 Monitoring is better than any other middleware product. It offers exhaustive monitoring features like message, performance, component monitoring etc, all of which can be used to track and rectify the errors. It follows a hub and spoke model.

u2022 When you need to integrate with an SAP system XI has an advantage in supporting various SAP components and so on.

u2022 Process functionalities inside XI to modify content in the communication channel on own defined rules for business purposes.

u2022 Mappings and adapters are good as comparable with any other middleware product.

u2022 Synchronous & Asynchronous communication is possible.

Dis-Advantages

u2022 Web methods are particularly good if u have B2B kind of communication with their Trading Partners product.

u2022 XI is lacking full-fledged Message Queue compared to other established Middleware products.

u2022 It lacks in ability to process huge messages but SAP is working on that.

u2022 It does not have a messaging layer exposed by APIs like IBM MQ-Series.

u2022 It is not comparable to Tibco in terms of speed.

u2022 SAP relies on other vendors except for a few adapters

Welcome to XI, but before posting queries please refer to the earlier blogs/ forms for materials,

refer these links and blog in it to gain knowledge of SAP XI.

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

/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/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i

What is XI?

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

What is IR and ID?

http://help.sap.com/saphelp_nw04/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/content.htm

Runtime

http://help.sap.com/saphelp_nw04/helpdata/en/2e/278a8363b5ac4483dc1efc382e51df/content.htm

Good Blog for new to XI:

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

XI u2013Starter

http://help.sap.com/saphelp_nw04/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm

SAP XI - Where to Find Information

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/sap%20xi%20-%20...

All the information you need in XI :

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

Understand the Architecture of XI

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

You can also go through the url for Elearning :

https://www.sdn.sap.com/sdn/elearning.sdn

https://www.sdn.sap.com/irj/sdn/sdnpilot/elearning

Following is the link for 'how to guides', A step by step guide to create scenarios:

https://websmp201.sap-ag.de/nw-howtoguides

Configuration of Adapters

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

One of the most powerful feature of XI, Business Process Management:

http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm

How the messages are delivered through XI:

http://help.sap.com/saphelp_nw04/helpdata/en/17/50d440e14f8431e10000000a1550b0/frameset.htm

cheers

reward points if found useful

Former Member
0 Kudos

In my R3 I get a status 3 and a green light, but in the Netweaver sys there is never an idoc in the products of aii. why?

i implemented the solution without XI and so I had to configure the base types and segments by myself. Do I have to consider sth. specially while doing this?

What should I configure in WE20 of netweaver?

This is not really described in the master guide. Thx in advance.

Former Member
0 Kudos

Hi Willy,

Will give a try to answer ur questions

Is there no possibility to communicate between mit R/3 and the Netweaver (AII) without XI?

--> Definitely there will be (Other then XI, TIBCO, Crossworlds are there..) , but we have to always go for the approach which is simple to implement and easy to maintain . since here you want to interact with net weaver components so XI will definitely get an edge over others.

What does the XI do?

XI is basically a message oriented middle ware which believes in SOA ( Service oriented architecture )

I think it bases on all the message types and basic types and imho there should be a way without XI to work properly?

-


>sure , i have mentioned above.

Which job does XI have in this scenario and why is it obligatory?

---> Basically here you will have to Design the objects and configure mail adapters (SCOT also...not sure though for this one..)...

Regards,

Former Member
0 Kudos

HI

XI is well suited for connecting SAP systems with each other and with non-SAP. SAP XI provides an integrated workflow engine that allows defining adapters to non-XML protocols and mappings to convert data content from source to target format.

XI comes handy particularly incase of SAP - Non SAP interfaces where you can import standard integration content. Also XI has got sophisticated open standard adapter framework which is very easy to implement and custom logic can be implemented using Adapter module programming.

Advantages

u2022 Monitoring is better than any other middleware product. It offers exhaustive monitoring features like message, performance, component monitoring etc, all of which can be used to track and rectify the errors. It follows a hub and spoke model.

u2022 When you need to integrate with an SAP system XI has an advantage in supporting various SAP components and so on.

u2022 Process functionalities inside XI to modify content in the communication channel on own defined rules for business purposes.

u2022 Mappings and adapters are good as comparable with any other middleware product.

Synchronous & Asynchronous communication is possible.

XI has following components:

1) Design and Configuration time components http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

2) Mappings

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

3) Adapters

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

4) CCBPM

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

5) Central monitoring

http://help.sap.com/saphelp_nw04/helpdata/en/7c/14b5765255e345a9e3f044f1e9bbbf/frameset.htm

cheers

reward points if found useful

former_member556603
Active Contributor
0 Kudos

Hi,

XI is the middle ware tool which is used to integrate the SAP and Non SAP system.

Purpose

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:

● Modeling and design of messages, transformations, and cross-component integration processes

● Configuration options for managing collaborative processes and message flow

● Runtime for message and process management

● Adapter Engine for integrating heterogeneous system components

● Central monitoring for monitoring message flow and processes

SAP XI supports internal company scenarios and cross-company scenarios.

XI has following components:

1) Design and Configuration time components http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

2) Mappings

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

3) Adapters

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

4) CCBPM

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

5) Central monitoring

http://help.sap.com/saphelp_nw04/helpdata/en/7c/14b5765255e345a9e3f044f1e9bbbf/frameset.htm

Thanks,

Satya Kumar

Former Member
0 Kudos

HI

hope these help u..

Thanks,

vincent.