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
• Defines the location of the product, which may have been changed from the default product
directory (if the product is locatable).
When installing to (or removing from) the primary root directory (“/”), this variable is the
absolute path to the product directory. For operations on an alternate root directory, the
variable must be prefixed by SW_ROOT_DIRECTORY to correctly reference product files.
If a product is not locatable, then the value of SW_LOCATION will always be the default
product directory defined when the product is packaged.
SW_PATH
• The search path for commands. A PATH variable defines the minimum set of commands
available for use in a control script (for example, /sbin:/usr/bin:/usr/ccs/sbin).
A control script should always set its own PATH variable, and the PATH variable must begin
with $SW.PATH. The PATH should be set as follows:
PATH=$SW_PATH
export PATH
Additional directories, like /usr/local/bin, can be appended to PATH, but you must make
sure that the commands in those directories exist.
SW_ROOT_DIRECTORY
• Defines the root directory in which the session is operating, either “/” or an alternate root
directory. This variable tells control scripts the root directory in which the products are installed.
A script must use this directory as a prefix to SW_LOCATION to locate the product’s installed
files.
All control scripts (except for the configure and unconfigure scripts) can be executed during
an install or remove task on an alternate root. If the scripts reference any product files, each
reference must include the {SW_ROOT_DIRECTORY} in the file pathname.
The scripts may only need to perform actions when installing to (removing from) the primary
root directory (“/”). If so, then the SW_ROOT_DIRECTORY can be used to cause a simple
exit 0 when the task is operating in an alternate root directory:
if test "${SW_ROOT_DIRECTORY}" != "/"
then
exit 0
fi
SW_SESSION_OPTIONS
• Contains the pathname of a file containing the value of every option for a particular command,
including software and target selections. This lets scripts retrieve any command options and
values other than the ones provided explicitly by other environment variables.
SW_SOFTWARE_SPEC
• Contains the fully qualified software specification of the current product or fileset. The software
specification allows the product or fileset to be uniquely identified. (Fully qualified software
specs include the r=, a=, and v= version components even if they contain empty strings. For
installed software, l= must also be included.)
Variables That Affect swinstall and swremove
SW_DEFERRED_KERNBLD
• This variable is normally unset. If it is set, the actions necessary for preparing the system file
/stand/system cannot be accomplished from within the postinstall scripts, but instead must
Using Environment Variables 209