Oracle TSAM Manager

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

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

Oracle TSAM Data Server

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

dataserver

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

The dataserver servlet URL must be set properly in order to work with the LMS (local monitor server). After Oracle TSAM Manager is installed the dataserver URL is: host:port/tsam/dataserver.

“host” is the full domain name or IP address where Oracle 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.

requestserver

Actively delivers requests from the Oracle TSAM Manager to the Oracle TSAM Agent. For more information, see the Oracle TSAM Deployment Guide.

Oracle TSAM Console

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

Java Application Server

The Oracle TSAM Manager runs in a Java application server. The supported Java application servers include Oracle WebLogic Server, Oracle OC4J and Apache Tomcat.

Database

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

The Oracle TSAM Manager supports Oracle Database and Apache Derby. Pre-built SQL scripts are provided to create the database schema for Oracle TSAM Manager. For more information, see the Oracle TSAM Deployment Guide.

Configuring Oracle TSAM Manager

web.xml file(short for tsam/WEB-INF/web.xml) and faces-config.xml file (short for 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 Oracle TSAM Manager runtime log is based on Jarkata commons logging with Apache log4j as the logging implementation. The log setting file is located at:

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: Oracle Example: `jdbc:oracle:thin:@localhost:1521:orcl` `jdbc:derby://localhost:1527/tmonitordb`
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.

Administration Guide