Use the installation verification tool (IVT) 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 each profile from its First steps console
with the IVT.
Before you begin
After installing the Network Deployment product and
creating a deployment manager or application server profile, you are
ready to use the IVT.
About this task
Use the IVT to gain
assurance that the product is successfully
installed. The IVT tests deployment manager profiles
and standalone 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 standalone application server.
On a standalone 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
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:
- profile_root/bin/ivt.sh server1
profile01
- profile_root\bin\ivt.bat server01
profile01
If you create profiles in another
location, the ivt script
location is within the profile_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:
- Application server name
- Name of
the profile
- Profile file path
- Type of profile
- Node
name
- Current encoding
- 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
- 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 standalone
application server, you can still run the IVT on the server.
The IVT provides the following useful information
about the deployment manager:
- Deployment manager
server name: dmgr
- Name of the profile
- Profile file
path
- Type of profile: dmgr
- Cell name
- Node name
- Current encoding
- 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
- 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.
- 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
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_root/logs/ivtClient.log file.
As the IVT verifies your system, the tool reports any detectable errors
in the SystemOut.log file.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log,
and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
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.