To properly deploy the Oracle TSAM Agent, you must add the LMS to each Oracle Tuxedo machine section of the UBBCONFIG file. Listing 1 shows an example of how to add the LMS to the UBBCONFIG file.Listing 1 LMS Added to UBBCONFIG FileThe “-l” option specifies the Oracle TSAM Data Server address which is configured in the Oracle TSAM Manager. For more information, see the Oracle TSAM Reference Guide. The Oracle TSAM Data Server uses the same port number as the Oracle TSAM Manager Console.
•
• UNIX Database Deployment: DatabaseDeployer.sh
• Windows Database Deployment: DatabaseDeployer.cmd
•
• Updates the database connection URL in the tsam.ear file (located at < TSAM_DIR >/deploy)
• If the specified database uses OS authentication, the user name and password should be null. For an Oracle database, the user name must be "tsam"; it must be created before you use this utility
• If you select the parameter "-overwrite yes", the existing TSAM database is always overwritten and the database connection URL in the tsam.ear file is updated; If you select the parameter "-overwrite no", the database connection URL is updated, but the existing TSAM database is not overwritten
• The database connection URL in the tsam.ear file is overwritten after you run the database deployment utility. You must redeploy the tsam.ear file on the application.Listing 2 UNIX Database Deployment Utility Example
2.
3. Deploy TSAM to an Oracle database with the user "tsam" and the password "tsam"
3. Deploy TSAM to an Oracle database with the user "tsam" and the password "tsam"UNIX Application Server Deployment: AppServerDeployer.shWindows Application Server Deployment: AppServerDeployer.cmdUNIX and Windows application deployment utility examples are shown in Listing 4 and Listing 5 accordingly.Execute the commands shown in Listing 6 and Listing 7 for Unix and Windows accordingly to deploy Oracle TSAM on an Apache Tomcat Server.
Note:
1. Start your WebLogic Domain and launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
2.
4. In the right panel, click Install.
5.
6. Click Next.
8. Click Next.
9. Select the servers where you want to deploy the tsam.ear file.
10. Click Next.
12. Click Next.
13. Review the configuration settings you have specified, and click Finish to complete the installation.
15. The default Apache Tomcat port number is 8080. You can change the default based on your environment. The port is defined in <TSAM_DIR>/apache-tomcat-6.0.24/conf/server.xml file. For example, you could change to port 9090 by doing the following:<Connector port=”9090” acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" redirectPort="8443"/>
• Oracle TSAM Manager console URL: http://host:8080/tsam.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 <TSAM_DIR>/apache-tomcat-6.0.24/conf/web.xml file . For example, the following configuration invalidates an inactive session after 30 minutes.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 <TSAM_DIR>/apache-tomcat-6.0.24/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.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 KB (2 megabytes). maxPostSize is modified in the <TSAM_DIR>/apache-tomcat-6.0.24/conf/server.xml file.<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: 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. The acceptCount parameter is modified in the Apache Tomcat server.xml file.<Connector maxPostSize="0" acceptCount="1000" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="130" minSpareThreads="25" port="8080" redirectPort="8443"/>
1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:port/console. Where: "localhost" is the host name of the machine running WebLogic Server, "port" is the port number where WebLogic Server listens for requests.
2.
3.
4. Click the Server, e.g., exampleServer, where Oracle TSAM is deployed.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:port/console. Where: "localhost" is the host name of the machine running WebLogic Server, "port" is the port number where WebLogic Server listens for requests (7001 by default).
2.
3.
4. Click TSAM application deployed.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:port/console. Where: "localhost" is the host name of the machine running WebLogic Server, "port" is the port number where WebLogic Server listens for requests (7001 by default).
2.
3.
4. Click the Server, e.g., exampleServer, which your TSAM deployed.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
2.
3.
4. Click the Server, e.g., exampleServer, which your TSAM deployed.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: 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).
2. In the Change Center of the Administration Console, click Lock & Edit, if you have not already done so.
3. In the left pane of the Administration Console, click Work Managers under Environment.
4. Click the Work Manager whose "Targets" includes the WebLogic Server where TSAM Manager web application is deployed. If no such work manager exists (usually called “WebLogic.wsee.mdb.DispatchPolicy”), create a new Work Manager and assign it to the right server.
5. Change Maximum Threads Constraint at tab of Configuration, if no constraint is configured, click New to create one.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: 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).
2. In the Change Center of the Administration Console, click Lock & Edit, if you have not already done so.
3. In the left pane of the Administration Console, click Work Managers under Environment.
4. Click the Work Manager whose "Targets" includes the WebLogic Server where TSAM Manager web application is deployed. If no such work manager exists (usually called “WebLogic.wsee.mdb.DispatchPolicy”), create a new Work Manager and assign it to the right server.
5. Change Capacity Constraint at tab of Configuration, if no constraint is configured, click New to create one.
6.
Note: If you do not see “Lock & Edit” in the Change Center of the Administration Console, WebLogic Server Configuration editing is enabled.Click Preferences. Uncheck the Automatically Acquire Lock and Activate Changes checkbox, then click Save.
b.
b.
b.