Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2561, March 2013)

1. Initiate analysis
2. Process software selections. The system accesses the Installed Products Database (IPD) or depot
catalog to get the product information for the selected software:
For installed software, the system checks that all products are compatible with its uname
attributes. This check is controlled by the default option allow_incompatible:
• If allow_incompatible is set to false, the system produces an error stating that the
product is not compatible with the host.
• If allow_incompatible is set to true, a warning is issued stating that the product is
not compatible.
3. Check for correct states in the filesets (installed, configured or available). For installed software,
swverify also checks for multiple versions that are controlled by the
allow_multiple_versions option:
• If allow_multiple_versions is false, an error is produced that multiple versions of
the product exist and the option is disabled.
• If allow_multiple_versions is true, a warning is issued saying that multiple versions
exist.
4. Check dependencies. An error or warning is issued if a dependency cannot be met.
Dependencies are controlled by the enforce_dependencies option:
• If enforce_dependencies is true, an error is generated telling you the type of
dependency and what state the product is in.
• If enforce_dependencies is false, a warning is issued with the same information.
• If the dependency is a corequisite, it must be present before the software will operate.
• If the dependency is a prerequisite, it must be present before the software can be installed
or configured.
5. Execute verify or fix scripts on installed software in prerequisite order.
A verify script is used to ensure that the configuration of the software is correct. Possible
vendor-specific tasks for a verify script include:
• Determine active or inactive state of the product.
• Check for corruption of product configuration files.
• Check for (in)correct configuration of the product into the OS platform, services or
configuration files.
• Check licensing factors.
Vendor-supplied scripts are executed and the return values generate an ERROR (1) or a
WARNING (2).
Scripts are executed in prerequisite order.
6. Perform file-level checks for:
• Contents (mtime, size and checksum) for control_files
• Contents (mtime, size and checksum) for files
• Missing control_files, files and directories
• Permissions (owner, group, mode) for installed files
• Proper symlink values
2.3 Verifying Your Installation (swverify) 59