Job Tuning

You can configure the SAP activities to control the number of messages being processed concurrently.

To control the number of messages being processed concurrently, you can choose the required configuration:
  • IDoc Listener and RFC BAPI Listener activities
    • Configure the Max Connections field of the referenced server connection according to the number of all the IDoc Listener and RFC BAPI Listener activities.
      Note: For the IDoc Listener activity, you not only have to consider the number of all the IDoc Listener and RFC BAPI Listener activities, but also the case of the TID management is Active.
    • Configure the RFC destination accordingly by using the SAP transaction code, SMQS.
    Note: The IDoc Listener and RFC BAPI Listener activities do not support the job tuning property, FlowLimit.
  • IDoc Parser
    • Configure the Max Session field in the activity.
      Note: The priority of the Max Session field is higher than the job tuning property, Flow Limit.
  • Invoke RFC/BAPI in SAP, Reply from RFC/BAPI in SAP, and Post IDoc to SAP activities
    • Note: Configure the RFC/BAPI No. of Threads property accordingly in the SAP Connection shared resource being used to control the number of concurrent sessions between plug-in and SAP. The number of threads configured must match the number of SAP connections configured in Max Connections field of the referenced client connection. The Asynchronous Timeout property maintained in TIBCO ActiveMatrix BusinessWorks™ needs to be maintained accordingly to avoid timeouts.
  • Kafka Message Source

    By default, only one partition is created. However, if more than one partition needs to be created, you can add it using the Kafka command.