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
For More Information
See Appendix A (page 227) for complete descriptions of each default.
swmodify Tasks and Examples
Here are some examples of how you can use swmodify to change catalog files or IPDs:
Adding Information to the IPD
To add descriptions of files /tmp/a, /tmp/b, and /tmp/c to an existing fileset:
swmodify -x files=/tmp/a /tmp/b /tmp/c PRODUCT.FILESET
If a control script adds new files to the installed file system, the script can use swmodify to make
a record of the new files.
Changing Existing IPD Information
To create some new bundle definitions for products in an existing depot:
# swmodify -d -s new_bundle_definitions \
\* @ /mfg/master_depot
If a product provides a more complex configuration process, a script can set the fileset’s state to
configured upon successful completion.
To change the values of a fileset’s attributes:
# swmodify -a state=installed PRODUCT.FILESET
To change the attributes of a depot:
# swmodify -a title=Master Depot \
-a description=/tmp/mfg.description \
@ /mfg/master_depot
Defining New Objects
You can import an existing application (not installed by SD-UX) by constructing a simple Product
Specification File (PSF) describing the product and then invoke swmodify to load that definition
into the IPD.
To create a new fileset definition (if the PSF contains file definitions, then add those files to the new
fileset):
swmodify -s new_fileset_definition
Removing Installed Software (swremove)
The swremove command removes software that has been installed on a host. Before its removal,
the software is first unconfigured. swremove also removes software products that have been copied
to a software depot.
swremove Features and Limitations
• Removes files from the specified location. It removes symbolic links, but not the targets of
symbolic links. It also lists busy files that were not removed.
• Automatic use of dependencies to automatically select software on which to operate (in addition
to any software you specify directly).
• Ability to run control scripts as part of the removal:
Undoes host configuration performed by configure scripts.Unconfigure
Checkremove Analyzes each target to determine if removal and unconfiguration can take
place. If this check fails, an object cannot be removed.
Preremove Performs additional file operations, such as removing files created by a
preinstall script.
76 Managing Installed Software