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
default value is false. If the is_patch attribute is true, is_sparse is also
set to true for the fileset, although it can be forced to false.
machine_type The machine 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 machine 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:
* If not concerned with the machine type.
9000/7??:32* Series 700, 32-bit capable hardware required.
*:*64 64-bit capable hardware required.
*:32: 32-bit capable hardware required.
9000/7??:*64 Series 700, 64-bit capable hardware required.
9000/[78]??:32* Series 800, 32-bit capable hardware required.
9000/[78]??:*64 Series 800, 64-bit capable hardware required.
The value is matched against a target’s uname -m or getconf
_CS_HW_CPU_SUPP_BITS result.
os_name Defines the operating system(s) on which the files will run if a fileset
architecture has been defined. (If not specified, swpackage assigns a
value of *, meaning the files run on all operating systems.) If there are
multiple operating systems, use wildcards or use the ’|’ character to
separate them. This attribute should pattern match to the value of uname
-s or getconf KERNEL_BITS on the supported target systems.
os_release Defines the operating system release(s) on which the files will run. (If not
specified, swpackage assigns a value of *, meaning the files run on all
releases.) If there are multiple operating system releases, use wildcards or
use the ’|’ character to separate them. This attribute should pattern match
to the value of uname -r on the supported target system(s).
os_version The version number of the operating system(s) on which the product will
run. If not specified, the attribute is assigned a value of *, meaning it runs
on any version. If there are multiple operating systems, use wildcards or
the | symbol to separate them. The value is matched against a target’s
uname -v result.
revision Defines the revision (release number, version number) of the fileset.
supersedes Used when a patch is replaced by (or merged into) a later patch. The
attribute indicates which previous patches are replaced by the patch being
installed or copied. This attribute value is a list of software specifications
of other patches that this patch supersedes.
title Defines the full name (one-line description) of the fileset.
end Optional keyword to end the fileset specification. No value is required. If
you place this keyword incorrectly, the file specification will fail.
Dependency Specification
The swinstall, swcopy, swverify, and swremove commands recognize software
dependencies. The default behavior for swinstall, for example, prevents an install unless all
dependencies are met.
182 Creating Software Packages