SAP NW Newbie

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_ME...

Did you know that you can send SOAP messages directly to the Integration Engine instead of using a SOAP sender? Send the SOAP message to  http://<server>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>   to bypass Adapter Engine. You cannot use this method if you need to use modules or have more than one attachment.

When testing messages by posting xml message payload from RWB, if you encounter a 401 (authorization problem), check login/system_client is set in the instance profile. If this parameter is not set, the message is sent to 000 client by default.

If you find Archive/Delete jobs not clearing off messages (causing the Persistence Layer fill level to continuously increase); if the old messages were processed by the IDoc Adapter, check if SXMS_REFRESH_ADAPTER_STATUS job is running properly. Check its variant and see if it selects the messages properly. This job checks the status of messages that were sent to the IDoc adapter. Since the IDoc adapter does not send response messages, it is not automatically known whether a message was processed or not.

If you have a requirement to archive all the messages, you would have selected all the interfaces in SXMB_ADMIN. When new interfaces are transported into the system, they are not added to this list and the archive job skips messages for those interfaces. The list doesn't seem to accept wildcards and hence it has to be updated every time a new interface is introduced.

Message Flow from Adapter Engine to Integration Server (Ex: File Sender): Message Processing within Integration Server: Message Flow from Integration Server to Adapter Engine (Ex: JDBC Receiver):