WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Using the installation verification tool

Use the installation verification tool (IVT) to verify that the installation of a WebSphere ESB stand-alone or deployment manager profile was successful.

Before you begin

After installing the WebSphere ESB and creating a stand-alone server profile or deployment manager profile you are ready to use the installation verification tools.

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

Why and when to perform this task

Use the installation verification tool (IVT) to gain assurance that the product is successfully installed. The IVT program runs a series of verification tests to make sure that the server processes can start.

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

IVT can be run from a selection on the First steps console, or from a command line. After the WebSphere ESB is installed or after a profile is created, a prompt is displayed for starting the First steps console, from which you can choose to run the installation verification.

Use the installation verification test to verify the proper creation of profiles.

Steps for this task

  1. Click Installation verification on the First steps console after installing the product, or after profile creation.
    You can also start the First steps console from the bin directory of the profile:
    • LINUX platforms UNIX platforms install_root/profiles/profile_name/bin/ivt.sh
    • For Windows platforms install_root\profiles\profile_name\bin\ivt.bat

    If you create additional profiles, 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 WebSphere ESB:
    • 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 theSystemOut.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 server or the deployment manager, 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, you can still run the IVT on the server.

  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 tool starts the server process of a profile 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

After installing the product and verifying the installation, you can configure the installation by creating more profiles.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_ivt.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)