Job Tuning

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

See "Engine and Job Tuning" in TIBCO ActiveMatrix BusinessWorks Administration for related information about job tuning.

The number of messages processed concurrently by the Invoke Oracle Tuxedo service is dependent on the number of threads available in the TIBCO ActiveMatrix BusinessWorks engine. As the TIBCO ActiveMatrix BusinessWorks engine is scaled, the Invoke Oracle Tuxedo service would be scaled accordingly.
Note: When configuring the number of threads per TIBCO ActiveMatrix BusinessWorks engine and/or number of TIBCO ActiveMatrix BusinessWorks appnodes, you need to consider the number of Oracle Tuxedo Jolt Clients that can be accepted concurrently by the Oracle Tuxedo Server. For tuning the number of Oracle Tuxedo Jolt Clients, refer to following.

Tuning the Number of Oracle Tuxedo Jolt Clients

On Oracle Tuxedo Server side, the parameters mentioned below need to be considered in the UBBCONFIG file.

  • To enable Oracle Tuxedo Jolt Clients to join an application, specify the MAXWSCLIENTS parameter in the MACHINES section of the UBBCONFIG file. MAXWSCLIENTS tells the Oracle Tuxedo system at boot time how many accesser slots to reserve exclusively for Oracle Tuxedo Jolt Clients.
  • To join Oracle Tuxedo Jolt Clients to an application, specify the Oracle Tuxedo Jolt Server Listener processes in the SERVERS section of the UBBCONFIG file and set the proper values for the option -m and the option -M in the CLOPT command line options.