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
The version component has the form: [,r <op> revision][,a <op> arch]
[,v <op> vendor][,c <op> category][,q=qualifier][,l=location]
[,fr <op> revision][,fa <op> arch]
where:
• Fully qualified software specifications include the r=, a=, and v= version components, even
if they contain empty strings. For installed software, l= is also required.
• All version components are repeatable within a single specification (e.g. r>=A.12, r<A.20).
If multiple components are used, the selection must match all components.
• The <op> (relational operator) component performs individual comparisons on dot-separated
fields and can be of the form:
=, ==, >=, <=, <, >, or !=
For example, r>=B.11.11 chooses all revisions greater than or equal to B.11.11. The
system compares each dot-separated field to find matches.
• The = (equals) relational operator lets you specify selections with the shell wildcard and
pattern-matching notations: [ ], *, ?, and ! For example, the expression r=1[01].* returns
any revision in version 10 or version 11.
• No space or tab characters are allowed in a software selection.
• qualifier is a string that can be attached to any product or bundle to help you filter a
software specification.
• location applies only to installed software and refers to software installed to a location
other than the default product directory.
• fr and fa apply only to filesets.
• A software instance_id can take the place of the version component. It has the form:
[instance_id] within the context of an exported catalog, where instance_id is an integer
that distinguishes versions of products and bundles with the same tag.
Software Files
To keep the command line shorter, software selection input files let you specify long lists of software
products. With a software selection file, you only have to specify the single file name.
The -f command-line option lets you specify a software selection file. For example:
swinstall -f mysoft -s /mnt/cd @ targetB
In this example, the file mysoft (which resides in the current working directory for software files)
contains a list of software selections for the depot /mnt/cd.
In the software file, blank lines and comments (lines beginning with #) are ignored. Each software
selection must be specified on a separate line.
How Commands and Options Interact with Selections
The enforce_selections command option enables you to control the behavior of the
swinstall, swcopy, swremove, swconfig and swverify commands based on the availability
of the software selections. If enforce_selections is set to the default value of false, then
any of these commands continue to execute even if any one of the selections is available. If
enforce_selections is set to true, then any of these commands continue to execute only if
all the software selections are available.
For more information on the options, see “Using Command Options” (page 37).
36 Introduction to Software Distributor