Tuxedo Clients Test

Monitoring the clients that are communicating with the Tuxedo server and the users who login from those clients will accurately point you to the busy users and the transaction load they impose on the server. In addition, it will also shed light on the idle users and the duration of the idle sessions, so that users who have been idle for too long a time can be isolated and their sessions terminated to avoid unnecessary resource usage. The Tuxedo Clients test provides such performance insights pertaining to every user who connects to the server from each client.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, select Tuxedo as the Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : A Tuxedo Domain Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every username:clientname connecting to the Tuxedo Domain server being monitored.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port at which the specified host listens. The default port is 12345.
TuxDir	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
AppDir	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
TuxConfig	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

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Client status	Indicates the current state of this client.	Number	The values this measure can report are as follows: idle busy transaction idle transaction busy The numeric values that correspond to the measure values listed above are as follows: Measure Value Numeric Value Idle 0 Transaction Idle 1 Busy 90 Transaction Busy 100 Note: By default, this measure reports the Measure Values discussed in the table above to indicate the current state of a client. The graph of this measure however, represents the same using the numeric equivalents only.
Total logged time	Indicates the total time for which this client was logged into the server	Mins	If any client was in the idle state for too long a time on the server, it is a cause for concern.
Begins	Indicates the number of transactions that have begun.	Number
Commits	Indicates the number of transactions that were committed.	Number
Aborts	Indicates the number of transactions that were aborted.	Number