Use the installation verification test

This topic describes how to use the installation verification test (IVT). The IVT verifies that the installation of the application server or deployment manager profile was successful. A profile consists of files that define the run-time environment for a deployment manager or an application server. Each profile has its own IVT command.

 

Before you begin

After installing the Network Deployment product and creating a deployment manager or application server profile, you are ready to use the installation verification test (IVT).

 

Overview

The IVT program scans product log files for errors and verifies core functionality of the product installation.

The Profile creation wizard creates profiles. After creating a profile, the Profile creation wizard displays a prompt for starting the First steps console. The First steps console is unique for each profile. See firststeps command for more information.

Installation verification is the first option on the First steps console.

The IVT program for an application server profile starts and monitors the application server process, which is the server1 process. The installation verification for a deployment manager profile starts and monitors the deployment manager process, which is the dmgr process. The IVT works differently for the deployment manager profile than for a stand-alone application server. On a stand-alone application server, the IVT queries servlets from the ivtApp application. However, the deployment manager does not have the ivtApp application, so the IVT looks at log files only.

 

Procedure

1. Start the First steps console and select Installation verification after creating a deployment manager profile or an application server profile.

   No installation verification is possible for a custom profile. After federating the node and using the deployment manager to create a server, one can start the server process to verify its functionality.

   Select the check box to launch the First steps console at the end of profile creation. We can also start the First steps console from the command line, as described in firststeps command.

   You can also start the ivt command directly from the bin directory of the profile:

   • install_root/profiles/profile/bin/ivt.sh

   • install_root\profiles\profile\bin\ivt.bat

   If you create profiles in another location, the ivt script location is within the profile_home/bin directory.

2. Observe the results in the First steps status window.

   The default log file for installation verification is the install_root/profiles/profile name/logs/ivtClient.log. If you create profiles in another location, the file path is profile_home/logs/ivtClient.log.

   The IVT provides the following useful information about the application server:

   • The application server name

   • The name of the profile

   • The profile file path

   • The type of profile

   • The node name

   • The current encoding

   • The port number for the administrative console

   • Various informational messages that include the location of the SystemOut.log file and how many errors are listed within the file

   • A completion message

   As the IVT starts the application server on a Windows platform, the IVT attempts to start the Windows service for the application server, if a Windows service exists. This is true even though the Windows service might have a manual startup type.

   If you federate a stand-alone application server, one can still run the IVT on the server.

   The IVT provides the following useful information about the deployment manager:

   • The deployment manager server name: dmgr

   • The name of the profile

   • The profile file path

   • The type of profile: dmgr

   • The cell name

   • The node name

   • The current encoding

   • The port number for the administrative console

   • Various informational messages that include the location of the SystemOut.log file and how many errors are listed within the file

   • A completion message

   As the IVT starts the deployment manager on a Windows platform, the IVT attempts to start the Windows service for the deployment manager if a Windows service exists. This is true even though the Windows service might have a manual startup type.

   See Automatically restarting server processes for more information.

3. If the log shows that errors occurred during the installation verification, correct the errors and run the IVT again. If necessary, create a new profile after correcting the error, and run the IVT on the new profile.

 

Result

The IVT program starts the server process automatically if the server is not running. Once the server initializes, the IVT runs a series of verification tests. The tool displays pass or fail status in a console window. The tool also logs results to the profile_home/logs/ivtClient.log file. As the IVT verifies your system, the tool reports any detectable errors in the SystemOut.log file.

 

What to do next

Return to Task overview: Installing to continue.

 

See also

ivt command

 

Related Tasks

Installing the product and additional software

 

See Also

firststeps command

 

---