# Administration Guide

# BEA TSAM Manager

This topic contains the following sections:

- Overview
- Configuring BEA TSAM Manager

## Overview

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:

- Communicates with the BEA TSAM Agent for performance metrics, configuration information and other utility messages.
- Maintains persistent data storage
- Provides a Web console for BEA TSAM administration, monitored data presentation and alerts management.

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:

- `dataserver`

Receives all messages from the BEA TSAM Agent. It extracts business data from the HTTP/XML body, collects the data, and stores it in the database.

- `requestserver`
- actively delivers requests from the BEA TSAM Manager to the BEA TSAM Agent. The `dataserver` servlet URL must be set properly in order to work with the LMS (local monitor server). AfterBEA TSAM Manager is installed the dataserver URL is: `host:port/tsam/dataserver`.

“`host`” is the full domain name or IP address where BEA TSAM Manager installed. “`port`” is the Tomcat listening port. “`tsam/dataserver`” is the data server fixed service endpoint. The LMS distinguishes the “requestserver” URL based on the “dataserver” URL.

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.

### Database

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

- Performance metrics collected by the BEA TSAM Agent
- Tuxedo component information from the BEA TSAM Agent
- User account information
- Alerts and events

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`log4j.properties`.

For more information, see the Apache log4j Web site.

Table 3-1 web.xml Configuration
Name | Description
--- | ---
BIRT_IMAGE_LIVETIME | Specifies how long TSAM Manager temporary image files remain in the file system (in minutes).
tsam.jdbc.url | JDBC connection string for TSAM Manager database. Derby Example:`jdbc:derby://localhost:1527/tmonitordb` Oracle Example: `jdbc:oracle:thin:@localhost:1521:orcl.`
tsam.jdbc.username | TSAM Manager database connection user name.
tsam.jdbc.password | TSAM Manager database connection password.
tsam.config.windowhs | Active interval (in seconds) for TSAM Manager house keeping thread.
tsam.config.maxappactive | Specifies how long active monitored application data are cached (in seconds). The default value is 600 seconds, or 10 minutes.
tsam.config.maxappdone | Specifies how long finished monitored application data are cached (in seconds). The default value is 1800 seconds, or 30 minutes.
tsam.config.maxappsize | Specifies the size of the cache which holds active and finished monitored application data. The default value is 1000.
tsam.config.timeoutwithtuxedo | 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
Name | Description
--- | ---
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.