Software Distributor Administration Guide (March 2009)

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
76 Installing Software