Tuxedo Domain Server Test

An administration server is a software program that performs administration functions. Each Tuxedo managed node has the following administration servers:

  • BRIDGE: An administration server that establishes the machine’s listening address.
  • Bulletin Board Liaison (BBL): An administration server that creates the shared memory Bulletin Board. Each master machine also has a Distinguished Bulletin Board Liaison (DBBL), which is an administration server that manages the updates to the Bulletin Board.

A Tuxedo managed node may have additional administration servers, such as Transaction Management Server (TMS), which handles transaction completion.

Failure of a critical administration server such as BBL can cause the activation of other administration servers on that machine to fail. If the DBBL fails to activate, the entire application's activation process will fail. It is hence imperative to continuously track the state of each administration server.

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.

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 Servername:ServerID associated with each administration server on 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

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Current server state

Indicates the current state of this administration server.


The values that this measure can report and their corresponding numeric equivalents have been detailed in the table below:

Measure Value Numeric Value
Active 100
Idle 1
Inactive 0


By default, this measure reports the Measure Values discussed in the table above to indicate the current state of a server The graph of this measure however, represents the same using the numeric equivalents only.

Requests handled

Indicates the number of requests handled by this administration server during the last measurement period.



Server load

Indicates the load on this server during the last measurement period.


Compare the value of this measure across servers to identify the server that is overloaded.