Mapping-Based Message Packaging 

Message-based message packaging is possible for all receiver adapter that support message packaging. You can use it if n individual messages exist after a mapping-based 1:n split of the message payload. Prerequisite: All individual messages go to the same Adapter Engine or to the same Adapter (for adapters that are not run by the Adapter Engine).

In message packaging, the individual messages resulting from the message split are not persisted individually, but grouped into a message package. This is then transferred to the Adapter Engine or appropriate adapter like a normal message. This saves time and resources in message transfer.

For performance reasons, you should not request acknowledgments for message packages since, in the case of a 1:n message split, this would result in n acknowledgment messages.

You have the following options for monitoring messages from message packaging:

●      Message packages only are displayed in the monitor for processed messages (ABAP). They are highlighted in the relevant column in the list of selected messages.

When you click a highlighted entry the system navigates to the monitor for message packages where you can then display the relevant individual messages.

In turn, the relevant message package is displayed when you enter the message ID of an individual message as your selection criterion in the monitor for processed messages.

●      Only message packages are showed in message monitoring (Java) in the Integration Engine. They are highlighted in the relevant column in the list of selected messages.

If you enter the message ID of a single message as your selection criterion, the corresponding bulk message is displayed.

Conversely, if you enter the message ID of a message package as the selection criterion for an Adapter Engine, all the corresponding individual messages will be displayed.

More information:

●      Enhanced (Mapping-Based) Interface Determination

●      Developing Multi-Mappings for Message Splits