Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

a. execute the preinstall script
b. install the files
c. execute the postinstall script
3. Execute the product postinstall script
If any of these steps fails (e.g., a lost source or a script error) then the undo scripts are run, and
the files restored from the point of failure in reverse order.
NOTE: Patches created using the features capabilities described may maintain saved files. In
this case, patches can be removed (rolled back) or committed (by removing saved files). See
Chapter 5: “HP-UX Patching and Patch Management” (page 102) for more information on patches.
NOTE: The use of autorecover_product=true during an update of the HP-UX OS is not
supported.
Installation With Separate Configuration
NOTE: Because deferring configuration of OS software and patches can leave the system in an
unusable state, do not use this technique with HP-supplied software.
If you create your own software that includes configuration scripts to be performed automatically
after installation, performing the configuration separately can increase the reliability of the overall
installation process.
To install without configuring, set the defer_configure option to true for swinstall. Then,
after all the installs have completed successfully, you can run the configure scripts for all targets at
once by using the swconfig command.
Multiple Versions
SD-UX supports installing multiple revisions of the same software on a system at the same time, if
the software supports it. By using multiple installed versions, recovery can be supported at the
system or task (all systems) level.
Installing a second version requires some careful planning, as well as understanding how to identify
multiple versions on the system.
Each product has a product directory attribute. The installed location on the target is by default
the same as the product directory. For example, a product Foo might have a product directory of
/opt/foo. You can list the locations of installed software with:
swlist -l product -a location
or
swlist -l product -a software_spec
A common practice is to install a second version of the product. When installing this software, a
new location must be selected. In the case of the product Foo, the new location might be
/opt/foo.v2. After specifying the new location (i.e., by adding l=/opt/foo.v2 after the
product tag in the GUI or CLI), swinstall will replace the product directory portion of all files
with the new product location.
NOTE: The allow_multiple_versions option must be set to true for swinstall to install
multiple versions of the software. The new version will not be configured by swinstall if there
is another version configured.
After a second version has been installed, each version can be identified either by the location
(Foo,l=/opt/foo and Foo,l=/opt/foo.v2), by the revision (Foo,r=1.0 and Foo,r=2.0),
or both. You can list the locations and revisions of all versions with:
swlist -l fileset -a location -a revision
Installation With Separate Configuration 139