The installver command performs two main functions. The tool computes a checksum on the installed files and compares the checksum to the shipped bill of materials for the product. The installver command can also compute a new baseline checksum for each file in the inventory of a configured system to use to identify file changes in later comparisons.
This topic describes the location of the command file, command syntax, and links to task information about using the tool.
The default log file is the app_server_root/logs/installver.log file. You can redirect the output using the -log parameter and an argument. Use the -log parameter without the file argument to generate the default log file.
Computing the checksum
The installver tool computes a checksum for each installed file in the product. The tool compares each computed checksum to the correct checksum for the file. The correct checksums are shipped in the bill-of-material files. One bill-of-materials file exists for each component.
The tool parses the bill-of-materials file for each component to find the correct checksum value for each file in the component. Each product file has an entry in some bill-of-materials file. The entry for a product file lists the product file path and the correct checksum value.
Shipped bill-of-material files
Each bill-of-materials file is named files.list. Each component has one files.list file. Each files.list file is in one of the app_server_root/properties/version/install/6.1.0.0/backup/component_name directories. A component_name directory exists for each component.
For instance, the files.list file for the activity component is in the app_server_root /properties/version/install/6.1.0.0/backup/activity directory. The file resembles the following example:
<?xml version="1.0" encoding="UTF-8"?> <componentfiles componentname="activity"> <file> <relativepath>properties/version/activity.component</relativepath> <checksum>1a20dc54694e81fccd16c80f7c1bb6b46bba8768</checksum> <permissions>644</permissions> <installoperation>remove</installoperation> </file> <file> <relativepath>lib/activity.jar</relativepath> <checksum>2f056cc01be7ff42bb343e962d26328d5332c88c</checksum> <permissions>644</permissions> <installoperation>remove</installoperation> </file> </componentfiles>
Comparing the computed checksum to the correct checksum
As the tool processes each product file in each bill-of-materials file, the tool also computes the actual checksum value of the corresponding installed product file. The tool then compares the checksum of the product file to the correct checksum value in the bill-of-materials file. The tool then reports any differences.
Location of the command file
Change directories to the bin directory to start the installver tool from the command line. The tool runs on any supported operating system except z/OS®.
installver
Use the following command syntax to automatically check the bill of materials against the installed file system.
See Verifying against the bill of materials for examples of using the command to compare the installed files to the product bill-of-materials files.
See Comparing specific file and component checksums for examples of using the command to compare only files or components that you specify.
See Excluding files from a checksum comparison for examples of using the command to exclude files from the comparison.
installver -createprofiletemplate
The following parameters are associated with the command.
Use the following syntax to create and compare an inventory of configured files to the currently installed files.
Create an inventory list of the files that are currently installed in the installation root directory
Compare the inventory list to files that are currently installed in the installation root directory
Compare and display trace results
After verifying your installation, you can create profiles or deploy an application on an existing application server profile.
After installing, updating, and verifying, the next step is to use the product. If you created a standalone application server or a cell, start the application server, or the deployment manager, nodeagent, and federated application server, to use the administrative console to deploy an existing application. See Fast paths for WebSphere® Application Server for more information.