BEA TSAM (Tuxedo System and Application Monitor) provides comprehensive monitoring and reporting for the BEA Tuxedo system and applications. It includes two components: BEA TSAM Agent and BEA TSAM Manager. For more information, see BEA TSAM Agent and BEA TSAM Manager.
The BEA TSAM agent enables collection of various performance metrics for applications, including XA and non-XA transactions, services, system servers. BEA TSAM Manager provides a graphical user interface to correlate and aggregate performance metrics collected from one or more Tuxedo domains and display it in real time.
BEA TSAM major features are:
Call Path Monitoring and Analysis
Service Monitoring and Statistics
System Server Monitoring and Statistics
Transaction Monitoring
Event Alerts
Open Plug-in Framework
Dynamic Monitoring Policy Management
Web-based Reporting and Management
BEA TSAM Software Components
BEA TSAM software consists of the following components:
BEA TSAM Agent
BEA TSAM agent enables collection of various performance metrics for applications. It includes the following sub-components:
BEA TSAM Framework
BEA TSAM Default Plug-in
LMS (Local Monitor Server)
BEA TSAM Manager
BEA TSAM Manager provides a graphical user interface to correlate and aggregate performance metrics collected from one or more Tuxedo domains and displays them in real time. It includes the following sub-components:
BEA TSAM Data Server
Derby Database
BEA TSAM Console
Installation Notes
BEA TSAM 1.1 includes two components: BEA TSAM Agent and BEA TSAM Manager.
BEA TSAM Agent is supported in the following Tuxedo releases:
Tuxedo 10.0
BEA TSAM Agent is an integral component of the Tuxedo 10.0 core installation.
Tuxedo 9.1
BEA TSAM Agent is included in Tuxedo 9.1 Rolling Patch 075 or above.
Tuxedo 8.1
BEA TSAM Agent is included in Tuxedo 8.1 Rolling Patch 332 or above.
BEA TSAM Manager is packaged with the BEA TSAM 1.1 installer. It is not mandatory to install the BEA TSAM Manager on a machine running Tuxedo.
You must ensure that the BEA TSAM Agent component is properly configured on each node to be monitored in order to use in conjunction with the BEA TSAM Manager.
The following section lists known limitations with BEA TSAM 1.1 software and include recommended workarounds. The limitations are listed by the Change Request (CR) number. The CR number is provided to facilitate the tracking of these problems.
Table 1 BEA TSAM 1.1 Known Issues
CR338151
The Call Path monitoring status never terminate if a service call is timed out or the service is running on a non TSAM supported Tuxedo node.
Problem
Usually, each service call path shown on the TSAM console should finally changed to a terminate status (either OK or Fail) to reflect the termination of the service call.
But if a service call is timed out or the service to be executed is running on a non TSAM supported Tuxedo node, the corresponding call path shown on the TSAM console will keep the active status and never change to terminate status even the actual service call is terminated.
Platform
All
Workaround
None
CR340185
The Call Path monitoring status never terminate if a tpacall() service request is cancelled by tpcancel().
Problem
Usually, each service call path shown on the TSAM console should finally changed to a terminate status (either OK or Fail) to reflect the termination of the service call.
But if a service call is initiated with tpacall() and cancelled by tpcancel(), the corresponding call path shown on the TSAM console will keep the active status and never change to terminate status even the actual service call is terminated.
Platform
All
Workaround
None
Online Documentation
The BEA TSAM 1.1 product documentation is available at
To obtain patches, access the BEA Customer Support page at http://www.bea.com/support/ and open a New Case to request the patches. BEA customers can gain access to support information by accessing the Customer Support page and registering for a Web account.
You can also contact Customer Support by using the contact information provided on the BEA TSAM 1.1 Customer Support Card, which is included in the product box.
When contacting Customer Support, be prepared to provide the following information:
Your name, e-mail address, phone number, and fax number
Your company name and company address
Your machine type and authorization codes
The name and version of the product you are using
A description of the problem and the contents of pertinent error messages
