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

# Optional vendor specification
# Optional subproduct specification
# REQUIRED FILESET SPECIFICATION
end
For each product object specified, swpackage requires only the product and tag keywords, plus
one or more fileset definitions. For each bundle specified, swpackage requires the bundle, tag
and contents keywords.
product Required keyword that begins the product specification.
tag The product’s identifier (short name).
architecture The target system on which the product or bundle will run. Provides a
human-readable summary of the four uname attributes (machine_type,
os_name, os_release and os_version), which define the exact target
system(s) the product supports.
bundle Required keyword that begins the bundle specification.
category_tag A repeatable tag-based attribute identifying a set of categories of which the
software object is a member. This is used as a selection mechanism and can
be used independent of patches. The default value is an empty list or patch
if the is_patch attribute is set to true. Like vendor_tag, this attribute can
be used as a pointer to a category object that contains additional information
about the category (for example, a one-line title definition and a description
of the category).
NOTE: The category tag patch is reserved. When the is_patch product
attribute is set to true, a built-in category_tag attribute of value patch is
automatically included with the product definition.
contents The list of fully qualified (all version distinguishing attributes included)
software specs for the bundle.
copyright A multi-line description of the product’s copyright; either the text itself (in double
quotes) or a pointer to the filename that contains the text.
description A multi-paragraph description of the product; either the text itself (within
double-quotes) or a pointer to the filename that contains the text.
directory The default, absolute pathname to the directory in which the product’s files
will be installed (the root directory of the product). If not specified, swpackage
assigns a value of /.
is_locatable Defines whether a product or bundle can be installed to any product directory,
or whether it must be installed into a specific directory. The attribute can be
set to true or false. If not defined, swpackage sets the default attribute to
“false.”
is_patch A boolean flag that identifies a software object as a patch. The default value
is false. When set to true, a built-in category_tag attribute of value patch
is automatically included with the product definition.
machine_type The system type on which the product will run. If not specified, the keyword
is assigned a wildcard value of *, meaning it will run on all machines. If there
are multiple platforms, you must separate each machine designation with a
| (vertical bar). For example, a keyword value of 9000/7*|9000/8* means
the product will run on all HP Series 9000 Model 7XX or all HP 9000 Series
8XX machines. Alternatively, the value 9000/[78]* would also work.
Other examples:
178 Creating Software Packages