on 05-19-2008 5:19 AM
Hi,
plz told me about pipeline steps.plz explain in depth.
with warm regards.
vikash
HI
The Integration Engine running on the ABAP stack which process message in a consistent way using a series of pipeline steps.
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.
For further information on the Pipeline steps refer the below links
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
cherrs
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.
Hi
During processing XI messages passed through a series of processing steps called XI Pipeline.
An XI pipeline is configured series of Pipeline services; A pipeline service is an ABAP Object class that performs a particular proceaaing step on a message.
All Messages that are received at the integration server are processed in a consistent way, with a single set of monitoring and management transactions, regardless of the underlaying platform,technology, or vendor of the application systems involved in the message exchange.
The Pipeline is accessed via a URl, behind which is an ICF service. The URL sending a message to the Pipeline is
[http://<host>:<port>/sap/xi/engine?type=entry]
Important Pipeline Steps are as follows:
Receiver Identification - Determine which system(s) should participate in an exchange with the incoming message.
Interface Determination - For each receiver system determine which Interface(s) should receive a message.
Message Branch - If multiple receivers are found, XI will instantiate a new message for each receiver.
Request Message Mapping - Call a mapping program to transform the message structure to the receiver format.
Outbound Binding - Bind a specific destintion and protocol to the message.
Call Adapter - Senf the transformed message to the adapter or the proxy.
Regards
Sami
Reward points if helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
before as in the XI terms the pipeline
is a set of services that process XML messages
on the integration engine
(so after the adapter will send the XML to the
integration engine)
XI pipleine steps are-
Sender Agreement->Reciever Determination->Interface Determination->Interface Mapping->Reciever Agreement.
1) Sender adapter will poll the data into XI . This is carried out by Adapter Engine
Once it reached XI, it will in XI Message pipeline in the integration engine.
2) Reciever Determination is executed - to look into who is the reciever
3) Then Interface determination- Sender Interface and Reciever Interface Mapping
4) reciever Agreement- with adapter or proxy structure.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Detremination: For each receiver determine which interface will should receieve the message.
3) Message Split: If more than one receievers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
Hope this answers your query.
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.
Hi Vikas,
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.
When a source message reaches to the Integration server, it performs six steps before the message reaches the destination. These steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Detremination: For each receiver determine which interface will should receieve the message.
3) Message Split: If more than one receievers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
XI pipleine steps are-
Sender Agreement->Reciever Determination->Interface Determination->Interface Mapping->Reciever Agreement.
1) Sender adapter will poll the data into XI . This is carried out by Adapter Engine
Once it reached XI, it will in XI Message pipeline in the integration engine.
2) Reciever Determination is executed - to look into who is the reciever
3) Then Interface determination- Sender Interface and Reciever Interface Mapping
4) reciever Agreement- with adapter or proxy structure.
for further details refer
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.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
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.