Administration Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

BEA TSAM Manager

This topic contains the following sections:



The BEA TSAM Manager is the data manipulation and representation component of BEA TSAM. It is a J2EE application. The BEA TSAM Manager provides the following functionality:

The BEA TSAM Manager ships with Apache Tomcat as the Java application server. “tsam” is the Web application name. The BEA TSAM Manager requires JRE 1.5 or above.

BEA TSAM Data Server

The BEA TSAM Data Server is the communication interface to BEA TSAM Agent. It includes two key servlets:

For more information, see the BEA TSAM Deployment Guide.

Note: From an HTTP perspective, the BEA TSAM Agent LMS is the HTTP client, and the BEA TSAM Manager is the HTTP server. If a firewall is deployed between the BEA TSAM Manager and Tuxedo applications, the firewall must allow the LMS to issue HTTP requests to the BEA TSAM Manager.


BEA TSAM uses a relational database to store the following information:

The BEA TSAM Manager includes Apache Derby as the default database (for evaluation purposes). Oracle database are also supported by using pre-built SQL script (An Oracle database is not included with BEA TSAM Manager). For more information, see the TSAM Manager Deployment Guide.

BEA TSAM Console

TSAM Console is the Web application which provides a GUI interface for administration and data presentation. For more information, see the BEA TSAM Console User Guide.


Configuring BEA TSAM Manager

All configuration parameters for the BEA TSAM Manager are located in the

web.xml file(short for <TSAMDIR>/apache-tomcat-5.5.17/webapps/tsam/WEB-INF/web.xml) and faces-config.xml file (short for <TSAMDIR>/apache-tomcat-5.5.17/webapps/tsam/WEB-INF/config/faces-config.xml).

Table 3-1 and Table 3-2 provide detailed web.xml and faces-config.xml configuration information.

The BEA TSAM Manager runtime log is based on Jarkata commons logging with Apache log4j as the logging implementation. The log setting file is located at: apache-tomcat-5.5.17/webapps/tsam/WEB-INF/classes named

For more information, see the Apache log4j Web site.

Table 3-1 web.xml Configuration
Specifies how long TSAM Manager temporary image files remain in the file system (in minutes).
JDBC connection string for TSAM Manager database.
Derby Example: jdbc:derby://localhost:1527/tmonitordb
Oracle Example: jdbc:oracle:thin:@localhost:1521:orcl.
TSAM Manager database connection user name.
TSAM Manager database connection password.
Active interval (in seconds) for TSAM Manager house keeping thread.
Specifies how long active monitored application data are cached (in seconds). The default value is 600 seconds, or 10 minutes.
Specifies how long finished monitored application data are cached (in seconds). The default value is 1800 seconds, or 30 minutes.
Specifies the size of the cache which holds active and finished monitored application data. The default value is 1000.
Specifies the time-out value (in seconds) for communication originated from TSAM Manager to Tuxedo. The default value is 30 seconds.

Table 3-2 faces-config.xml Configuration
Time Zone
Specifies the TSAM Manager time zone date/time fields. Attribute: “timeZoneID” for “util” bean.
If not set, the default time zone (where TSAM Manager is located) is used.

Notes: When you want to customize the BEA TSAM Manager use web.xml and faces-config.xml as templates. Remember to backup these file before changing their configurations
Note: There are other configuration settings in web.xml and faces-config.xml that are not included in this document. It is strongly advised that you do not alter these settings. If these settings altered, BEA TSAM Manager may function incorrectly or not function at all.

  Back to Top       Previous  Next