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

Key points in this structure are:
• Where are shareable (for example, executables) and non-shareable (for example, configuration)
files installed?
• How is configuration used to put non-shareable files in place?
Determining Product Structure
Determine the product structure that your software should follow. SD-UX provides four levels of
software objects:
Level Objects
Filesets (Required) Filesets include the actual product files, information that describes
those files (attributes) and separate control scripts that are run before, during
or after the fileset is installed, copied or removed. Filesets are the smallest
manageable (selectable) software object. Files must be grouped into one or
more filesets. Filesets must be grouped into one or more products. (Filesets can
be members of only a single product.)
Subproducts (Optional) Subproducts are used to group related filesets within a product if the
product contains several filesets. Subproduct definitions are optional.
Products (Required) Filesets (and/or subproducts) must be grouped into one or more
products. They are usually grouped into collections that form a set of related
software, or match the products that a customer purchases. The SD-UX commands
maintain a product focus, while still allowing the flexibility to manage subsets
of the products via subproducts and filesets.
Bundles (Optional) Bundles are provided only by the HP factory. Customer packaging
of bundles is not supported.
NOTE: You can define different versions of products for different platforms and operating systems,
as well as different revisions (releases) of the product itself. You can include different product
versions on the same distribution media.
Adding Control Scripts
SD-UX supports execution of product and fileset control scripts that allow you to perform additional
checks and operations with other HP-UX commands and functions. The swask, swinstall,
swconfig, swverify, and swremove commands each can execute one or more control scripts
on the primary roots. You can write the scripts and include them in your software package. All
scripts are optional but many times are needed correctly complete the task that you want your
software package to perform. See Chapter 11: “Using Control Scripts ” (page 201) for a complete
discussion of control scripts.
SD-UX supports the following types of scripts, which can be defined for products and fileset:
Checkinstall Analyses each target to determine if the installation and configuration can
take place. (Executed by swinstall.)
Checkremove Analyses each target to determine if removal and unconfiguration can take
place. (Executed by swremove.)
Configure Configures installed filesets or products. (Executed by swconfig and
swinstall.)
Fix Corrects and reports on problems in installed software. (Executed by
swverify.)
Postinstall Performs additional install operations (such as resetting default files)
immediately after a fileset or product has been installed. (Executed by
swinstall.)
166 Creating Software Packages