Introduction to SAP XI Message Pipeline Processing

An XI message is created when a Sender Communication Channel receives a payload either while listening to a source system or by polling (fetching) from a source system. The message will pass through several steps where the determination of its destination(s) and changes to its structure/values will happen.

The Integration Engine processes the message in a step by step (pipeline) process. The following are the most important steps executed by the central pipeline:


PLSRV_RECEIVER_DETERMINATION and PLSRV_INTERFACE_DETERMINATION
The Sender CC is just the starting point. Based on the CC and the message, the group of objects (interface) involved in the processing of the message and the destination where the message ends up must be determined in XI.
The receiver determination and interface determination steps find out the details of the receiver system and the interface for a message. The receiver can be a constant one or calculated dynamically based on the payload.

PLSRV_RECEIVER_MESSAGE_SPLIT
If the message is being sent to multiple receivers, it will be branched to its multiple destinations at this step. The term split should not be mistook as partitioning of the message contents.

PLSRV_MAPPING_REQUEST
The message may require changes to its structure or values to meet the design needs. These structural/value changes are done by mapping objects. The mapping can be done in ABAP or Java.
Typically, mappings are designed to be carried out in Java as it is faster and design is relatively easy.
If Java mapping is used, the message is sent from IE to AE via RFC Program ID AI_RUNTIME_JCOSERVER (SM59).
Not all messages require changes in their structure or values. If there is no change, mapping will not happen.

PLSRV_OUTBOUND_BINDING and PLSRV_CALL_ADAPTER
These are the stages where message is handed over to its receiver adapter (or to BPE for further processing) from where it will be posted to its receiver system(s).

A successful execution of these steps concludes the pipeline processing in Integration Engine.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more