Deployment Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Oracle TSAM Plus Deployment Guide

This chapter contains the following sections:

 


Deploying Oracle TSAM Plus Agent

The Local Monitor Server (LMS) is an Oracle Tuxedo system server provided by the Oracle TSAM Plus Agent.

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 File
...
*MACHINES
MACHINEA
...
*GROUPS
...
LMSGRP LMID=MACHINEA
...
*SERVERS
LMS SRVGRP=LMSGRP SRVID=1 CLOPT=”-A -- -l tsamweb.abc.com:8080/tsam”
...

The “-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.

Note: LMS can also be added to a running Oracle Tuxedo application using TMIB.

 


Deploying Oracle TSAM Plus Manager

This section contains the following topics:

Overview

The Oracle TSAM Plus Manager functions as a Web application in a Servlet/JSP container. It uses the DBMS (Database Management System) to store persistent Oracle Tuxedo performance and monitoring data. Before using Oracle TSAM Plus Manager, it must be deployed to a database server and a Web application container.

If you input the LDAP configuration file during installation, the LDAP deployment is done automatically; otherwise, you must do the LDAP deployment using the "LDAP Deployment Utility" if you want to enable the LDAP authentication.

If you select "Bundled Derby database", "An existing Derby database" or "An existing Oracle database" during installation, Oracle TSAM Plus Manager is deployed on the specified database server automatically; otherwise, you must deploy Oracle TSAM Plus Manager to a database server using the "Database Deployment Utility".

If you select "Bundled Tomcat server", "An existing Tomcat server" or "An existing WebLogic server" during installation, Oracle TSAM Plus Manager is deployed on the specified application server automatically; otherwise you must deploy Oracle TSAM Plus Manager to an application server using the "Application Server Deployment Utility" or manually.

Oracle TSAM Plus Manager LDAP Deployment

The LDAP deployment updates the LDAP configuration information in the tsam.ear file (located at < TSAM_DIR >/deploy).

LDAP Deployment Utilities

Oracle TSAM Plus provides the following LDAP Deployment utilities:

Listing 2 and Listing 3 show UNIX and Windows LDAP Deployment utility examples accordingly.

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.

For more LDAP configuration file information, see the Oracle TSAM Plus Installation Guide.

Listing 2 UNIX LDAP Deployment Utility Example
cd < TSAM_DIR >/deploy
./LDAPDeployer.sh tpgauth
Listing 3 Windows LDAP Deployment Utility Example
cd < TSAM_DIR >\deploy
LDAPDeployer.cmd c:\tpgauth

Oracle TSAM Plus Manager Database Server Deployment

If you choose to deploy Oracle TSAM Plus 12cR1 to an existing database server after installation, you must add an Oracle TSAM Plus database after installation using the database deployment utilities.

Database Deployment Utilities

Oracle TSAM Plus provides the following database deployment utilities:

The database deployment utilities do the following:

Listing 4 and Listing 5 show UNIX and Windows database deployment utility examples accordingly.

Note: The database utility has the following restrictions:

For more information, see the Oracle TSAM Plus Installation Guide.

Listing 4 UNIX Database Deployment Utility Example
  1. Deploy TSAM Plus to a Derby database
  2. cd < TSAM_DIR >/deploy
    ./ DatabaseDeployer.sh -type derby -hostname localhost -port 1527 -dbname TSAM -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  3. Deploy TSAM Plus to a Derby database with the user "app" and the password "app"
  4. cd < TSAM_DIR >/deploy
    ./ DatabaseDeployer.sh -type derby -hostname localhost -port 1527 -dbname TSAM -user app -password app -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  5. Deploy TSAM Plus to an Oracle database with the user "tsam" and the password "tsam"
  6. cd < TSAM_DIR >/deploy
    ./ DatabaseDeployer.sh -type oracle -hostname localhost -port 1521 -dbname TSAM -user tsam -password tsam -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  7. Reset the default admin user password to "admin1"
  8. cd < TSAM_DIR >/deploy
    ./DatabaseDeployer.sh -type oracle -hostname localhost -port 1521 -dbname TSAM -user tsam -password tsam -adminpassword admin1 -resetpassword yes
  9. Specify a Weblogic data source JNDI name "ds_tsam"
  10. cd < TSAM_DIR >/deploy
    ./DatabaseDeployer.sh -wlsdsJNDIname ds_tsam
    Listing 5 Windows Database Deployment Utility Example
  11. Deploy TSAM Plus to a Derby database
  12. cd < TSAM_DIR >\deploy
    DatabaseDeployer.cmd -type derby -hostname localhost -port 1527 -dbname TSAM -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  13. Deploy TSAM Plus to a Derby database with the user "app" and the password "app"

cd < TSAM_DIR >\deploy

DatabaseDeployer.cmd -type derby -hostname localhost -port 1527 -dbname TSAM -user app -password app -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  1. Deploy TSAM Plus to an Oracle database with the user "tsam" and the password "tsam"

cd < TSAM_DIR >\deploy

DatabaseDeployer.cmd -type oracle -hostname localhost -port 1521 -dbname TSAM -user tsam -password tsam -overwrite no -admingid 0 -viewergid 1 -adminpassword admin1
  1. Reset the default admin user password to "admin1"
  2. cd < TSAM_DIR >\deploy
    DatabaseDeployer.cmd -type oracle -hostname localhost -port 1521 -dbname TSAM -user tsam -password tsam -adminpassword admin1 -resetpassword yes
  3. Specify a Weblogic data source JNDI name "ds_tsam"
  4. cd < TSAM_DIR >\deploy
    DatabaseDeployer.cmd -wlsdsJNDIname ds_tsam

Oracle TSAM Plus Application Server Deployment

If you choose to deploy Oracle TSAM Plus 12cR1 to an existing application server after installation, you must deploy it to an existing application server (WebLogic or Tomcat) after installation using the application server utilities, or manually.

Note: The WebLogic server has the following restrictions:

Application Server Deployment Utilities

Oracle TSAM Plus provides the following application server deployment utilities:

UNIX Application Server Deployment: AppServerDeployer.sh

Windows Application Server Deployment: AppServerDeployer.cmd

UNIX and Windows application deployment utility examples are shown in Listing 6 and Listing 7 accordingly.

Listing 6 UNIX Application Server Deployment Utility Example
  1. Deploy TSAM Plus to a WebLogic server
  2. cd < TSAM_DIR >/deploy
    ./AppServerDeployer.sh -type weblogic -adminurl localhost:7001 -directory /home/oracle/wlserver_10.3 -user weblogic -password weblogic1
  3. Deploy TSAM Plus to a Tomcat server
  4. cd < TSAM_DIR >/deploy
    ./AppServerDeployer.sh -type tomcat -directory /home/oracle/apache-tomcat-6.0.24
    Listing 7 Windows Application Server Deployment Utility Example
  5. Deploy TSAM Plus to a WebLogic server
  6. cd < TSAM_DIR >\deploy
    AppServerDeployer.cmd -type weblogic -adminurl localhost:7001 -directory C:\oracle\wlserver_10.3 -user weblogic -password weblogic1
  7. Deploy TSAM Plus to a Tomcat server
  8. cd < TSAM_DIR >/deploy
    AppServerDeployer.cmd -type tomcat -directory C:\oracle\apache-tomcat-6.0.24

Manual Application Server Deployment

Oracle TSAM Plus Manager provides deployment scripts for the following application servers:

Oracle TSAM Plus Manual Apache Tomcat Server Deployment

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: Replace < TSAM_DIR > and < TOMCAT_DIR > with the actual TSAM and TOMCAT paths on your disk.
Listing 8 Oracle TSAM Plus Manual Apache Tomcat Server Deployment (Unix)
TSAMDIR=< TSAM_DIR >; export TSAMDIR
TOMCATDIR=< TOMCAT_DIR >; export TOMCATDIR
JAVA_HOME=$TSAMDIR/jdk; export JAVA_HOME
PATH=$TSAMDIR/jdk/bin:$PATH; export PATH
cd $TSAMDIR/deploy
mkdir tsam
cd tsam
jar xf ../tsam.ear
mkdir tsam
cd tsam
jar xf ../tsam.war
cp ../../adflib/* WEB-INF/lib/
jar cf ../tsam.war *
cd ..
rm -rf $TOMCATDIR/webapps/tsam
rm -rf $TOMCATDIR/webapps/tsamhelp
cp tsam.war $TOMCATDIR/webapps/
cp tsamhelp.war $TOMCATDIR/webapps/
cd ..
cp adflib/* $TOMCATDIR/lib/
rm -rf tsam
Listing 9 Oracle TSAM Plus Manual Apache Tomcat Server Deployment (Windows)
set TSAMDIR=< TSAM_DIR >
set TOMCATDIR=< TOMCAT_DIR >
set JAVA_HOME=%TSAMDIR%\jdk
set PATH=%JAVA_HOME%\bin;%PATH%
cd /d %TSAMDIR%\deploy
mkdir tsam
cd tsam
jar xf ..\tsam.ear
mkdir tsam
cd tsam
jar xf ..\tsam.war
copy ..\..\adflib\* WEB-INF\lib\
jar cf ..\tsam.war *
cd ..
rd %TOMCATDIR%\webapps\tsam /s/q
rd %TOMCATDIR%\webapps\tsamhelp /s/q
copy tsam.war %TOMCATDIR%\webapps\
copy tsamhelp.war %TOMCATDIR%\webapps\
cd ..
copy adflib\* %TOMCATDIR%\lib\
rd tsam /s/q
Oracle TSAM Plus Manual Oracle WebLogic Server Deployment

After installing Oracle WebLogic Server, do the following steps to deploy Oracle TSAM Plus:

  1. Start your WebLogic Domain and launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
  2. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left panel of the Administration Console, select Deployments.
  4. In the right panel, click Install.
  5. In the Install Application Assistant, locate the tsam.ear file in the $TSAMDIR/deploy directory.
  6. Click Next.
  7. Choose the installation targeting style as an application.
  8. Click Next.
  9. Select the servers where you want to deploy the tsam.ear file.
  10. Click Next.
  11. Optionally update additional deployment settings. These settings include:
    • The deployed name of the application or module.
    • The security model that is applied to the application or module.
    • How the source files are made available to all targeted Managed Servers.
    • Typically, the default values are adequate.

  12. Click Next.
  13. Review the configuration settings you have specified, and click Finish to complete the installation.
  14. At the Settings for TSAM Plus page, you can modify specific settings for TSAM Plus at Configuration - > General. For example, Session Timeout (in seconds).

  15. If you chose to immediately go to the deployment configuration screen, click the tabs to set additional TSAM Plus configuration settings. If you chose to change this information later, you are returned to the Deployments table, which now includes the TSAM Plus installation.
  16. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Changing Configuration Parameters

As needed, you can change the parameters for the following servers:

Apache Tomcat Server Configuration

You can directly run Oracle TSAM Plus Manager without changing any Apache Tomcat configuration parameters.

If required, you can change the default for the following parameters:

Configuration parameters for Apache Tomcat Server are located in the following files:

Setting the Minimum JAVA Option Memory Size

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:

-Xms2048m -Xmx2048m

We strongly suggest you allocate at least 2048MB memory for heap memory size of tomcat server.

Configuring Apache Tomcat Listening Port

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:

<!-- 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 Plus 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 Plus Manager is installed. The Oracle TSAM Plus Agent LMS must be set correctly using the Oracle TSAM Plus Manager data server URL.

Configuring Session Timeout

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:

  <!-- ==================== Default Session Configuration ================= -->
  <!-- You can set the default session timeout (in minutes) for all newly   -->
  <!-- created sessions by modifying the value below.                       -->
    <session-config>
        <session-timeout>40</session-timeout>
    </session-config>

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:

<session-config>
        <session-timeout>60</session-timeout>
</session-config>"
Configuring HTTP KeepAlive

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.

For example:

<Connector port="8080" ...  maxKeepAliveRequests="-1"/>
Configuring POST Maximum Byte Size

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.

For example:

<!-- 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 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: It is recommended that maxPostSize is set to 0.
Configuring Maximum Thread Simultaneous Processing

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.

Configuring Maximum Incoming Connection Requests

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.

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.

WebLogic Server Configuration

You can directly run the Oracle TSAM Plus Manager without changing any Oracle WebLogic configuration parameters.

If required, you can change the default for the following parameters:

Setting the Minimum JAVA Option Memory Size

When installing Oracle TSAM Plus with a Weblogic server, specify at least 2048MB heap memory for the Weblogic server:

-Xms2048m -Xmx2048m

For information about how to change the heap size, refer to Oracle Weblogic documents.

Configuring Oracle WebLogic Listening Port

The default Oracle WebLogic Server Listening port number is 7001. To change the default Listening Port, do the following steps:

  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. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left panel of the Administration Console, under Environment, click the Servers.
  4. Click the Server, e.g., exampleServer, where Oracle TSAM Plus is deployed.
  5. Change default Listen Port at tab of Configuration -> General.
  6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Configuring Session Timeout

To set Session Timeout, do the following steps:

  1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
  2. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left panel of the Administration Console, click Deployments.
  4. Under Summary of Deployments on the right page, click TSAM web application link.
  5. Go to Configuration -> Application and then configure the Session Timeout (in seconds).
  6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Configuring HTTP KeepAlive

To enable and disable HTTP KeepAlive, do the following steps:

  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. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left panel of the Administration Console, under Environment, click the Servers.
  4. Click the Server, e.g., exampleServer, which your TSAM Plus deployed.
  5. Enable or disable HTTP KeepAlive by selecting Protocols -> HTTP.
  6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Configuring POST Maximum Byte Size

To set the maximum size in bytes of the POST unlimited, do the following steps:

  1. Launch Oracle WebLogic Server Administration Console using the following URL: http://localhost:7001/console.
  2. In the Change Center of the Administration Console, click Lock & Edit.
  3. In the left panel of the Administration Console, under Environment, click the Servers.
  4. Click the Server, e.g., exampleServer, which your TSAM Plus deployed.
  5. Change Max Post Size at tab of Protocols -> HTTP.
    Note: Set Max Post Size less than 0, which indicates an unlimited size.
  6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Configuring Maximum Thread Simultaneous Processing

Maximum Thread Simultaneous Processing is mapped into Maximum Threads Constraint at WebLogic Server. To configure Maximum Threads Constraint, do the following steps:

  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. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Configuring Maximum Incoming Connection Requests

Maximum Incoming Connection Requests is mapped into Capacity Constraint at WebLogic Server. To configure Capacity Constraint, do the following steps:

  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. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Note: If you do not see “Lock & Edit” in the Change Center of the Administration Console, WebLogic Server Configuration editing is enabled.
Note: Click Preferences. Uncheck the Automatically Acquire Lock and Activate Changes checkbox, then click Save.

For more information, see the Oracle WebLogic Web site.

Starting Up and Shutting Down Oracle TSAM Plus Manager

If you chose the bundled Apache Tomcat Server and the bundled Derby database during installation, startup/shutdown script files for both are installed in the Oracle TSAM Plus bin folder.

If you only choose the bundled Apache Tomcat Server, the installed startup/shutdown script only deals with Apache Tomcat Server. If you only choose the bundled Derby database, startup derby/shutdown derby script files are installed in the Oracle TSAM Plus bin folder.

Bundled Apache Tomcat Server Start Up/Shut Down

If you run Oracle TSAM Plus Manager with the bundled Apache Tomcat Server (with or without the Bundled Derby database), use the following steps to start and shut down Oracle TSAM Plus Manager:

  1. Start Oracle TSAM Plus Manager
  2. UNIX:

    1. cd <TSAM_DIR>/bin
    2. ./startup.sh
    3. Windows:

    4. cd <TSAM_DIR>/bin
    5. startup.cmd
  3. Shut down Oracle TSAM Plus Manager
  4. UNIX:

    1. cd <TSAM_DIR>/bin
    2. ./shutdown.sh
    3. Windows:

    4. cd <TSAM_DIR>/bin
    5. shutdown.cmd

Bundled Derby Database Start Up/Shut Down

If you run Oracle TSAM Plus Manager with the bundled Derby database (without the bundled Apache Tomcat Server), use the following steps to start and shut down Derby:

Note: If you do not choose the bundled Apache Tomcat Server, you must set up your JAVA environment (JDK 1.6 or above) and boot up your existing application server manually.
  1. Start the bundled Derby database
  2. UNIX:

    1. cd <TSAM_DIR>/bin
    2. ./startupderby.sh
    3. Windows:

    4. cd <TSAM_DIR>/bin
    5. startupderby.cmd
  3. Shut down the bundled Derby database
  4. UNIX:

    1. cd <TSAM_DIR>/bin
    2. ./shutdownderby.sh
    3. Windows:

    4. cd <TSAM_DIR>/bin
    5. shutdownderby.cmd

Data Management Enhancement Tool

Data Management Enhancement (DME) tool creates TSAM Plus monitoring tables with Oracle time partition, which provides you an automatic way to control the TSAM Plus monitoring table size and avoid filling up the table with enormous amount of data.

DME tool is provided independently with TSAM Plus installer. After installing TSAM Plus manager, you can choose to run DME tool, as needed.

The following TSAM Plus tables are partitioned when enabling DME:

Supported Database

DME tool is supported on Oracle Database 11.2.0.1.0, 11.1.0.6.0, and 10.2.0.1.0.

Prerequisites

Before using DME tool, make sure the following:

Running DME Script

Under the directory $TSAM_MANAGER_INSTALLED_DIR/deploy/dme/bin, run the AutoPurgeManager script. The script format is as follows:

AutoPurgeManager <repHost> <repPort> <repSID> [options]

where:

Options

-action <actioncode>

Mandatory option, where <actioncode> can be one of the following:

-dbPassword <dbPassword>

Mandatory option. Password of the database user, SYS.

-reposName <reposName>

Repository schema user name. Mandatory with create, enableAutoPurge, and disableAutoPurge actions.

-reposPassword <reposPassword>

Repository schema password. It overwrites the existing password set for TSAM Plus repository. Mandatory with create and enableAutoPurge actions.

-adminGroupId <adminGroupId>

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.
Note: If you use LDAP authentication the group ID should be same as the GID in LDAP.

-viewerGroupId <viewerGroupId>

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 overwritten
Note: If you use LDAP authentication the group ID should be same as the GID in LDAP.

-adminPassword <adminPassword>

TSAM Plus administrator password. Mandatory with create action. If it is set with enableAutoPurge/disableAutoPurge, the existing password will be overwritten.

-partitionsRetained <partitionsRetained>

Optional. TSAM Plus monitoring table partitions to be retained. Defaults to 32 days if it is not set when executing create. If it is set with enableAutoPurge, the existing retaining period will be overwritten.

-defaultTablespaceName <default tablespace name>

Optional. Default tablespace name. Defaults to TSAM_TABLESPACE. It is used with create action only.

-defaultDatafileName <default tablespace filename>

Optional. Full path name of the default tablespace file. Defaults to $ORACLE_HOME/dbs/tsam.dbf. It is used with create action only.

-defaultDatafileSize <default tablespace data file size>

Optional. Default tablespace data file size. Defaults to 200MB. It is used with create action only.

-defaultDatafileExtdSize <default tablespace data file extension size>

Optional. Default tablespace data file extension size. Defaults to 50MB. It is used with create action only.

Examples(1)

./AutoPurgeManager  bejxxxx.cn.oracle.com 1521 tsam -action enableAutoPurge -dbPassword tsam -reposName tsam -reposPassword tsam -adminGroupId 5 -viewerGroupId 6 -adminPassword admin11  -partitionsRetained 1 -verbose -defaultTablespaceName TUX_TABLESPACE -defaultDatafileName /testarea/em/app/oradata/tsam/tuxedo.dbf

Examples(2)

./AutoPurgeManager xxx.xxx.com 1521 orcl -action create -dbPassword 123 -reposName tsam -reposPassword tsam -adminPassword admin11

Limitation

TSAM_DAILY_MAINTENANCE, the Oracle Database Scheduler created by DME, cannot be stopped when DME is enabled.

Known Issue

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.

 


Oracle TSAM Plus Migration

This section contains the following topics:

Oracle TSAM 1.1/10gR3 Alert Migration

Oracle TSAM Plus Manager 12cR1 can import Oracle TSAM 1.1/10gR3 alert definition items or event trigger rule files and convert them to Oracle TSAM Plus 12c format. To make these conversions, you must do the following steps:

Oracle TSAM 1.1/10gR3 Alert Definition Items Migration

  1. Make sure your Oracle TSAM 1.1/10gR3 and Oracle TSAM Plus 12cR1 database servers are running.
  2. cd <TSAM12c_DIR >/deploy
  3. Run the commands shown in Listing 10.
  4. Listing 10 AlertMigration.sh (UNIX only)/cmd (Windows only)
    -srcdbtype SRCDBTYPE -srcdbhostname SRCDBHOSTNAME -srcdbport SRCDBPORT -srcdbdbname SRCDBNAME -srcdbuser SRCDBUSER -srcdbpassword SRCDBPASSWORD -dstdbtype DSTDBTYPE -dstdbhostname DSTDBHOSTNAME -dstdbport DSTDBPORT -dstdbdbname DSTDBNAME -dstdbuser DSTDBUSER -dstdbpassword DSTDBPASSWORD.

Oracle TSAM 1.1/10gR3 Rules File Migration

1. Make sure your Oracle TSAM Plus 12c database servers are running.

2. cd <TSAM12c_DIR >/deploy

3. Run the commands shown in Listing 11.

Listing 11 AlertMigration.sh (UNIX only)/cmd (Windows only)
-srcfile SRCFILE -dstdbtype DSTDBTYPE -dstdbhostname DSTDBHOSTNAME -dstdbport DSTDBPORT -dstdbdbname DSTDBNAME -dstdbuser DSTDBUSER -dstdbpassword DSTDBPASSWORD.

AlertMigration.sh Parameters

Table 1 lists AlertMigration.sh/cmd parameters.

Table 1 AlertMigration.sh/cmd Parameters

Parameter

Description
Default Value

Optional Value
srcfile
Oracle TSAM 1.1/10gR3 rules file path
srcdbtype
Oracle TSAM 1.1/10gR3 database type
oracle, derby
srcdbhostname
Oracle TSAM 1.1/10gR3 database host name
srcdbport
Oracle TSAM 1.1/10gR3 database port
srcdbdbname
Oracle TSAM 1.1/10gR3 database name
srcdbuser
Oracle TSAM1.1/10gR3 database user
null
srcdbpassword
Oracle TSAM 1.1/10gR3 database password
null
dstdbtype
Oracle TSAM Plus 12c database type
oracle, derby
dstdbhostname
Oracle TSAM Plus 12c database host name
dstdbport
Oracle TSAM Plus 12c database port
dstdbdbname
Oracle TSAM Plus 12c database name
dstdbuser
Oracle TSAM Plus 12c database user
null
dstdbpassword
Oracle TSAM Plus 12c database password
null

Note: If the specified database uses OS authentication, the user name (parameter srcdbuser or dstdbuser) and password (parameter srcdbpassword or dstdbpassword) should be null.

Oracle TSAM 1.1/10gR3 Policy Migration

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.

Oracle TSAM 11gR1 (11.1.1) Database Migration

The Oracle database created by TSAM 11gR1 (11.1.1) can be reused by TSAM Plus 12cR1 (12.1.1.1) after the database is upgraded. The Oracle TSAM Plus 12cR1 (12.1.1.1) database is different from the Oracle TSAM 11gR1 (11.1.1) database. You must run a database migration script before reusing it.

You must do the following steps:

  1. Make sure your Oracle TSAM 11gR1 (11.1.1) database server is running.
  2. Run the script under <TSAM12c_DIR>/deploy/TSAMUpgradeOracle.sql
  3. Take using Oracle SQLPlus as an example, the steps of running the script are as follows:

    1. Enter the directory <TSAM12c_DIR>/deploy.
    2. Run SQLPlus and connect to TSAM Plus 12.1.1.1 database.
    3. Execute the following command:
    4. SQL > @TSAMUpgradeOracle.sql
Note: TSAM 11g Derby database upgrading is not supported.

 


See Also


  Back to Top       Previous  Next