Message Packaging 

You can improve the performance of message processing in SAP NetWeaver Process Integration (PI) by grouping together asynchronous messages in packages and then processing each message package in one LUW.

Semantically speaking, each package contains individual, unrelated messages. They are saved to the database individually; no special package archiving function is available.

Messages can end up in various different packages while they are being processed because a new package is created for each processing step.

You configure how packages are created in the sender system and in the central Integration Engine. Packages can be received and saved in the receiver system. They are then processed as individual messages.

Sender adapters handle message packages in different ways.

●      The Advanced Adapter Engine can receive packages but not create them.

The Advanced Adapter Engine will be referred to simply as the Adapter Engine in the remainder of this document.

●      The Business Process Engine (BPE) can process packages (more information: Message Packaging for Integration Processes).

●      The IDoc adapter sends all messages that have the same interface to the Integration Server in one RFC call. It can send IDoc message packages to an IDoc receiver.

When sending IDoc message packages, SAP recommends using message packaging in preference to the function for activating IDoc message packages (transaction IDXPW) because you do not need to make any additional configuration settings and because there is no delay in message processing.

●      The plain HTTP adapter cannot process packages.

●      The Web service runtime can receive packages but processes the messages individually.

The messages are transferred to the mapping as a package; however, they are actually processed individually. Message-based message packaging is possible for all receiver adapters that support message packaging.

More information:

●      Activating Message Packaging      

●      Configuring Message Packaging       

●      Monitoring Message Packaging      

The way you organize the involved queues has a significant effect on the improvement in performance that you achieve when using message packaging.

●      Exactly Once In Order (EOIO) Queues

If the application uses lots of queues and each queue only contains a few entries, improvements in performance will be limited because packages are created based on the contains of a queue; consequently, only small packages can be created in this case.

It is therefore better to use fewer queues, and to use queues in which there is a large buildup of messages. More information: Changing the Number of EOIO Queues.

●      Parallel Exactly-Once (EO) Queues

If you have too many parallel queues configured for a particular receiver, this can limit any improvements in performance from packaging because none of the queues will contain a large buildup of messages. Consequently, you are advised to use fewer queues.

●      Homogenous Messages

To simplify the creation of packages, where possible, configure your queues so that as many messages of the same type as possible are processed in one queue.

If you are using principal propagation, note that messages with different user identities cannot be processed in the same package.