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 behavior is as follows:
◦ If neither global_srp nor local_srp_list option is specified, swinstall will
install on the global view and all system containers.
◦ If global_srp=true, and local_srp_list option is not specified, swinstall will install
only on the global view.
◦ If global_srp=true, and local_srp_list is set, swinstall will install on the global
view and the listed system containers.
◦ If local_srp_list is set, and global_srp option is not specified, swinstall will
install only in the listed system containers.
Applies only to swinstall, swremove, and swconfig.
• include_file_revisions=false
Normally set to false, controls whether swpackage includes each source file’s revision attribute
in the product(s) being packaged. Because this operation is very time consuming, the revision
attributes are not included by default.
A value of true for this keyword causes swpackage to execute the what and possibly the
ident commands (in that order) to try to determine a file’s revision.
Applies only to swpackage.
• install_cleanup_cmd= /usr/lbin/sw/install_clean
The script called by the agent to perform release-specific install cleanup steps immediately
after the last postinstall script has been run. For an OS update, this script should at least remove
commands that were saved by the install_setup script.
Applies only to swagent.
• install_setup_cmd=/usr/lbin/sw/install_setup
Defines a script called by the agent to perform release-specific install preparation. For an OS
update, this script should copy commands needed for the checkinstall, preinstall, and postinstall
scripts to an accessible location while the OS updates the system commands.
This script is executed before any kernel filesets are loaded.
Applies only to swagent.
• installed_software_catalog=products
Defines the directory path where the Installed Products Database (IPD, information describing
the installed software) is stored. When set to an absolute path, this option defines the location
of the IPD. When this option contains a relative path, the controller appends the path to the
path specified by the admin_directory option to determine the path to the IPD. For alternate
roots, this path is resolved relative to the location of the alternate root. (This option does not
affect where software is installed, only the IPD location.)
This option permits the simultaneous installation and removal of multiple software applications
by multiple users or multiple processes, with each application or group of applications using
a different IPD.
Caution: use a specific installed_software_catalog to manage a specific application.
SD-UX does not support multiple descriptions of the same application in multiple IPDs.
See also the admin_directory option.
Applies to swacl, swask, swconfig, swinstall, swlist, swmodify, swremove, and
swverify.
• job_title=
When running large numbers of jobs, you may want to add more information to help you
identify a specific job. Providing a value for this lets you add an ASCII string that will be
displayed along with the ID and other job attributes when you invoke swjob or the job browser.
Applies to swconfig, swcopy, swinstall, swremove, and swverify.
Options Listed Alphabetically 237