Skip to Content

Tuning parameter* *


In addition of part 1  (RFC Quota) and part2  (RFC Quota Part 2), I will discuss Tuning category. We can set the number and type of queues available in Web As for processing the message using SXMB_ADM using various parameters inside the tuning category.


 The number of XI processing queues depends on the following:            

    • Ability and performance of receiver applications (for outbound queues)



:Determines the level of parallel processing for messages with quality of service Exactly Once (EO).

If the parameter in the central Integration Server has the value n, then an inbound EO message is put in a queue with the name <prefix>< number>, where<number> is a four figure random number between 0 and n-1 that is determined at runtime, and <prefix> is the corresponding 4 figure queue prefix. The same applies to the Integration Engine. If the central Integration Server and local sender and receiver clients are installed in various clients in a system, then you can set the parallel processing level for the sender, central, and receiver queues separately by using the subparameters SENDER, CENTRAL, RECEIVER, SENDER_BACK, and RECEIVER_BACK.

(i.e. s=sender, I=central, R=Receiver, B=Sender and reciver Ack Queues)                                                         

Set the parallel processing level on the central Integration Server to a level so  that it roughly corresponds to the arrival rate of messages with quality of service Exactly Once (EO).

example Queue name: XBTI0,XBTI1,XBTI2,XBTI3

 Possible Values 1 – 10,000



: enables you to schedule the parallel execution of messages with quality of service Exactly Once (EO) that have been sent by a specific sender system in separate sender-specific queues on the Integration Server and in the sender and receiver system.

The parameter EO_INBOUND_PARALLEL_SENDER enables you to prioritize messages from particular sender systems by using separate queues to process them

to define sender/reciever id from transaction SXMSIF

 Possible Values 1 – 10,000

EOINBOUND_TO_OUTBOUND_ :defines whether messages with the quality of service +Exactly Once +(EO) that are not branched are completely processed in inbound processing (value 0) or whether they are put in special separate outbound queues for outbound processing following receiver determination (value 1).

 Possible Values 0 or 1

EOOUTBOUND_PARALLEL_ :determines the parallel processing level of outbound processing of messages with the quality of service +Exactly Once +(EO) on the Integration Server.

SAP recommend that you set the parallel processing level on the central Integration Server to correspond to the performance of and the burden on the receiver systems involved.


:determines the level of parallel processing for outbound processing on the Integration Server for messages with the quality of service Exactly Once (EO) that are changed to quality of service Exactly Once In Order (EOIO) following logical routing.This occurs when a message with the quality of service EO is split into multiple messages that are sent to the same receiver system (interface split), and where the sequence of interfaces has to be taken into account .

ISRETRY_LIMIT_ :contains the total number of retry attempts if a retry-enabled error occurs during asynchronous processing and the error is set to retry-status in the queue.

Possible Values 0 to 100


:enables serial processing of messages of a particular size. This applies for messages with the quality of service +Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.</p><p>The queue name is XBTL.</p><p>Possible Values  0 – 2,097,151 (KB)</p><p><u>EO_MSG_SIZE_LIMIT_PARALLEL</u>:efers to the parameter explained above EO_MSG_SIZE_LIMIT. This parameter enables you to further improve the way that the main memory is burdened, by processing large messages (messages that exceed the value set in EO_MSG_SIZE_LIMIT) in parallel.</p><p>The value (n+) determines the level of parallel processing; the extra queue for large messages is given a number (0 to n-1) as a suffix, for example, XBTL0001.


BEO_IN_PARALLEL:_ ensures an even distribution of the entries of the queues that are determined by the parameter EO_INBOUND_PARALLEL. The value gives the maximum number of entries that can be reached for each queue.

For example, there are two queues: XBTI0001 with 5000 entries and XBTI0002 with 10 entries. If the parameter value is 3000, once it is activated, both queues will have approximately 2500 entries. The entry is activated by the parameter BALANCING

Possible Values  1 – 100,000

BEO_OUT_PARALLEL_:ensures an even distribution of the entries of the queues that are determined by the parameter EO_OUTBOUND_PARALLEL.

Possible Values  1 – 100,000

BEO_IN_PARALLEL_SENDER_:ensures an even distribution of the entries of the queues that are determined by the parameter EO_INBOUND_PARALLEL_SENDER

Possible Values  1 – 100,000

BALANCING:activates the entries for the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL, and B_EO_IN_PARALLEL. If the queues are redistributed,  it is automatically deactivated so that the messages can be processed ‘normally’ again.  To prevent locking conflicts, therefore, exit the editing mode for configuration maintenance once you have set the parameter.

Possible Values  0 (deactivated), 1 (activated)

MINPACK_SIZE_:is used in message packaging. It gives a minimum package size as a % of the value of the maximum filter-specific package size, and is only evaluated in immediate message packaging.

You can also set this parameter using transaction SXMSFILTER.

Possible Values  0 – 100

<u>Practical: </u>


Start from transaction SXMB_ADM






Go for integration Engine Configuration :




Select category as tuning




choose the specific configuration




here you can updated the Tuning Parameter :




Available Parameter and subparameter :





For defining the message filtration excute transaction SXMSFILTER.

From here you can go to jobs , sender/receiver ID  as well as you can set the package size.





Jobs :



Sender/receiver( you can also go with transaction  SXMSIF)



Message filter :



To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Dijesh Tanna
    Hi Sunil,
    First of all nice blog for tunning..

    Secondly , We are currently facing performance problem at ECC side and want to process messages in parallel mode. By default different messages are assigned to 6-7 different queues (XBTR* ).

    However the distribution is uneven, XBTR0000 have 8 messages assigned to it while other queues have only  2 messages.

    Should I use EO_INBOUND_PARALLEL with sub paramete Receiver to increase the no of queues (may be 50 or 100 ) and than B_EO_OUT_PARALLEL to evenly distribute the messages ?

    Thanks & Regards,
    Dijesh Tanna.


Leave a Reply