This test helps you in 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.

This page depicts the default parameters that need to be configured for the TuxedoClientTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the full path to the installation directory of the Tuxedo Domain server in the TUXDIR text box. 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 in the APPDIR text box. For example, 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 of the TUXCONFIG file in the TUXCONFIG text box. For example, while monitoring a Tuxedo server on Windows, your TUXCONFIG can be: E:\oraclehome\tuxedo11gR1\samples\atmi\simpapp\tuxconfig

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.