Tuxedo Transactions Test

The BEA Tuxedo transaction management server, named TMS, is responsible for coordinating global transactions, on behalf of BEA Tuxedo applications, from their point of origin—typically on the client—across one or more server machines, and then back to the originating client. TMS tracks transaction participants and supervises a two-phase commit protocol, ensuring that transaction commit and rollback are properly handled at each site.

To measure the load on the TMS, you need to know how many transactions are being handled by the TMS and what is their current state - whether they are being committed? rolled-back? aborted?. This can be achieved using the Tuxedo Transactions test. This test reports the number of transactions currently handled by TMS, and reveals the state of each transaction. 

Target of the test : A Tuxedo Domain Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the Tuxedo Domain server being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed


The host for which the test is to be configured.


The port at which the specified host listens. The default port is 12345.


Specify the full path to the installation directory of the Tuxedo Domain server. For example, while monitoring a Tuxedo server on Windows, your TuxDir can be: E:\oraclehome\tuxedo11gR1


Specify the full path to the application directory of the Tuxedo Domain server. For example, while monitoring a Tuxedo server on Windows, your appdir can be: E:\oraclehome\tuxedo11gR1\samples\atmi\simpapp


Each BEA Tuxedo domain is controlled by a configuration file in which installation-dependent parameters are defined. The binary version of this configuration file is called TuxConfig. The TUXCONFIG file may be given any name; the actual name is the device or system filename specified in the TUXCONFIG environment variable. Specify the name of the TuxConfig file here. For example, while monitoring a Tuxedo server on Windows, your TuxConfig can be:E:\oraclehome\tuxedo11gR1\samples\atmi\simpapp\tuxconfig

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates the number of transactions currently handled by the server.


A high value for this indicates heavy load on the TMS. To know which transactions are currently being serviced by TMS and what their status is, use the detailed diagnosis of this measure. The detailed diagnosis reveals the Global_Transacation_Identifier, Machine_Id, Transaction_status, and Group_count. A transaction can be in of the following states: