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
• Be in the proper software state (the dependency must be configured if the software dependent
on it is to be installed and configured, installed if software dependent on it is to be installed
but not configured, or available if the software dependent on it is to be copied)
• Be free of errors (for example, no incompatibility errors).
If you select software that has a dependency and more than one available object resolves that
dependency, SD-UX automatically selects the latest compatible version.
Types of Dependencies
Software packagers can define corequisites, prerequisites, and exrequisites as dependencies.
These dependencies can be specified between filesets within a product, including expressions of
which versions of the fileset meet the dependency. Dependencies can also be specified between
a fileset and another product. Expressions for revisions and other product attributes are supported.
Corequisites An object requires another to operate correctly, but does not imply any load
order. However, corequisites modify the load order in some cases. For more
information on options, see “Using Command Options” (page 37).
Prerequisites An object requires another to be installed and/or configured correctly before
it can be installed or configured respectively. Prerequisites do control the
order of operations.
Exrequisite An object requires the absence of another object before it can be installed
or configured.
Working with Protected Software
Some HP software products are protected software. That is, you cannot install or copy the software
unless you provide a codeword and customer ID. The customer ID uniquely identifies the owner of
the codeword and lets you restrict installation to a specific owner. To find your codeword and
customer ID, examine the CD certificate shipped with your software.
It is your responsibility to ensure that the codeword and software are used properly in this manner.
One codeword unlocks most or all of the products on your media. When you purchase additional
protected products, HP provides additional codewords. SD-UX keeps tracks of codewords as you
enter them. This means you do not have to enter the codeword each time you access the software.
The swinstall, swcopy, and swlist commands make use of codewords in managing software.
Using the GUI and TUI Commands
The swinstall, swcopy, swlist, swremove commands each provide a Graphical User
Interface and Terminal User Interface. Advantages of the GUI/TUI include:
• You can quickly create and visually monitor software management tasks interactively
• You can easily analyze the effects of tasks and retry tasks that fail.
• You do not have to be familiar with a broad range of defaults, options, software selections,
and other variables that are required to enter complex commands on the command line.
(Additional GUI interfaces are available if you have enabled remote operations. See Chapter 7:
“Remote Operations Overview” (page 116).)
The Terminal User Interface
The terminal user interface lets you use the SD-UX GUI capabilities on systems with text-based
terminals. With the TUI, you use the Arrow, Tab, Space, and Return keys to navigate.
Using the GUI and TUI Commands 23