Multithreading

Multithreading of an application allows the application to simultaneously process multiple, independent events. Multithreading is supported in both inbound and outbound services.

Multithreading in an Outbound Adapter Configuration

The scalability of the outbound adapter configuration is accommodated through the number of connections configured in the ConnectionPools tab. If you set the maximum connection number of a server connection pool to 3, three threads can be available to potentially receive messages from the SAP system. If the number of messages processed by the adapter configuration has to increase, adjust the thread count property property accordingly. You can configure this property in one of the following ways:

Specify the Max Connections field in the ConnectionPools Tab of Adapter for SAP Configuration editor.
Specify the adr3.maxconnections property in the adr3.tra file.
Specify the system:maxconnections argument from the command line.

The number of threads should be equal to the number of connections required. The maximum limit is eight threads per server connection. The maximum limit is 99 threads per server connection pool. To configure the maximum number of connections allowed, modify the profile parameter GW/MAX_CONN for the SAP application server.

For more information about the number of threads, see Server Connection Pool Configuration Reference.

Note: To take advantage of the number of connections available in the server connection pool, it is good practice that you maintain the connection count available in SAP transaction SMQS for the corresponding RFC Destination.

Multithreading in an Inbound Adapter Configuration

The scalability of the inbound adapter configuration is accommodated through the thread count configured in the ConnectionPools tab of the adapter configuration. If you set the maximum connection number of a server connection pool to 3, three threads can be available to potentially receive messages from the JMS or RV destination. If the number of messages processed by the adapter service needs to increase, maintain the thread count property accordingly.

The maximum limit is 99 threads per adapter service.

Note:

When an adapter configuration is configured in TIBCO Business Studio, all adapter services having the same messaging transport configuration can share the same session configuration. For example, if there are two Subscription Service services and the message transport is set to JMS queue, both of these services share the same JMS session by default and all threads associated with that session. Even though the services each have their own respective thread count, if the services share the same session, the total number of threads is actually used.

When configuring the thread count for an adapter service, it is good practice that you configure accordingly based on the number of connections available and the number of concurrent messages.

In the case of Subscription Service services, to receive optimal performance, it is good practice that you set the inbound partner profile in the SAP system to “Trigger by background program”. If the inbound partner profile is set to “Trigger immediately”, the client connection used by the adapter service can be potentially blocked until the processing in the SAP system is completed and prevent the adapter service from processing and sending the next message to the SAP system.

Multithreading with Distributed Queues

Request-Response Service and Subscription Service services can be run in load-balanced Distributed Queue (or RVDQ) mode. For multithreading to be enabled for such configurations, ensure that the worker tasks for worker instances are set to values greater than 1. The number of threads active in each service is equal to the adapter task set for that configuration, provided sufficient connections are created for the configuration.