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
Cumulative patch See superseding patch.
Daemon The SD-UX program that schedules the agent to perform software management tasks. On a SD-UX
controller, the daemon polls the job queue for scheduled jobs.
data_model_revision
The internal attribute for SD-UX INDEX file syntax. Layout_version 1.0 uses data_model_revision
2.40; whereas, layout_version 0.8 uses data_model_revision 2.10.
DCE Distributed Computing Environment. Technology used by SD-UX for distributed communications.
Controllers, daemons, and agents communicate using the DCE Remote Procedure Call (RPC).
Default Hosts File The file (either/var/adm/sw/defaults.hosts for system level defaults) or $HOME/.sw/
defaults.hosts for user level defaults) that contains the default list of hosts for SD-UX
commands.
Default Options Changeable values that affect SD-UX command behaviors and policies. Default options are
contained in the defaults file. See Appendix A (page 227) for more information.
Defaults File The file (either /var/adm/sw/defaults for system-wide defaults or $HOME/.sw/defaults
for user- level defaults), which contains the default options and operands for each SD-UX command.
Delegation SD-UX provides a controlled access to depot-resident products: both the host where the agent is
running and the user initiating the call (delegation) must have read access.
Dependency A relationship between fileset in which one requires another in a specific manner. For example,
before fileset A can be installed, it may require fileset B to be installed. SD-UX supports corequisite,
exrequisite, and prerequisite dependencies. See Dependent.
Dependent A fileset that has a dependency on another fileset. For example, if fileset A depends on fileset B,
then B is a dependent or has a dependency on A.
Depot A repository of software products and a catalog, organized so SD-UX commands can use it as
a software source. The contents of a depot reside in a directory structure with a single, common
root. A depot can exist as a directory tree on a SD-UX file system or on CD-ROM media, and it
can exist as a tar archive on a serial media (tape). All depots share a single logical format,
independent of the type of media on which the depot resides. Depots can reside on a local or
remote system. You can package software directly into a depot or copy packaged software into
the depot from elsewhere.
Depot Source See depot.
Description An attribute for products and filesets, usually a paragraph description of that product or fileset.
Destination The path at which a file will be installed.
Details Dialog In the GUI or TUI, a dialog box that lets you get more information about a specific process to
monitor its progress.
Developer Host A system where software application files are placed for further integration and preparation for
distribution. You may use a developer host to assemble, organize, and create product tapes or
depots.
Directory In packaging, a keyword that defines the a directory for a product object. The directory specified
is a default, absolute pathname to the directory in which the product will be installed.
Directory Depot The directory on a target host where a depot is located. The default is /var/spool/sw.
Disk Space
Analysis (DSA)
A process that determines if a host’s available disk space is sufficient for the selected products
to be installed.
Downdating Overwriting an installed version of software with an older version.
DSA See Disk Space Analysis
End An optional keyword that ends the software object specification in a PSF. No value is required.
Exrequisite A dependency in which a fileset requires the absence of another fileset before it can be installed
or configured. For example, if fileset A cannot be installed or configured if fileset B is already
installed, fileset B is an exrequisite for fileset A.
Fileset A collection of files. Most SD-UX operations are performed on filesets.
269