3 Post-Installation Tasks

You can verify and validate the installation with the help of post-installation validations. In case of failed installation, you can follow the procedure to uninstall and reinstall Oracle Traffic Director.

This section contains the following topics:

Verifying the Installation

If something went wrong it can be traced by examining the log file, you can verify whether the installation was completed properly by running the viewInventory script.

For more information about verifying and troubleshooting the installation, see Verifying and Troubleshooting installation of Oracle Universal Installer.

Examining the Installation Log

The installer creates log files in the logs subdirectory within the Oracle inventory directory.

Note:

If you do not know the location of the Oracle inventory directory, you can find the path to it in the ORACLE_HOME/oraInst.loc file.

The below table lists logs directory that contains the following files:

Logs Directory Description

install date-time-stamp .log

This is the main log file.

install date-time-stamp .out

This log file contains the output and error streams during the installation.

launcher-time-stamp .log

This file contains the date/time the launcher was initiated.

installProfile date-time-stamp .log

This log file contains the overall statistics, like time taken to complete the installation, as well as configuration, memory, and CPU details.

oraInstall date-time-stamp .log

This log file contains the output stream of the copy session.

timeTaken date-time-stamp .log

This file is created only if you start the installer with the -printtime option. It contains information for the amount of time taken to move between screens (applicable for GUI installations only).

time date-time-stamp .log

This file is created only if you start the installer with the -printtime option. It contains time information for the copy session.

memory date-time-stamp .log

This file is created only if you start the installer with the -printmemory option. It contains memory usage information for the copy session.

Viewing the Inventory

After installing Oracle Traffic Director and performing the post-installation steps, verify that the Oracle home directory contains the required directories by running viewInventory script. Executing this script after successful installation will get a result output, as shown is the following example:

<ora_home>/oui/bin/viewInventory.sh | grep -i otd 
(For Windows it would be: <ora_home>/oui/bin/viewInventory.bat) 
Oracle Home: /oracle/Middleware      
FeatureSet: fmw_install_otd 12.2.1.3.0        
Component: oracle.as.install.otd.prerequisite 12.2.1.3.0        
Component: oracle.as.install.otd 12.2.1.3.0      
FeatureSet: otd 12.2.1.3.0      
FeatureSet: em_fmcOtdPlugin 12.2.1.3.0        
Component: oracle.sysman.fmw.plugin.webtier.otd 12.2.1.3.0      
FeatureSet: webgate_otd 12.2.1.3.0        
Component: oracle.oamclient.webgate.otd 12.2.1.3.0

For more information about the viewInventory script, see Understanding viewInventory script.

Configuring Oracle Traffic Director Domain

You need to configure a domain after installing Oracle Traffic Director.

In case of collocated installation, ensure that WLS is already installed. For more information, see Configuring a WebLogic Domain for Oracle Traffic Director in Administering Oracle Traffic Director.