Use the installation verification tools to verify that the installation
of the product and the application server or
deployment manager profile is successful. A profile consists
of files that define the runtime environment for a
deployment manager or an application server. Verify the core product
files with the installver checksum tool. Verify each profile from its First
steps console with the IVT tool.
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 tools.
Note on installing a service packs on Microsoft® Windows Vista™ and Windows 2008 operating systems: After installing WebSphere
® Application Server
Version 6.1 on your Microsoft
® Windows
® Vista operating system,
you should install a service pack containing Version 6.1.0.9 or later
before attempting to perform any of the following actions. If you
are running Windows 2008,
you must first install a service pack containing Version 6.1.0.17
or later.
- Launching the Websphere Application Server runtime
- Verifying the installation
- Using the Profile Management tool or the manageprofiles command
to create profiles
About this task
Use the installation verification tools to gain assurance that
the product is successfully installed. Two tools exist. This task describes
when and how to use to both tools. One tool is the checksum tool (the installver
tool). The installver tool compares the checksum of each installed file to
the correct checksum value for each file and reports differences. The other
tool is the installation verification test (IVT). The IVT tests deployment
manager profiles and stand-alone application server profiles 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.
The Profile Management tool creates profiles. After
creating a profile, the Profile Management tool 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
- Run the installver tool to verify that all files are correctly
installed.
See Verifying checksums of installed files for
more information.
- Use the installation verification test to verify the proper creation
of profiles.
- 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, you
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.
You 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:
If you create profiles in another location, the ivt script
location is within the plugins_root/bin directory.
- Observe the results in the First steps status window.
The log file for installation verification is the profile_root/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, you 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.
- 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.
Results
The installver tool validates the integrity of all installed files.
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 plugins_root/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.
You can also
install other packages on the product installation image, such as IBM HTTP
server, the Web server plug-ins, or the Application Client.
See Task overview: Installing for more information.