Tuxedo Bulletin Boards Test
The BEA Tuxedo system uses the TUXCONFIG file to set up a bulletin board (BB) on each server machine in a Tuxedo domain. When a Tuxedo server process becomes active, it advertises the names of its services in the bulletin board. Some information in the bulletin board is global and is replicated on every server machine in the Tuxedo domain (for example, the names and locations of all servers offering a particular service). Other information is local and is visible only on the local bulletin board (for example, the actual number and type of client requests currently waiting on a local server request queue).
The bulletin board provides location and namespace transparency within a Tuxedo domain. Location transparency means that Tuxedo client and server processes do not have to be aware of the location of a resource within the Tuxedo domain. Namespace transparency means that Tuxedo client and server processes can use the same naming conventions (and namespace) to locate any resource in the Tuxedo domain.
Using the Tuxedo Bulletin Boards test, you can determine how many servers, services, and interfaces are registered with the BB, and what percentage of these elements are currently in use and not.
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 Tuxedo Domain server being monitored.
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 |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Total servers |
Indicates the number of servers registered with the BB. |
Number |
|
Total services |
Indicates the number of services advertised on the BB. |
Number |
|
Total interfaces |
Indicates the number of network interfaces that are registered with the BB. |
Number |
|
Current servers |
Indicates the number of servers currently available in the domain.
|
Number |
|
Current services |
Indicates the number of services currently available in the domain. |
Number |
|
Current interfaces |
Indicates the number of interfaces currently available in the domain. |
Number |
|
Current queues |
Indicates the number of queues currently available in the domain. |
Number |
|
Available servers |
Indicates the percentage of servers registered with the BB that are currently available. |
Percent |
Ideally, the value of this measure should be high. |
Available services |
Indicates the percentage of services advertised on the BB that are currently available. |
Percent |
Ideally, the value of this measure should be high. |
Available interfaces |
Indicates the percentage of interfaces registered with the BB tha are currently available. |
Percent |
Ideally, the value of this measure should be high. |