The ivt command starts the installation
verification test (IVT) program. The IVT verifies that the installation
of the application server or deployment manager profile
was successful. A profile consists of files that
define the runtime environment for a deployment
manager or an application server. Each profile has its own ivt command.
Note: This topic references one or more of the application
server log files. As a recommended alternative, 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 on distributed and IBM® i systems. You can also use
HPEL in conjunction with your 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.
The IVT program starts the application server or deployment manager automatically if the server
process is not already running. After the server process initializes,
the IVT runs a series of verification tests and displays pass or fail
status in a console window.
The IVT program scans the SystemOut.log file
for errors and verifies core functionality of the profile.
You
can start the IVT program from the command line or from the First
steps console.
Location of the command file
The location
of the installation verification test script for a profile is the
profile_root/bin directory.
The script file name is:
Parameters
The following parameters are
associated with this command.
- server_name
- Required parameter that identifies the name of the server process,
such as server1 or dmgr
- profile_name
- Required parameter that identifies the name of the profile that
contains the server definition
- -p server_port_number
- Optional parameter that identifies the default_host port when
the port is not 9080, which is the default
- -host machine_host_name
- Optional parameter that identifies the host machine of the profile
to test
The default is localhost.
Syntax for the ivt command
Logging
The ivt command
logs results to the profile_root/logs/ivtClient.log file.
Note: This topic references one or more of the application
server log files. As a recommended alternative, 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 on distributed and IBM i systems. You can also use
HPEL in conjunction with your 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.