Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)
Table Of Contents
- Software Distributor Administration Guide
- Contents
- HP secure development lifecycle
- About This Document
- 1 Introduction to Software Distributor
- SD-UX Overview
- SD-UX Concepts
- Using the GUI and TUI Commands
- The Terminal User Interface
- Starting the GUI/TUI Commands
- Window Components
- Opening and closing items in the object list
- Marking Items in the Object List
- Preselecting Host Files
- Software Selection Window
- Session and File Management—The File Menu
- Changing Software Views—The View Menu
- Changing Options and Refreshing the Object List—The Options Menu
- Performing Actions—The Actions Menu
- Getting Help—The Help Menu
- XToolkit Options and Changing Display Fonts
- Working from the Command Line
- 2 Installing Software
- Installation with swinstall
- Features and Limitations
- Installing with the GUI
- Installing from the Command Line
- Installation Tasks and Examples
- Updating to HP-UX 11i
- Installing Patches
- Recovering Updated Files
- Installing Software That Requires a System Reboot
- Using Software Codewords and Customer IDs
- Re-installing Software Distributor
- Installing Multiple Versions
- Installing to an Alternate Root
- Compatibility Filtering and Checking
- Software Selection Checking
- Configuring Your Installation (swconfig)
- Verifying Your Installation (swverify)
- Installation with swinstall
- 3 Managing Installed Software
- 4 Managing Software Depots
- Depot Management Commands and Concepts
- Copying Software Depots
- Registering and Unregistering Depots (swreg)
- Verifying Signed Software Signatures
- Additional Depot Management Tasks and Examples
- Combining Patch Depots
- Creating a Tape Depot for Distribution
- Setting Depot Attributes
- Creating a Network Depot
- Managing Multiple Versions of HP-UX
- Listing Registered Depots
- Listing the Contents of a Depot (swlist -d)
- Source Depot Auditing
- Verifying a Depot (swverify -d)
- Removing Software from Depots
- Removing a Depot
- 5 HP-UX Patching and Patch Management
- 6 Using Jobs and the Job Browser
- 7 Remote Operations Overview
- 8 Reliability and Performance
- 9 SD-UX Security
- 10 Creating Software Packages
- Overview of the Packaging Process
- Identifying the Products to Package
- Adding Control Scripts
- Creating a Product Specification File (PSF)
- Product Specification File Examples
- PSF Syntax
- PSF Object Syntax
- Selecting the PSF Layout Version
- PSF Value Types
- Product Specification File Semantics
- Re-Specifying Files
- Packaging the Software (swpackage)
- Packaging Tasks and Examples
- Registering Depots Created by swpackage
- Creating and Mastering a CD-ROM Depot
- Compressing Files to Increase Performance
- Packaging Security
- Repackaging or Modifying a Software Package
- Packaging In Place
- Following Symbolic Links in the Source
- Generating File Revisions
- Depots on Remote File Systems
- Verifying the Software Package
- Packaging Patch Software
- Writing to Multiple Tapes
- Making Tapes from an Existing Depot
- 11 Using Control Scripts
- Introduction to Control Scripts
- General Script Guidelines
- Packaging Control Scripts
- Using Environment Variables
- Execution of Control Scripts
- Execution of Other Commands by Control Scripts
- Control Script Input and Output
- File Management by Control Scripts
- Testing Control Scripts
- Requesting User Responses (swask)
- Request Script Tasks and Examples
- 12 Nonprivileged SD
- A Command Options
- B Troubleshooting
- Error Logging
- Common Problems
- Cannot Contact Target Host’s Daemon or Agent
- GUI Won’t Start or Missing Support Files
- Access To An Object Is Denied
- Slow Network Performance
- Connection Timeouts and Other WAN Problems
- Disk Space Analysis Is Incorrect
- Packager Fails
- Command Logfile Grows Too Large
- Daemon Logfile Is Too Long
- Cannot Read a Tape Depot
- Installation Fails
- swinstall or swremove Fails With a Lock Error
- Use of Square Brackets ([ and ]) Around an IPv6 Address Causes an Error
- Some SD commands do not work after network configuration changes
- C Replacing or Updating SD-UX
- D Software Distributor Files and File System Structure
- Glossary
- Index

copyright The text (or a pointer to a filename) for the copyright information
for the depot’s contents.
description The description of the target depot; either the text itself or a
pointer to a filename that contains the text.
number The part or manufacturing number of the distribution media (CD
or tape depot).
title The full name of the target depot (tape) being created/modified
by swpackage.
end Ends the distribution specification, no value is required. This
keyword is optional. If you use it and it is incorrectly placed, the
specification will fail.
Vendor Specification
The vendor attributes let you add a description to the PSF.
The layout_version defined for the PSF file determines how vendor specifications are associated
with products and bundles. If a layout_version is not defined or is defined as 1.0, vendor
specifications will be associated with all subsequent products and bundles that define a matching
vendor_tag attribute.
If a layout_version of 0.8 is specified, all subsequent products and bundles will automatically
be assigned to a vendor_tag from the last vendor object defined at the distribution level, if any,
or from a vendor object defined within a product or bundle, unless a vendor_tag is explicitly
defined.
The following is an example of a vendor specification:
vendor
tag HP
description < data/description.hp
title Hewlett-Packard Company
end
Each keyword defines an attribute of a vendor object. If a vendor specification is included in the
PSF, swpackage requires the vendor and tag keywords.
NOTE: The vendor specification is not the same as vendor-defined attributes. See “Vendor-Defined
Attributes” (page 175) for more information.
vendor Keyword that begins the vendor specification.
tag Defines the identifier (short name) for the vendor.
title Defines the full name (one line description) for the vendor.
description Defines the multi-paragraph description of the vendor; the value is either the
text itself (within double-quotes) or a pointer to the filename containing the text.
end Ends the vendor specification. This keyword is optional.
Category Specification
(Does not apply to layout version 0.8.) A software collection can contain a list of category objects
that are used as a selection mechanism. Category objects are identified by the keyword “category”
and contain additional information about the category. The category_tag attribute points to a
particular category object and can appear anywhere within a product, bundle, subproduct, or
fileset.
All software objects with the attribute of is_patch set to true are automatically assigned a category
of “patch.”
176 Creating Software Packages