- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
flow XI
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 05-16-2008 6:36 AM
what is the XI flow
- SAP Managed Tags:
- SAP Process Integration
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
refer this blog..
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
regards,
pradeep A.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (10)
Answers (10)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Satya
If your new SAP XI , then its better to read TBIT. Below are the links of TBIT
which are very helpful in understanding the End-to-end process of XI. And you can even do some exercies here which very helpful.
after this you must be knowing what is xi flow...
TBIT40:
https://websmp109.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT40
TBIT41:
TBIT42:
TBIT43:
http://www50.sap.com/useducation/curriculum/course.asp?cid=60161651
TBIT44:
https://websmp102.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT44
also follow these simple scenarios
1. Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part I /people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
2. Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part II /people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
3. Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III /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
regards
sandeep
if helpful kindly reward points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Pipeline is the term used to refer to all steps that are performed during the processing of an XML message.
A pipeline represent a fixed processing run for particular XML messages and differs from other pipelines depending on the configuration of the Integration Engine. There are pipelines for a local Integration Engine in the sender or receiver system, or for a central Integration Engine that is configured as the Integration Server, for example.
The individual processing steps that an XML message must pass through when it is processed are called pipeline elements. Each pipeline element calls exactly one pipeline service.
Pipeline services provide functions for processing XML messages. They read and can change inbound XML messages, for example, the mapping or routing. They can also call processing processes, for example functions to create business data in an SAP component. The service type, number, and sequence are specified for each pipeline and cannot be changed.
The pipeline services are either part of the Integration Engine itself or originate from other areas of the SAP Exchange Infrastructure. A pipeline service can be used by more than one pipeline element.
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the system that participates in the exchange of the message.
b) Interface Detremination:
For each receiver determine which interface will should receieve the message.
c) Message Split:
If more than one receievers are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.
Refer to this link for more details;
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714f85ffc11d5b3ea0050da403d6a/content.htm
Message flow:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Satya,
<b>Simply Check these Links</b>
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
*********Reward points,if found useful
Edited by: BVS on May 16, 2008 9:37 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
HI satya
PIPELINE:
XI messages are passed through a series of processing steps called xi pipeline. A pipeline service is an abap object class that performs a particular processing step on a message. All the messages that are received at the integration server are processed in a consistent way.
URL for sending a message to a pipeline is:
http://<host>:<port>/sap/xi/engine?type=entry
PIPELINE Steps:
Receiver Identification:
To determine which systems should participate in an exchange with the incoming message.
Interface Determination:For each receiver system determine which interface should receive a message.
Message Branch:
If multiple receivers are found, XI instantiate a new message for each receiver
Request Message Mapping:
Call the mapping program to transform the message structure to the receiver format.
Outbound Binding:
Bind a specific destination and protocol to the message.
Call Adapter:
Send the transformed message to the adapter or proxy.
u can refer below links for further refrence
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714f85ffc11d5b3ea0050da403d6a/content.htm
Message flow:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
cheers
reward points if found useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
The flow is as follows,
1.File picked by the adapter,at the A.E it converts to XML format.
2.Generate a msg ID for the file and creates XI header to that file using CPA cache. CPA cache will be having the
information about all the Control(address) data.
3.Module processor
4.The file goes to send queue by the adapter engine, that file will be picked by the internal XI adapter and the file
will be forwarded to the Integration engine.
5.Pipeline steps follow the Integration Engine.
Receiver determination, Interface determination, Msg split, Msg mapping, Logical routing, Receiver aggrement, call adapter
6.The file will go to receive queue, which was taken and forwarded to the adapter engine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Satya,
Process flow diagram
The diagram which represents the message flow in XI (IE AE and in BPM ).
hope this may help ful
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
Pipeline is the term used to refer to all steps that are performed during the processing of an XML message.
A pipeline represent a fixed processing run for particular XML messages and differs from other pipelines depending on the configuration of the Integration Engine. There are pipelines for a local Integration Engine in the sender or receiver system, or for a central Integration Engine that is configured as the Integration Server, for example.
The individual processing steps that an XML message must pass through when it is processed are called pipeline elements. Each pipeline element calls exactly one pipeline service.
Pipeline services provide functions for processing XML messages. They read and can change inbound XML messages, for example, the mapping or routing. They can also call processing processes, for example functions to create business data in an SAP component. The service type, number, and sequence are specified for each pipeline and cannot be changed.
The pipeline services are either part of the Integration Engine itself or originate from other areas of the SAP Exchange Infrastructure. A pipeline service can be used by more than one pipeline element.
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the system that participates in the exchange of the message.
b) Interface Detremination:
For each receiver determine which interface will should receieve the message.
c) Message Split:
If more than one receievers are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.
Refer to this link for more details;
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714f85ffc11d5b3ea0050da403d6a/content.htm
Message flow:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Satya,
what is XI-Flow ?
XI Flow is nothing but the basic steps which the message follow's or goes to various steps to reach target system from source system ..............and there are many blogs in SDN u just need to search them .........!
Regards,
Aziz khan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Satya,
XI Flow- It will consumes XML Messages and it will produce the XML Messages.
They are two types of communication
Proxy communication : if the application XML protocol we can use the proxy communication
Adapter communication: if the application not in XML protocol
we can use adpter to convert the XML.
Adapters are: FILE,SOAP,RFC, IDOC, XI..
Regards,
Sateesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Pipeline Steps called flow of XI .....
Hoe XI will pick up any message and Transfers explained in below.......
1. For the message to be picked up by the communication channel, the channel should be associated with a
sender agreement. Mere creation of a communication channel be doesn’t ensure the message to polled
and picked up by the adapter. The message reaches the adapter in its native message format. As the
communication in SAP XI happens in XI message format, a module inside the adapter converts the
message in native format into XI message format.
2. During this process, a message ID is generated for the message. To build the XI header (sender
agreement details like the sender system, sender message interface and the interface namespace) the
details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration
object details that have been created using the configuration time. The details are updated into the
runtime cache when you activate the Configuration objects in Integration builder –Configuration time.
This cache is referred to as CPA cache).
3. This message is then sent to module for further processing. During the process of sending the
message to module processor, the message “Application attempting to send an XI message
asynchronously using connection AFW” is logged.
4. The module processor performs steps like structure conversion, communication channel specific
conversions (that have been specified in the “module tab” of the adapter channel). These conversion
modules are executed in the same sequence as mention in the communication channel.
5. After the successful execution of the conversion modules, the appropriate module (call SAP adapter
module) of the module processor is called which will send this message for persistent storage. This
message is put into the Send Queue of the messaging system for further processing. Messages like
“Message trying to put into the send Queue” and “Message successfully put into the queue” are logged
during this process. A confirmation message (success/ failure) is sent back to the sender application at
this stage. This confirmation message is used by the channel to perform various steps like deleting the
file that has a processing mode as delete.
6. The message that has been put in the Send Queue has to be picked up and sent to the Integration
Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication
purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this
process, the status of the message is set to DLNG and. Messages like “The message was successfully
retrieved from the send queue and message status set to DLNG”are logged.
7. The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with
which the Adapter framework has register itself.
8. On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL
(http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message
“The message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry
using connection AFW” is logged and the message statues is set to DLVD means message has been
successfully delivered to the endpoint( XI IS in this case).....
Regards,
Raj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi
i think previously u posted the same question,
there i have given the message flow in xi...with link...if it is not then check the flow of data thru pipeline steps
Pipeline :
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the system that participates in the exchange of the message.
b) Interface Detremination:
For each receiver determine which interface will should receieve the message.
c) Message Split:
If more than one receievers are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.
Note: reward points if solution found helpfull
Regards
Chandrakanth.k
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Supporting Multiple API Gateways with SAP API Management – using Azure API Management as example in Technology Blogs by SAP
- SAP Build Process Automation Pre-built content for Finance Use cases in Technology Blogs by SAP
- Start page of SAP Signavio Process Insights, discovery edition, the 4 pillars and documentation in Technology Blogs by SAP
- Exploring Integration Options in SAP Datasphere with the focus on using SAP extractors - Part II in Technology Blogs by SAP
- SAP Application User provision based on Application Role via Entra ID in Technology Q&A
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.