This test reports the current state of and the load on every administration server on the target Tuxedo server, so that server failures and improper load distribution amongst administration servers (i.e., services) are detected early and fixed.

The default parameters associated with this test are:

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

• In the HOST text box, specify the host for which the test is to be configured.

• Specify the port at which the specified HOST listens in the PORT text box. The default port is 12345.

• 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

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.