• The LDAP deployment updates the LDAP configuration information in the tsam.ear file (located at <TSAM_DIR>/deploy). For more information, refer to Deploying LDAP Configuration File in Oracle TSAM Plus Configuration Guide.
• Unix/Linux 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”.Listing 1‑1 and Listing 1‑2 show Unix/Linux and Windows database deployment utility examples accordingly.
• 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 1‑1 Unix/Linux Database Deployment Utility Example
2.
3. Deploy TSAM Plus to an Oracle database with the user "tsam" and the password "tsam"
Note: Other parameters for creating DB are ignored when -wlsdsJNDIname is specified.Listing 1‑2 Windows Database Deployment Utility Example
3. Deploy TSAM Plus to an Oracle database with the user "tsam" and the password "tsam"
Note: Other parameters for creating DB are ignored when -wlsdsJNDIname is specified.Since TSAM Plus 12.1.3 Rolling Patch 008, a new mandatory argument, -enable_partition yes|no, is introduced for DatabaseDeployer.sh/cmd. It specifies whether to create the Oracle Database schema with partition. -enable_partition yes is only used for Oracle Enterprise Edition (with partition feature).Unix/Linux Application Server Deployment: AppServerDeployer.shWindows Application Server Deployment: AppServerDeployer.cmdUnix/Linux and Windows application deployment utility examples are shown in Listing 1‑3 and Listing 1‑4 accordingly.Since TSAM Plus 12.1.3 Rolling Patch 008, a new file, tsam_wls12c.ear, is provided under <TSAM_DIR>/deploy for support of Weblogic/ADF 12.1.3. After Rolling Patch 008 applied, AppServerDeployer.sh/cmd updates both tsam.ear and tsam_wls12c.ear. The database connection for JDBC/JPA in tsam.ear or tsam_wls12c.ear is copied from previous tsam.ear. Therefore, database connections for JDBC/JPA in ears between patch applied before and after are same.Execute the commands shown in Listing 1‑5 and Listing 1‑6 for Unix/Linux 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.
•
• For Weblogic/ADF 12.1.3, locate the tsam_wls12c.ear file in the $TSAMDIR/deploy directory. This requires TSAM Plus 12.1.3 Rolling Patch 008 and later versions.
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. 2. cd <TSAM12c_DIR>/deployTable 1‑1 lists AlertMigration.sh/cmd parameters.
Table 1‑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 12cR2 (12.1.3) policy management page. For more information, see Tuxedo Monitoring Policy in the Oracle TSAM Plus Users Guide.
2. Run the scripts under <TSAM12c_DIR>/deploy
• Enter the directory <TSAM12c_DIR>/deploy.