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

• The swinstall and swremove commands do not automatically run configuration scripts
when you specify an alternate root directory with these commands. You must run swconfig
to configure or unconfigure alternate roots.
• Automatic configuration can also be postponed on software installed to the root directory, /
(for example, when multiple versions are installed), by using the defer_configure command
option with swinstall or swremove.
• By default, swconfig only supports configuration of compatible software. You can switch
this feature on or off with the allow_incompatible option.
• If a fileset relies on another software product for proper operation, that software product must
be in a configured state and is controlled by the enforce_dependencies option.
• The swconfig command configures only one version of a fileset at a time, controllable through
the allow_multiple_versions option.
• The swconfig command moves software between the installed and configured states.
• The swconfig command uses dependencies to automatically select software on which to
operate (in addition to any software you specify directly). See “Software Dependencies ”
(page 22) for more information.
NOTE: When a swinstall session includes a reboot fileset (such as when you update the core
HP-UX operating system to a newer release), the configure scripts are automatically run as part of
the system start-up process after the system reboots. You do not have to run swconfig to complete
the configuration.
The Configuration Process
The configure process has three phases: selection, analysis, and configuration.
Phase I: Selection
In this phase, swconfig resolves the software selections. The swconfig behavior can be controlled
using the enforce_selections option. If set to false (default), swconfig proceeds even
when only one software selection is available in the source. If set to true, swconfig proceeds
only if all of the software selections are available.
Phase II: Analysis
In this phase, swconfig determines if the software can be configured successfully (includes checks
of software existence, prerequisites). If you execute swconfig with the -p (preview) option, the
command stops after completing analysis and does not change anything on the host.
Analysis takes place on the local host. The configuration phase will not take place if any errors
occur during analysis. Errors in the analysis phase will only exclude those products that had errors
in them. If only warnings occur, the task continues.
The sequential analysis tasks on the host are:
1. Initiate analysis.
2. Process software selections:
Get information from the Installed Product Database and check for compatibility.
The system checks that all software is compatible with the host’s uname attributes. This check
is controlled by the allow_incompatible command option. If it is set to false, the system
produces an error; if set to true, it produces a warning.
Configuring Your Installation (swconfig) 53