In many cases within the Business Process Engine (BPE), inbound processing takes up the largest amount of processing time. Therefore, if there is a large number of messages in BPE inbound processing, it can occur that these messages cannot be processed as quickly as required. The qRFC queues increase in size and there is a kind of message jam.
Message packaging in BPE helps improve performance by delivering multiple messages to BPE process instances in one transaction. This can lead to an increased message throughput. In some cases it can lead to an increase in the runtime for specific messages, for example the time the message must wait whilst an appropriate message package is created.
More information: Using Message Packaging Correctly
The extent of the throughput improvement that can be obtained depends on the type of scenario. Collect scenarios are particularly suitable for message packaging. This includes the scenarios Collecting and Bundling the Messages of One Interface and Collecting and Bundling the Messages of Multiple Interfaces.
For more information about the advantages and disadvantages of message packaging in different scenarios, see Using Message Packaging Correctly.
Message packaging in BPE is independent of message packaging in PI (XI), but they can be used together.
For more information on message packaging in PI, see Message Packaging.
The BPE adapter functions as before without BPE message packaging; however it can also receive PI message packages (not to be confused with BPE message packages). If BPE message packaging is activated globally, an entry is made for each message in a table, irrespective of whether message packaging is activated for that process type. The BPE adapter behaves differently depending on whether message packaging is active for the process type of an incoming message.
● Message packaging is active for the relevant process type: The message is not transferred directly to inbound processing using qRFC. Instead, the packaging job transfers the message in a package by calling the qRFC module SWF_XI_PROCESS_MSG.
● Message packaging is not active for the relevant process type: The adapter transfers the message directly to inbound processing by calling the qRFC module 'SWF_XI_MSG_RAISE_EVENT'. This is the same way the adapter behaves when message packaging is deactivated globally.
If message packaging is globally activated, you can use transactions SWF_INB_MON and SWF_INB_ADM for monitoring and administering messages.
The packaging job creates the message packages according to the configured parameters, and transfers the packages to inbound processing by using qRFC. Runtime information for all incoming messages is managed in a central database table that allows messages to be processed consistently across the various components. All the message packages that are created are also managed in a special database table.
Inbound processing functions as before without message packaging. However, when message packaging is activated globally, for process types with active message packaging, whole packages as opposed to individual messages can be processed in one transaction.