After installation, verify actual checksums of installed files against a bill of materials that ships with the product. If the checksums match, the installed product is installed correctly. If the checksums differ, review the differences to determine whether a problem exists.
Install the product before attempting to compare checksums of the installed files to the shipped bill of materials.
This topic describes using the installver command to compare a set of bill-of-material files against a checksum of the installed files to verify that all installed files are correct. The product includes a bill-of-materials file for each component to provide this system of verifying installation files.
The installver tool dynamically generates a list of total components found in the installation.
When you issue one of the checksum commands from the app_server_root/bin directory, the status of the command is displayed on the terminal console.
The messages report the total number of issues found. If the issue count is zero, all of the components exist and no problems exist. The tool logs the results of the command to the app_server_root/logs/installver.log file if you use the -log parameter without specifying a file name for the log.
./installver.sh -log /tmp/waslogs/my_installver.log
Example output from components with errors
I CWNVU0160I: [ivu] Verifying. I CWNVU0170I: [ivu] The installation root directory is C:\Program Files\eclipse\eclipse3.x\workspace\ WAS.installver\test\v6x\product.installroot\ I CWNVU0300I: [ivu] The total number of user excluded files found are 0. I CWNVU0300I: [ivu] The total number of IBM excluded files found are 0. I CWNVU0180I: [ivu] Searching directory properties\version\install\6.0.0.0\backup for file listing: files.list I CWNVU0260I: [ivu] The total number of components found is: 6 I CWNVU0270I: [ivu] Gathering installation root data. W CWNVU0280W: [ivu] Component mismatch: expected mismatchcomponentname but found mismatchingname I CWNVU0360I: [ivu] The following bill of materials issue is found for component nullvaluesample: Hash must not be null or an empty string. I CWNVU0360I: [ivu] The following bill of materials issue is found for component nullvaluesample: Name must not be null or an empty string. I CWNVU0360I: [ivu] The following bill of materials issue is found for component nullvaluesample: Hash must not be null or an empty string. I CWNVU0360I: [ivu] The following bill of materials issue is found for component nullvaluesample: Permission must not be null or an empty string. I CWNVU0360I: [ivu] The following bill of materials issue is found for component symlinksample: Hash must not be null or an empty string. I CWNVU0290I: [ivu] Starting the verification for 6 components. I CWNVU0470I: [ivu] Starting to analyze: _binarycomponentsample I CWNVU0480I: [ivu] Done analyzing: _binarycomponentsample I CWNVU0470I: [ivu] Starting to analyze: nullvaluesample I CWNVU0430I: [ivu] The following file is missing: testpath I CWNVU0390I: [ivu] Component issues found : 1 I CWNVU0480I: [ivu] Done analyzing: nullvaluesample I CWNVU0470I: [ivu] Starting to analyze: overlapbinarycomponentsample W CWNVU0422W: [ivu] The following file is overlapped: lib/binaryTest.jar W CWNVU0425W: [ivu] The overlap is caused by: _binarycomponentsample I CWNVU0390I: [ivu] Component issues found : 1 I CWNVU0480I: [ivu] Done analyzing: overlapbinarycomponentsample I CWNVU0470I: [ivu] Starting to analyze: regularcomponentsample I CWNVU0440I: [ivu] The following file is different: lib/different.jar I CWNVU0410I: [ivu] fc19318dd13128ce14344d066510a982269c241b is the checksum in the bill of materials. I CWNVU0420I: [ivu] 517d5a7240861ec297fa07542a7bf7470bb604fe is the checksum on the file system. I CWNVU0440I: [ivu] The following file is different: lib/ibmtemplateexclude.jar I CWNVU0410I: [ivu] d3ac7a4ef1a8ffb4134f2f6e7f3c0d249d74b674 is the checksum in the bill of materials. I CWNVU0420I: [ivu] d3ac7a4ef1a838b4134f2f6e7f3c0d249d74b674 is the checksum on the file system. I CWNVU0430I: [ivu] The following file is missing: lib/missing.jar I CWNVU0440I: [ivu] The following file is different: lib/usertemplateexclude.jar I CWNVU0410I: [ivu] 12dea96fec20593566ab75ff2c9949596833adc9 is the checksum in the bill of materials. I CWNVU0420I: [ivu] 12dea96fec20593566ab75692c9949596833adc9 is the checksum on the file system. I CWNVU0430I: [ivu] The following file is missing: missingfilebutwithbaddirectory/missingBadDirectory.jar I CWNVU0390I: [ivu] Component issues found : 5 I CWNVU0480I: [ivu] Done analyzing: regularcomponentsample I CWNVU0470I: [ivu] Starting to analyze: symlinksample I CWNVU0480I: [ivu] Done analyzing: symlinksample I CWNVU0400I: [ivu] Total issues found : 7 I CWNVU0340I: [ivu] Done.
Example output from a typical successful installation
This example shows typical results from checking a successful installation.
You can safely ignore issues from the prereq.wccm component. These known issues do not cause overall system issues.
Carefully examine an issue before assuming that the issue is a problem.
I CWNVU0160I: [ivu] Verifying. I CWNVU0170I: [ivu] The installation root directory is C:\WebSphere\V6x-ND\ I CWNVU0300I: [ivu] The total number of user excluded files found are 1. I CWNVU0300I: [ivu] The total number of IBM excluded files found are 75. I CWNVU0180I: [ivu] Searching directory properties\version\install\6.0.0.0\backup for file listing: files.list I CWNVU0260I: [ivu] The total number of components found is: 285 I CWNVU0270I: [ivu] Gathering installation root data. I CWNVU0460I: [ivu] The utility is running. I CWNVU0460I: [ivu] The utility is running. I CWNVU0290I: [ivu] Starting the verification for 285 components. I CWNVU0470I: [ivu] Starting to analyze: activity I CWNVU0480I: [ivu] Done analyzing: activity I CWNVU0470I: [ivu] Starting to analyze: activity.impl I CWNVU0480I: [ivu] Done analyzing: activity.impl I CWNVU0470I: [ivu] Starting to analyze: activity.session I CWNVU0480I: [ivu] Done analyzing: activity.session I CWNVU0470I: [ivu] Starting to analyze: activity.session.impl I CWNVU0480I: [ivu] Done analyzing: activity.session.impl I CWNVU0470I: [ivu] Starting to analyze: acwa I CWNVU0480I: [ivu] Done analyzing: acwa I CWNVU0470I: [ivu] Starting to analyze: adapter I CWNVU0480I: [ivu] Done analyzing: adapter ... I CWNVU0470I: [ivu] Starting to analyze: prereq.wccm I CWNVU0430I: [ivu] The following file is missing: web/configDocs/activitysessionejbext/ ActivitySessionEJBJarExtension.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/activitysessionejbext/ ActivitySessionEnterpriseBeanExtension.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/activitysessionejbext/ ContainerActivitySession.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/activitysessionejbext/ classes-frame.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/activitysessionservice/ ActivitySessionService.html ... I CWNVU0430I: [ivu] The following file is missing: web/configDocs/wssecurity/consumer-binding.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/wssecurity/default-bindings.html I CWNVU0430I: [ivu] The following file is missing: web/configDocs/wssecurity/generator-binding.html I CWNVU0390I: [ivu] Component issues found : 625 I CWNVU0480I: [ivu] Done analyzing: prereq.wccm I CWNVU0470I: [ivu] Starting to analyze: prereq.webtlsrn I CWNVU0480I: [ivu] Done analyzing: prereq.webtlsrn I CWNVU0470I: [ivu] Starting to analyze: prereq.wsadie I CWNVU0480I: [ivu] Done analyzing: prereq.wsadie ... I CWNVU0470I: [ivu] Starting to analyze: wsexception I CWNVU0480I: [ivu] Done analyzing: wsexception I CWNVU0470I: [ivu] Starting to analyze: wsif I CWNVU0480I: [ivu] Done analyzing: wsif I CWNVU0400I: [ivu] Total issues found : 627 I CWNVU0340I: [ivu] Done.
See the description of the installver command for explanations of each parameter.
Go to Computing a new baseline checksum for an inventory of configured files to learn more about the installver command.