MESSAGE PACKAGING

MESSAGE PACKAGING

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

We 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 Business Process Engine (BPE) can process packages

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

●      The plain HTTP adapter cannot process packages.

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

To use message packaging, you must first activate it.

How to Activate ?

- SXMB_ADMIN - CONFIGURATION - CONFIGURE INTEGRATION ENGINE 

- Under PARAMETER Categories select RUNTIME category

- choose change configuration

- Select the entry with the category 'RUNTIME', parameter 'PACKAGING', current value '0' (packaging deactivated), and the default '0' (no packaging).

- Set the current value to 1.

Packaging is now activated.

CONFIGURE MESSAGE PACKAGING

We can configure message packaging so that it suits your requirements. To do so, you define configuration types that you then assign to the different locations where message packaging can be used.

These are the seven locations in pipeline processing where packages can be created.

To make a global package configuration such as this more specific, you can assign a configuration type not just to a specific message packaging location, but also to a specific sender or receiver ID. This configuration type is then applied instead of the global configuration for those messages that correspond to this sender or receiver ID.

To create configuration type - 

Call SXMS_BCM and switch to change mode.

Create a new configuration type by using one of the following two methods:

○       Use the DEFAULT configuration type and modify it to meet your requirements

○       Add a new entry

To assign a configuration type to a packaging location, use transaction SXMS_BCONF.

There are three parameters that you can use to define configuration types:

●      Wait Time

Maximum wait time until the queue is processed when the maximum number of messages has not yet been reached.

●      Number

Maximum number of messages per package.

●      Package Size

Maximum total size of all messages in package in KB.

SAP ships the configuration type 'DEFAULT', which is assigned by default to all locations where packaging is possible, and which is available for all queues:

●      Wait Time: 0 seconds

●      Number: 100 messages

●      Package Size: 1000 KB

Since the wait time in this case is 0, there are no delays in message processing once packaging has been activated. The messages are simply processed quicker.

Monitoring Message Packaging

Transaction XMSPKSTATCNF to configure package statistics.

Transaction XMSPKSTATCNF to configure packaging.


                                                             

                                                            AMOR FATI - LOVE OF FATE