Tuxedo Connections Test

Several types of applications require the notion of a conversation with a server during which context is kept from message to message. Application programmers can use the conversational functions to establish and maintain state-preserving connections between the requesting process and conversational server processes. Specifically, programmers can do the following:

  • Open a connection to a conversational server
  • Begin and end a global transaction during the conversation
  • Have a conversation span multiple machines and resource managers
  • Detect and provide notification of connection failures
  • Terminate the connection when satisfied that the task has been completed

A conversational server is dedicated to the originating requester for the duration of the connection; the system automatically spawns a new copy of a server if one is not available when a conversational connection is requested.

This test monitors the number of conversational connections that are currently active on the Tuxedo server.

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.

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

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

No of connections

Indicates the number of conversational connections currently open on the Tuxedo server.


Use the detailed diagnosis of this measure to view the complete details of the conversational connections. These details include the following:

  • Originator_GroupId
  • Originator_Logical_Machine_Id
  • Data_transmitted_by_originator
  • Receiver_GroupId
  • Receiver_Logical_Machine_Id
  • Data_transmitted_by_receiver
  • Service_name