Installing Oracle TSAM Using GUI-Mode Installation

The following sections describe how to install Oracle TSAM using graphical user interface (GUI) mode installation on both Windows and UNIX systems:

•	What Is GUI-Mode Installation?

•	Installing on Windows or UNIX Platforms in Graphics Mode

•	Uninstalling Oracle TSAM

What Is GUI-Mode Installation?

The graphical user interface mode installation is the graphics-based method of executing the Oracle TSAM installation program. It can run on both Windows and UNIX systems.

To run GUI-mode installation, the computer console on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do.

Note:

To install Oracle TSAM on a UNIX system with a non-graphics console, see “Installing Oracle TSAM Using Console-Mode Installation” on page 3‑1.

Installing on Windows or UNIX Platforms in Graphics Mode

1.	Launch Oracle TSAM installer.

2.	Choose Install Set: Select the install set that you want installed on your system:

•	Full Install

•	Agent Install

•	Manager install

3.	Click Next to proceed with the installation. The Choose Oracle Home Directory screen appears.

You can select from the following options:

•	Choose existing Oracle Home directory

•	Specify Oracle Home directory

If you select option 2, then you need to specify an Oracle Home directory. The path of this directory must be an absolute existing path name with writing permission; otherwise, the following message is displayed:

Error: The specified directory does not exist or is not writable.

Note:

If Oracle TSAM Agent is selected, the installer must verify that the current Oracle Tuxedo version is 11gR1. The "registry.xml" file under the Oracle Home is checked. If the default Oracle Home folder does not contain this file, option 1 is not displayed. The following message is displayed: Error: Oracle Tuxedo is not found in the specified directory.

If this file exists, the installer can verify the Oracle Tuxedo version, Oracle Tuxedo components list and the Oracle Tuxedo installation directory. If the Oracle Tuxedo version is not supported, the following message is displayed: Error: Registered Oracle Tuxedo version 11gR1 is not found in the specified directory.

If the selected Oracle Tuxedo install set is not "Full" or "Server", the following message is displayed: Error: Registered Oracle Tuxedo version does not have server component installed.

If the Oracle Tuxedo installation directory does not exist, the following message is displayed: Error: Registered Oracle Tuxedo install directory is not found.

If the Oracle Tuxedo installation directory is not writable, the following message is displayed: Error: Registered Oracle Tuxedo install directory is not writable.

If a previous installation is detected, the Overwrite screen appears:

---------------------------------------------------------------------

Overwrite feature?

The following TSAM 11gR1 feature is found under

/apps/OracleHomes/tsam11gR1

...

Do you want to overwrite it?

---------------------------------------------------------------------

You can choose to overwrite it or not.

Oracle TSAM backs up the three configuration files in the deployment folder to the Oracle TSAM installation folder when shutting down. The backed up files are:

/tsam.properties

/art.properties

/persistence.xml

If these files are found in the chosen installation folder, the following prompt appears:

---------------------------------------------------------------------

TSAM 11gR1 configuration files are found under /apps/OracleHomes/tsam11gR1. Do you want to import them? No/Yes

---------------------------------------------------------------------

If you choose "Yes", these files are imported.

4.	Click Next to proceed with the installation. The Choose Install Folder screen appears. You can modify the default TSAM 11g Release 1 (11.1.1.2) installation directory.

5.	Click Next to proceed with the installation. If you selected Full Install or Manager Install, the Choose Authentication Type screen appears.

---------------------------------------------------------------------

Choose Authentication Type:

User information can be stored in the Oracle TSAM database or an existing LDAP server.

The authentication type "Local first" supports both.

"LDAP only" exclusively supports LDAP authentication.

• Local first

• LDAP only

---------------------------------------------------------------------

If you choose "Local first", the installer prompts:

Do you want to specify an LDAP configuration file now?

• No

• Yes

If you choose "No", you can specify the LDAP configuration file by running the LDAP deployment utility LDAPDeploye" after installation.

If you choose "No" in this process, there is no LDAP configuration file deployed. You must deploy an LDAP configuration file after installation manually by using the LDAP deployment utility (LDAPDeployer.sh or LDAPDeployer.cmd) if you want to enable the LDAP authentication. For more information, see Deploying Oracle TSAM Manager in the Oracle TSAM Deployment Guide.

If you choose "LDAP only" as the authentication type or "Yes", you are prompted to input the path of the LDAP configuration file.

Enter an existing LDAP configuration file:

6.	Click Next to proceed with the installation. If you selected Full Install or Manager Install, the Choose Database Type screen appears.

•	Bundled Derby database

•	An existing Derby database

•	An existing Oracle database

•	Skip, I will deploy TSAM 11gR1 to an existing database server after the installation

Existing Derby or Oracle databases are expected to be configured and running before Oracle TSAM manager installation. For bundled Derby, if you deploy Oracle TSAM manager to an existing WebLogic server, the bundled Derby database still runs after installation. Otherwise (if the application server is Tomcat), the bundled Derby database shuts down.

Note:

If you choose to skip this process, the Oracle TSAM database is not created during installation. You must add an Oracle TSAM database after installation manually by using the database deployment utility (DatabaseDeployer.sh or DatabaseDeployer.cmd). For more information, see Deploying Oracle TSAM Manager in the Oracle TSAM Deployment Guide.

7.	Click Next to proceed with the installation. If you choose connect to an existing Derby or Oracle database, the Choose Database Type screen appears.

host name:

port:

database name:

user name:

password:

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".

If the specified database cannot be connected, an error message is displayed and you should specify the database connection again.

If a previous database installation is detected, the installer prompts:

TSAM 11gR1 Database overwrite prompt

------------------------

TSAM 11gR1 Database is found under "XXX".

Do you want to overwrite it?

------------------------

Choose "yes" to overwrite it, or "no" to leave it untouched.

If you choose the bundled Derby database, the existing database is directly overwritten.

8.	Click Next to proceed with the installation. If you choose to create a new database, Oracle TSAM 11gR1 creates a user with the name "admin". You are prompted to specify and verify the password accordingly.

Enter the administrator group ID (DEFAULT: 0):

Enter the viewer group ID (DEFAULT: 1):

Oracle TSAM 11gR1 creates a user with the name "admin". Specify its password: Verify password:

9.	Click Next to proceed with the installation. If install mode "Full Install" or "Manager Install" is selected, The Choose Application Server screen appears.

•	Bundled Tomcat server

•	An existing Tomcat server

•	An existing WebLogic server

•	Skip, I will deploy TSAM 11gR1 to an existing application server after the installation

If 1 is selected, If 1 is selected, the Oracle TSAM startup/shutdown script and TSAM Manager war package is copied to the Install Directory.

If 2 is selected, you are prompted to specify an existing Tomcat folder.

Choose a folder where Tomcat server is installed:

If 3 is selected, you are prompted to specify an existing WebLogic Server directory.

Oracle WebLogic server directory selection

------------------------

•	Choose existing Oracle WebLogic Server directory

•	Specify existing Oracle WebLogic Server directory

For 1, 2 or 3, the Oracle TSAM Manager .war package is also deployed to the specified application server.

Note:

If you select 4, Oracle TSAM Manager will not be deployed during installation. You must deploy it to an existing application sever (WebLogic or Tomcat) after installation manually by using the application server utility (AppServerDeployer.sh or AppServerDeployer.cmd).For more information, see Deploying Oracle TSAM Manager in the Oracle TSAM Deployment Guide.

10.	Click Next to proceed with the installation. If you choose deploy to an existing WebLogic Server, you are required to input the following WebLogic Server connection parameters.

admin url:

user name:

password:

The existing WebLogic Server is expected to be located on the local installation machine. Remote existing Weblogic Servers are not supported.

11.	If the installation process continues, the Pre-Installation Summary screen appears. Review the summary information and click Install if the information is acceptable. The installation process continues. Click Previous to go back and modify any input that you want to change.

12.	Upon completion, the Install Complete screen appears. Click Done to exit the installation program.

Uninstalling Oracle TSAM

Perform the following steps to uninstall Oracle TSAM software:

Windows:

Choose Start→Programs→Oracle WebLogic E-Business Platform→tsam11gR1→uninstall_tsam11gR1 from the Start menu.

You can also uninstall via Start→Control Panel→Add or Remove Programs.

UNIX

Execute the command

<ORACLEHOME>/tsam11gR1/uninstall_tsam11gR1/uninstall_tsam11gR1

The Oracle TSAM Uninstaller screen appears. Click Uninstall to start uninstalling Oracle TSAM. Click Done to complete the uninstallation.

See Also

•	Oracle TSAM Deployment Guide