After installing the product or after installing maintenance packages, you can use the installation verification utility (IVU) to compute checksums of the installed file set to verify the checksum against the checksum in the product bill of materials.
Installing the product also installs the IVU, which is the installver_wbi.bat command-line tool.
You use the installver_wbi.bat command-line tool to compute a checksum on the installed files and compare the checksum to the product bill of materials.
The installation verification utility tool is installed during the installation of WebSphere® ESB.
You can also use the IVU to compute a new checksum for a system after you make significant configuration changes. The installver_wbi.bat tool computes a new baseline checksum for each file in the inventory of a configured system to use to identify file changes in the later comparisons. Such a comparison is useful for detecting file tampering on the configured system, for example, you can use the new checksums to compare installations on multiple systems. The following graphic illustrates the main use-cases where you can perform product verification at any point of the product life-cycle or use the inventory file, which is part of the baseline checksum feature, to provide full-file verification of a configured system.
Although the most common use of the tool is to compare the product bill of materials to the installed file set, other tasks are also possible.
To verify the checksums of installed files, perform the following steps.
When you are satisfied that your installed or updated file set matches the product bill of materials, you are finished verifying the product files.
If you detect a problem, see if the problem is a known problem by checking the WebSphere Enterprise Service Bus Support Web site.
The IVU performs the tasks using the logic described in the following graphic:
After verifying your installation, you can create profiles or deploy an application on an existing application server profile.