Software Distributor Administration Guide for HP-UX 11i

Installing Software
Configuring Your Installation (swconfig)
Chapter 2 85
• If the dependency is a prerequisite, the configuration fails.
• If the dependency is a corequisite, the configuration of this fileset
will likely succeed, but the product may not be usable until its
corequisite dependency is installed and configured.
Phase III:
Configuration
In this phase, the actual software configuration takes place. Configure or
unconfigure scripts are executed and the software state is changed from
installed to configured (or unconfigured).
The purpose of configuration is to configure the host for the software and
configure the product for host specific information. For example,
software may need to change the host’s .rc setup, or the default
environment set in /etc/profile. Or you may need to ensure that
proper codewords are in place for that host or do some compilations.
Unconfiguration reverses these steps.
The sequence of configuration tasks is shown below. Products are
ordered by prerequisite dependencies, if any. Fileset operations are also
ordered by any prerequisites.
1. (Un)configure each product.
2. Run scripts for associated filesets, checking return values.
If an error occurs, the fileset is left in the installed state. If a warning
occurs, the fileset will still be configured.
3. Update the IPD to show the proper installed or configured state.
Configure scripts must also adhere to specific guidelines. For example,
these scripts are only executed in the context of the host that the
software will be running on, so they are not as restrictive as customized
scripts. For more information on scripts, see Chapter 11, “Using Control
Scripts,” on page 369.