
Message packaging in the Business Process Engine (BPE) improves inbound processing performance. To be able to take advantage of message packaging for integration processes, you must activate it globally for the BPE and individually for the process types that message packaging could be useful for. The process type corresponds to a workflow task. Using the configuration parameters, you can configure message packaging so that it suits your requirements.
More information: Message Packaging for Integration Processes
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 .
You need the PI release SAP NetWeaver 7.0 Support Package Stack 13 or higher to be able to activate message packaging for integration processes.
You must activate message packaging globally for BPE at the process type level to be able to use message packaging for integration processes. Follow the procedure below:
It is important that the packaging job runs regularly as scheduled so that the message packaging for integration processes is executed successfully. For this reason, the packaging job has the job class A. We recommended that you reserve at least one batch process for jobs with job class A (transaction RZ04) so that you avoid a blockage of all batch processes due to long-running batch jobs of lower job classes.
Message packaging is not activated by default.
For more information on message packaging parameters, see the next section Configuring Message Packaging.
When the reconfiguration phase is completed, incoming messages are processed using message packaging.
Once you have activated message packaging for the BPE and the process type, there are further configuration options for configuring the inbound processing for the individual process types that are available to you.
The following settings are available in message packaging:
The first two criteria both determine when a message package is considered to be complete because it has reached the defined size limit, either with the maximum number of messages or the sum of the message sizes. The maximum wait time restricts the latency time. Before the maximum wait time of at least one unpackaged message is exceeded, the first two criteria alone determine whether a message package is complete and can be sent to inbound processing by qRFC. These criteria restrict the amount of memory required. In the remainder of this documentation they are referred to as size-restriction criteria.
To deactivate one of the criteria, set the value to 0.
For more information on latency in message packaging, see Using Message Packaging Correctly .
Example
During a packaging job run, a message package is created that is not complete with respect to the Maximum Number of Messages and Maximum Package Size size limit criteria. In addition, the maximum wait time is not exceeded for any of the messages it contains. In this case, the incomplete message package is not transferred to the inbound processing during the packaging job.
This situation may have changed when the next packaging job is run.
The inbound processing monitoring function (transactions SWF_INB_MON and SWF_INB_ADM) help you to optimize the message packaging configuration.
More information: Monitoring Message Packaging