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

software package to perform. See Chapter 11: “Using Control Scripts ” (page 201) for a complete
discussion of control scripts.
Selecting the PSF Layout Version
You can select the layout version in the depot definition in the PSF (see “Product Specification File
Semantics” (page 175)) or with the layout_version option for swpackage, swmodify, swcopy,
or swlist.
PSF syntax conforms to the layout_version=1.0 of the IEEE Standard 1387.2: Software
Administration (POSIX). Previous versions of SD supported the POSIX layout_version=0.8
syntax, which continues to be supported.
Software depots cannot mix layout versions; they must be one or the other.
Differences between the two layout versions include the following:
• The vendor specification is handled differently.
For the current standard (layout_version=1.0), each vendor class definition is associated
only with subsequent products or bundles that contain a vendor_tag attribute that matches
the tag attribute within the vendor class definition.
For the previous standard (layout_version=0.8) or if you do not specify a
layout_version, products or bundles are automatically associated with the last vendor
class you defined at the distribution level, or from a vendor that you define within the product
or bundle. Explicitly defined vendor_tag attributes (with or without a value) take precedence.
• The corequisites and prerequisites have singular titles for layout_version=0.8 (that is,
corequisite and prerequisite). See “Dependency Specification” (page 182) for more information.
• Category objects and keywords are handled differently.
For layout_version=1.0 (current standard):
◦ category_tag is a valid product attribute that replaces the category and
category_title attributes.
◦ you can define category class objects.
For layout_version=0.8 (previous standard):
◦ category and category_title are valid product attributes that replace the
category_tag attribute.
◦ category class objects are not recognized.
For a more complete description of PSF requirements for layout_version=0.8, refer to the
swpackage.4 manual page in a previous version of HP-UX.
PSF Value Types
With the exception of vendor-defined attributes (see “Vendor-Defined Attributes” (page 175)), the
values for each attribute keyword in your PSF must match one of the specific types discussed below.
NOTE: PSF syntax conforms to the layout_version=1.0 of the POSIX 1387.2 Software
Administration standard. Previous versions of SD-UX supported the POSIX layout_version=0.8
syntax, which continues to be supported. See “Selecting the PSF Layout Version ” (page 172) for
more information.
172 Creating Software Packages










