|
|
This topic contains the following sections:
The Local Monitor Server (LMS) is a Tuxedo system server provided by the Oracle TSAM Agent.
To properly deploy the Oracle TSAM Agent, you must add the LMS to each Tuxedo machine section of the UBBCONFIG file. Listing 1 shows an example of how to add the LMS to the UBBCONFIG file.
...
*MACHINES
MACHINEA
...
*GROUPS
...
LMSGRP LMID=MACHINEA
...
*SERVERS
LMS SVRGRP=LMSGRP SRVID=1 MINDISPATCHTHREADS=1 MAXDISPATCHTHREADS=5 CLOPT=”-A -- -l tsamweb.abc.com:8080/tsam/dataserver”
...
LMS is multi-threaded so that you can configure the service dispatching thread number based on the Tuxedo application work load. The “-l” option specifies the Oracle TSAM Data Server address which is configured in the Oracle TSAM Manager. For more LMS information, see the
Oracle TSAM Reference Guide. The Oracle TSAM Data Server uses the same port number as the Oracle TSAM Manager Console.
| Note: | LMS can also be added to a running Tuxedo application using TMIB. |
The Oracle TSAM Manager functions as a Web application in a Servlet/JSP container. It uses DBMS (Database Management System) to store persistent Tuxedo performance and monitoring data.
You must deploy Oracle TSAM database before using Oracle TSAM Manager. If you select installing the bundled Apache Tomcat Server, Oracle TSAM Manager will be deployed on it automatically; otherwise you need to deploy Oracle TSAM Manager on a supported Web container manually.
Some of the deployment steps require you to edit the web.xml file located at WEB-INF directory in the tsam.war package. You need to unpack tsam.war using jar tool, edit WEB-INF/web.xml, repack to a war package, then deploy the war package to a supported Web container.
If you run Oracle TSAM Manager with the bundled Apache Tomcat, you can start and shut down Oracle TSAM Manager using the following steps:
Table 1 lists the Oracle TSAM environment parameters.
The Oracle TSAM environment parameters are configured automatically by the Oracle TSAM Manager installer. On UNIX platforms, the Oracle TSAM environment parameters are located in the tsam.env file; on Windows platforms, they are located in the startup.cmd file.
Oracle TSAM Manager provides deployment scripts for the following DBMS:
To successfully deploy an Oracle database, you must do the following steps:
An SQL script, sql/createdb_oracle.sql, is provided to create an Oracle TSAM Manager database for Oracle.
| Notes: | Before using this script, you must have already installed and configured an Oracle database. |
Table 2 lists the Oracle TSAM Manager configuration file parameters you need to edit to configure an Oracle database:
| Note: | The Oracle TSAM Manager configuration file is located at: |
| Note: | tsam/WEB-INF/web.xml. |
To successfully deploy a Apache Derby database, you must do the following steps:
A pre-built Apache Derby database instance is provided; however, you can also create one using the provided SQL script sql/createdb.sql. The following example creates a Oracle TSAM Manager database using the Apache Derby ij utility:
ij version 10.2
ij> connect 'jdbc:derby://localhost/tmonitordb;create=true';
ij> run 'createdb.sql';
Table 3 lists the Oracle TSAM Manager configuration file parameters you need to edit to configure an Apache Derby database:
| Note: | The Oracle TSAM Manager configuration file is located at: |
| Note: | tsam/WEB-INF/web.xml. |
Apache Tomcat can be automatically installed and configured when Oracle TSAM Manager is installed.Configuration parameters for Apache Tomcat are located in the following files:
You can directly run Oracle TSAM Manager without changing any Apache Tomcat configuration parameters.
If required, you can change the default for the following parameters:
The default Apache Tomcat port number is 8080. You can change the default based on your environment. The port is defined in <TSAMDIR>/apache-tomcat-5.5.17/conf/server.xml file. For example, you could change to port 9090 by doing the following:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port=”9090” acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" redirectPort="8443"/>The Oracle TSAM Manager console and data server URLs depend on the Apache Tomcat port setting. The following example assumes the default port “8080” used:
The “host” is the full domain name or IP address where the Oracle TSAM Manager is installed. The Oracle TSAM Agent LMS must be set correctly using the Oracle TSAM Manager data server URL.
The session timeout can be configured by modifying the <session-config> element in <TSAMDIR>/apache-tomcat-5.5.17/conf/web.xml file . For example, the following configuration invalidates an inactive session after 30 minutes.
<session-config>
<session-timeout>30</session-timeout>
</session-config>
This is the maximum number of HTTP requests that can be pipelined until the connection is closed by the server. Apache Tomcat provides an attribute maxKeepAliveRequests in the <TSAMDIR>/apache-tomcat-5.5.17/conf/server.xml file for custom control. Setting this attribute to 1 disables HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. Setting this to -1 allows an unlimited pipeline amount or keep-alive HTTP requests. If not specified, this attribute is set to 100.
<Connector port="8080" ... maxKeepAliveRequests="-1"/>
You must configure the maximum size in bytes of the POST, maxPostSize, that is handled by the container FORM URL parameter parsing. The limit can be disabled by setting this attribute to a value less than or equal to 0. If not specified, this attribute is set to 2097152 (2 megabytes). maxPostSize is modified in the <TSAMDIR>/apache-tomcat-5.5.17/conf/server.xml file.
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector maxPostSize="0" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443"/>
If Oracle TSAM has huge amount of monitoring data in the database, and maxPostSize is not adequate, an exception message, “javax.servlet.ServletException: Post too large”, is given when any operations fail.
| Note: | It is recommended that maxPostSize is set to 0. |
This is the maximum number of request processing threads created by Apache Tomcat, maxThreads, which determines the maximum number of simultaneous requests that can be handled by Apache Tomcat. If not specified, this attribute is set to 200. maxThreads is modified in the Apache Tomcat server.xml file. Oracle TSAM keeps a thread-level JDBC connection if the thread has database access. When you configure this attribute, you need to consider the DBMS capability.
This is the maximum queue length, acceptCount, for incoming connection requests when all possible request processing threads in Apache Tomcat are in use. Any requests received when the queue is full are refused. The default value is 100. Setting acceptCount to a larger number allows the Apache Tomcat queue to accept more HTTP requests if Apache Tomcat is busy. acceptCount is modified in the Apache Tomcat server.xml file.
The following is a maxPostSize, maxThreads, acceptCount example:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector maxPostSize="0" acceptCount="1000" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="130" minSpareThreads="25" port="8080" redirectPort="8443"/>
For more information, see the Apache Tomcat Web site.
After installing Oracle WebLogic Server, do the following steps to deploy Oracle TSAM:
http://localhost:7001/console.tsam.war file in the $TSAMDIR directory.tsam.war file.At the Settings for TSAM page, you can modify specific settings for TSAM at Configuration - > General. For example, Session Timeout (in seconds).
| Note: | It is recommended that you restart your domain to launch TSAM. |
You can directly run the Oracle TSAM Manager without changing any Oracle WebLogic configuration parameters.
If required, you can change the default for the following parameters:
The default Oracle WebLogic Server Listening port number is 7001. To change the default Listening Port, do the following steps:
http://localhost:7001/console.To configure Session Timeout, do the following steps:
http://localhost:7001/console.To enable and disable HTTP KeepAlive, do the following steps:
http://localhost:7001/console.To set the maximum size in bytes of the POST unlimited, do the following steps:
http://localhost:7001/console.Maximum Thread Simultaneous Processing is mapped into Maximum Threads Constraint at WebLogic Server. To configure Maximum Threads Constraint, do the following steps:
http://<hostname>:<port>/console, where <hostname> is the host name of the machine running WebLogic Server, and <port> is the port number that WebLogic Server listens for requests (7001 by default).WebLogic.wsee.mdb.DispatchPolicy”), create a new Work Manager and assign it to the right server.Maximum Incoming Connection Requests is mapped into Capacity Constraint at WebLogic Server. To configure Capacity Constraint, do the following steps:
http://<hostname>:<port>/console, where <hostname> is the host name of the machine running WebLogic Server, and <port> is the port number that WebLogic Server listens for requests (7001 by default).WebLogic.wsee.mdb.DispatchPolicy”), create a new Work Manager and assign it to the right server.| Note: | If you do not see Lock & Edit in the Change Center of the Administration Console, that means that WebLogic Server Configuration editing is enabled. Then click Preferences link, uncheck Automatically Acquire Lock and Activate Changes checkbox, then click save button. Now you will see two buttons, Lock & Edit, Release Configuration in the Change Center of the Administration Console. |
For more information, see the Oracle WebLogic Web site.
After installing Oracle OC4J, do the following steps to deploy Oracle TSAM:
http://localhost:8888/em.tsam.war file in the $TSAMDIR directory.You can directly run the Oracle TSAM Manager without changing any Oracle OC4J configuration parameters.
If required, you can change the default for the following parameters:
The default Oracle OC4J Listening port number is 8888. To change the default Listening Port, modify the configuration file <OC4J_HOME>/j2ee/home/config/default-web-site.xml accordingly.
The default servlet session timeout for OC4J is 20 minutes. To change the default value, modify file /WEB-INF/web.xml in tsam.war. Find the following lines or add them if they don’t exist:
<session-config><session-timeout>20</session-timeout>
</session-config>
Change the value accordingly.
The default value is 100. Oracle HTTP Server uses directives in httpd.conf to configure the value (not applicable for standalone OC4J).
Modify the configuration file <OC4J_HOME>/j2ee/home/config/server.xml. Find the following lines or add them if they don’t exist:
<global-thread-pool min="100" max="100" queue="200"
keepAlive="700000" cx-min="100" cx-max="100" cx-queue="200"
cx-keepAlive="700000" debug="true"/>
Change the value accordingly.
Modify the configuration file <OC4J_HOME>/j2ee/home/config/server.xml. Find the following lines or add them if they don’t exist:
<max-http-connections max-connections-queue-timeout="120"
socket-backlog="50" value="100"/>
Change the attributes accordingly.
For more information, see the Oracle OC4J Web site.
|