To properly deploy the Oracle TSAM Plus 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 Plus Data Server address which is configured in the Oracle TSAM Plus Manager. For more information, see the Oracle TSAM Plus Reference Guide. The Oracle TSAM Plus Data Server uses the same port number as the Oracle TSAM Plus Manager Console.
• The LDAP deployment updates the LDAP configuration information in the tsam.ear file (located at < TSAM_DIR >/deploy).
Note: The LDAP information in the tsam.ear file is overwritten after you run the LDAP Deployment utility. You must redeploy the tsam.ear file on the application server.Listing 2 UNIX LDAP Deployment Utility ExampleListing 3 Windows LDAP Deployment Utility Example
• 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)
• Resets the default admin user password to the password specified by the parameter -adminpassword when setting the parameter “-resetpassword yes”.
• Specifies a Weblogic data source JNDI name with the "-wlsdsJNDIname" parameter. The database properties parameters are ignored if "-wlsdsJNDIname" is specified.
• The Oracle database driver is recommended to be “*Oracle's Driver (Thin) for Instance connections, Versions:9.0.1 and later”, “*Oracle's Driver (Thin) for RAC Service-Instance connections; Versions:10 and later", or “*Oracle's Driver (Thin) for Service connections; Versions:9.0.1 and later"
• The Derby database driver is recommended to be “Derby's Driver (Type 4) Versions:Any”.
• If you select the parameter "-overwrite yes", the existing TSAM Plus 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 Plus 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 4 UNIX Database Deployment Utility Example
2.
3. Deploy TSAM Plus to an Oracle database with the user "tsam" and the password "tsam"
3. Deploy TSAM Plus 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 6 and Listing 7 accordingly.Execute the commands shown in Listing 8 and Listing 9 for Unix and Windows accordingly to deploy Oracle TSAM Plus 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. When installing Oracle TSAM Plus with a Tomcat server, the default JVM memory size is not sufficient for Oracle TSAM Plus to run. You can extend the memory by specifying the JAVA_OPTS environment variable value to: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 Plus Manager console URL: http://host:8080/tsam.The “host” is the full domain name or IP address where the Oracle TSAM Plus Manager is installed. The Oracle TSAM Plus Agent LMS must be set correctly using the Oracle TSAM Plus Manager data server URL.The defalut Tomcat session timeout is 30 minutes. You can modify the default value in <TSAM_DIR>/apache-tomcat-6.0.24/conf/web.xml. Following is an example that sets the default timeout to 40 minutes:To modify the TSAM Plus Web application session timeout only, you need to modify <TSAM_DIR>/apache-tomcat-6.0.24/webapps/tsam/WEB-INF/web.xml. Following is an example: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 bytes (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 Plus 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 Plus 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 Plus is deployed.
6.
1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
2.
3.
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 Plus 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 Plus 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 Plus 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 Plus 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.
•
•
•
•
• $ORACLE_HOME is set to the directory of Oracle database software home.
Note: If you have installed Oracle database client, make sure SQLPLUS/Perl/JDK/JRE are also installed.
• SQLPLUS is under $ORACLE_HOME
• Perl is under $ORACLE_HOME
• JDK/JRE is under $ORACLE_HOME.Under the directory $TSAM_MANAGER_INSTALLED_DIR/deploy/dme/bin, run the AutoPurgeManager script. The script format is as follows:
• <repHost> - Host name to be used for the repository
• <repPort> - Port number to be used for the repository
• <repSID> - SID to be used for the repositoryMandatory option, where <actioncode> can be one of the following:
• create - creates TSAM Plus repository with Oracle time partition.
• enableAutoPurge - enables Auto Purge under existing TSAM Plus repository
• disableAutoPurge - disables Auto Purge under existing TSAM Plus repository
• drop - drops existing TSAM Plus repositoryRepository schema password. It overwrites the existing password set for TSAM Plus repository. Mandatory with create and enableAutoPurge actions.Optional. TSAM Plus user group ID for "administrator". Defaults to 0 if it is not set when executing create. If it is set with enableAutoPurge/disableAutoPurge, the existing group ID will be overwritten.Optional. TSAM Plus user group ID for "viewer". Defaults to 1 if it is not set when executing create. If it is set with enableAutoPurge/disableAutoPurge, the existing group ID will be overwrittenTSAM Plus administrator password. Mandatory with create action.If it is set with enableAutoPurge/disableAutoPurge, the existing password will be overwritten.If it is set with enableAutoPurge, the existing retaining period will be overwritten.Optional. Full path name of the default tablespace file. Defaults to $ORACLE_HOME/dbs/tsam.dbf. It is used with create action only.Optional. Default tablespace data file size. Defaults to 200MB. It is used with create action only.Optional. Default tablespace data file extension size. Defaults to 50MB. It is used with create action only../AutoPurgeManager xxx.xxx.com 1521 orcl -action create -dbPassword 123 -reposName tsam -reposPassword tsam -adminPassword admin11TSAM_DAILY_MAINTENANCE, the Oracle Database Scheduler created by DME, cannot be stopped when DME is enabled.If the TSAM Plus schema created by DME shares the same Oracle database instance with Oracle Enterprise Manager (12.1.0.1.0 with Bundle Patch 1), when you drop TSAM Plus schema using DME drop action, DME will hang up at "Quiescing DB ... ". To work around such issue, you can press Ctrl + C to break the hang-up and proceed to run the rest tasks.2. cd <TSAM12c_DIR >/deployTable 1 lists AlertMigration.sh/cmd parameters.
Table 1 AlertMigration.sh/cmd Parameters
Note: If the specified database uses OS authentication, the user name (parameter srcdbuser or dstdbuser) and password (parameter srcdbpassword or dstdbpassword) should be null.TSAM 1.1/10gR3 policy files can be imported in the Oracle TSAM Plus 12cR1 (12.1.1.1) policy management page. For more information, see Tuxedo Monitoring Policy in the Oracle TSAM Plus Users Guide.
2. Run the script under <TSAM12c_DIR>/deploy/TSAMUpgradeOracle.sql
a. Enter the directory <TSAM12c_DIR>/deploy.