|
|
This topic contains the following sections:
The LMS (Local Monitor Server) is a Tuxedo system server provided by the BEA TSAM Agent.
To properly deploy the BEA 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”
...
The 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 BEA TSAM Data Server address which is configured in the BEA TSAM Manager. For more LMS information, see the
BEA TSAM Reference Guide. The BEA TSAM Data Server uses the same port number as the BEA TSAM Manager Console.
| Note: | LMS can also be added to a running Tuxedo application using TMIB. |
The BEA TSAM Manager functions as a Web application in a Servlet/JSP container. It uses the DBMS (Database Management System) to store persistent Tuxedo performance and monitoring data.
| Notes: | Apache Tomcat 5.5.17 Servlet/JSP container is installed with BEA TSAM Manager. |
| Note: | An evaluation copy of Apache Derby 10.2.2.0 DBMS is installed with BEA TSAM Manager. |
If you run BEA TSAM Manager with Apache Derby and Apache Tomcat on the same machine, you can start and shut down BEA TSAM Manager using the following steps:
Table 1 lists the BEA TSAM environment parameters.
The BEA TSAM environment parameters are configured automatically by the BEA TSAM Manager installer. On UNIX platforms, the BEA TSAM environment parameters are located in the tsam.env file; on Windows platforms, they are located in the startup.cmd file.
The BEA TSAM Manager supports the following DBMS:
No other actions are required if you use the Apache Derby provided in the BEA TSAM installer. The following information is for reference.
To successfully deploy a Apache Derby database, you must do the following steps:
Use the following commands to set up a Apache Derby environment on UNIX and Windows platforms:
export JAVA_HOME=<JDK or JRE directory>
export DERBY_HOME=<TSAMDIR>/db-derby-10.2.2.0-bin
cd <TSAMDIR>
set JAVA_HOME=<JDK or JRE directory>
set DERBY_HOME=<TSAMDIR>\db-derby-10.2.2.0-bin
cd <TSAMDIR>
Use the following commands to start up and shutdown a Derby database on UNIX and Windows platforms
cd <TSAMDIR>
startup: $DERBY_HOME/bin/startNetworkServer
shutdown: $DERBY_HOME/bin/stopNetworkServer
| Note: | If Apache Tomcat and Apache Derby are not run on the same machine, start Apache Derby using the following command: |
| Note: | NetworkServerControl start [-h <host>] [-p <portnumber>] |
cd <TSAMDIR>
startup: %DERBY_HOME%\bin\startNetworkServer.bat
shutdown:%DERBY_HOME%\bin\stopNetworkServer.bat
For more information, see the Apache Derby documentation (located in <TSAMDIR>/db-derby-10.2.2.0-bin/docs or the
Apache Derby Web site).
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 BEA 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 2 lists the BEA TSAM Manager configuration file parameters you need to edit to configure an Apache Derby database:
| Note: | The BEA TSAM Manager configuration file is located at: <TSAMDIR>/apache-tomcat-5.5.17/webapps/tsam/WEB-INF/web.xml: |
To successfully deploy an Oracle database, you must do the following steps:
An SQL script, sql/createdb_oracle.sql, is provided to create a BEA TSAM Manager database for Oracle.
| Notes: | Before using this script, you must have already installed and configured and Oracle database. |
| Note: | If you use an Oracle database, it is recommended that you comment out or remove the lines in the BEA TSAM start/shutdown scripts that start/shutdown the pre-built Apache Derby database instance. |
To use BEA TSAM Manager with Oracle, you must download the Oracle JDBC drivers and put them into a specified directory. Do the following steps:
| Note: | ojdbc14.jar for Oracle 10g Release 2 is recommended. You may choose different JDBC driver version according to your Oracle release. |
apache-tomcat-5.5.17/webapps/tsam/WEB-INF/lib. | Note: | Apache Tomcat typically creates this directory the first time the BEA TSAM Manager runs. If you do not find this directory, you can manually create it using the following command: |
cd apache-tomcat-5.5.17/webapps
mkdir tsam
cd tsam
jar -xf ../tsam.war
For more information, contact your DBA or go to the Oracle website.
Table 3 lists the BEA TSAM Manager configuration file parameters you need to edit to configure an Oracle database:
| Note: | The BEA TSAM Manager configuration file is located at<TSAMDIR>/apache-tomcat-5.5.17/webapps/tsam/WEB-INF/web.xml: |
Apache Tomcat is automatically configured when the BEA TSAM Manager is installed.Configuration parameters for Apache Tomcat are located in the following files:
You can directly run the BEA 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 909 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 BEA 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 BEA TSAM Manager is installed. The BEA TSAM Agent LMS must be set correctly using the BEA 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 the BEA TSAM has huge amount 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. 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. BEA 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.
|