Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
kenny_scott
Contributor

The process of changing the Messaging System Queue thread properties has changed with XI 3.0 SP19 / XI 7.0 SP11. Previously the queue consumer threads were adjusted in the property -


     messaging.connections

of the J2EE service

SAP XI AF Messaging

------------------------

Since XI 3.0 SP19/ XI 7.0 SP11 this has changed to the property -

   messaging.connectionDefinition

of the  service

XPI Service: SAP XI AF Core.

-----------------------------------------

(N.B.,

the Industry Standard Adapters (e.g., CIDX, RNIF) use the property -

messaging.connectionParams

of the service

XPI Service: Messaging System)

-----------------------------------------

The example below adds a new property set for the RFC Adapter. This is appended after the global AFW entry,

i.e.,

(name=global, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=5, Rqst.maxConsumers=5), (name=RFC_http://sap.com/xi/XI/System,  messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=8, Recv.maxConsumers=8, Call.maxConsumers=12, Rqst.maxConsumers=12)

If the requirement is to increase the number of threads to the same amount for all the adapter types then the queue values (e.g., Recv.maxConsumers) in the global property set can be modified.

After changing then 'Update', Save and restart the SAP XI AF Core service.

With the introduction of the Queue Separation feature each adapter type has its own queue instance and respective configurable properties. If the system has been upgraded to XI 3.0SP19/ XI 7.0 SP11 then there may be a decrease in system performance because the central AFW queue's properties :


Synchronous :

   Call.maxConsumers

   Rqst.maxConsumers

Asynchronous :

Send.maxConsumers

     Recv.maxConsumers

previously had a higher value than the current default 5,

i.e., see the note :-

#1084161 Performance decrease after applying XI 3.0 SP20 7.0 PS12



default values

             SAPXI AF Core -> messaging.connectionDefinition



new values after the global change to the Adapter consumer thread values


N.B.,

  for > = PI 7.1 systems use the configTool to change the service -

      com.sap.aii.af.svc

property -

      messaging.connectionDefinition



* Industry Standard Adapters,  use the configTool service - com.sap.aii.af.ms.svc

**

ICO scenarios only use the send (i.e., Send and Call) queues
5 Comments