This topic contains the following sections:
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:
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.
Note: | From an HTTP perspective, the Oracle TSAM Agent LMS is the HTTP client, and the Oracle TSAM Manager is the HTTP server. If a firewall is deployed between the Oracle TSAM Manager and Tuxedo applications, the firewall must allow the LMS to issue HTTP requests to the Oracle TSAM Manager. |
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.
The Oracle TSAM Manager runs in a Java application server. The supported Java application servers include Oracle WebLogic Server, Oracle OC4J and Apache Tomcat.
Oracle TSAM uses a relational database to store the following information:
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.
All configuration parameters for the Oracle TSAM Manager are located in the
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:
tsam/WEB-INF/classes/log4j.properties
.
For more information, see the Apache log4j Web site.
Notes: | When you want to customize the Oracle 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, Oracle TSAM Manager may function incorrectly or not function at all. |