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
Centralized
management
See remote operations.
Checkinstall script An optional, script associated with a product or fileset, executed by swinstall during the analysis
phase. The result returned by the script determines if the fileset can be installed or updated.
Checkremove
script
An optional script associated with a fileset that is executed during the swremove analysis phase.
The result returned by the script determines if the fileset can be removed.
checksum Cyclic Redundancy Check (CRC), a computed value that is compared with stored data to tell if
a file has been corrupted during transfer.
CLI Command Line Interface. See Command Line User Interface.
Client Usually refers to diskless server computer. Previous versions of SD-UX supported diskless clients.
CLUI See Command Line User Interface. All SD-UX commands can be run from the command line. See
also GUI, TUI, and IUI.
Codeword To protect software from unauthorized installation, HP (and other vendors) use special codewords
and customer identification numbers to lock the software to a particular owner. These codewords
and customer IDs are provided to you when you purchase the software or receive it as update.
Command line
options
Optional parameters for a command entered with the command itself at the HP-UX command line
prompt. See also default options.
Command Line
User Interface
(CLI/CLUI)
Text-formatted commands and options entered at an HP-UX command line prompt or executed
by a script. SD-UX also has a Graphical User Interface (GUI) and a Terminal User Interface (TUI)
for the sd, swinstall, swcopy, swlist, and swremove commands.
Committed The state in which a patch is applied and rollback files have been deleted. Other patch states
include applied and superseded and committed/superseded.
Committed/superseded
A patch state in which the patch is both committed and superseded.
Compatibility
Filtering
The ability of swinstall to filter the software available from a source according to the host’s uname
attributes. Software products are created to run on specific computer hardware and operating
systems. Many versions of the same products may exist, each of which runs on a different
combination of computer hardware and operating system. By default, swinstall does not allow
selection and installation of incompatible software.
Compatible
Software
A software product that will operate on a given hardware system. Software that passes
compatibility filtering for a local host. Also see Incompatible Software.
Configure Script An optional script associated with a fileset and automatically executed by swinstall (or manually
executed by swconfig) after the installation of filesets is complete.
Container ACL
Template
A special ACL (global_soc_template) that is used to create initial ACLs for depot and roots.
See also product ACL template.
Contents A keyword used to assign filesets to subproducts. This allows a fileset to be contained in multiple
subproducts.
Control Script Optional scripts packaged with software or added to software by modifying the IPD. Control
scripts are run during swconfig, swinstall, swremove, or swverify operations. Control scripts may
include: configure or unconfigure for swconfig; checkinstall, preinstall, postinstall and configure
scripts for swinstall; the checkremove, unconfigure, preremove, and postremove scripts for
swremove; and the fix or verify script for swverify.
Controller The SD-UX programs or commands (swinstall, swcopy, etc.) that are invoked by the user on the
local host and that direct the actions of an SD-UX agent.
Copyright A keyword that defines the copyright attribute for the destination depot (media) being
created/modified by swpackage. It refers to the copyright information for the software product.
Corequisite A dependency in which a fileset requires that another fileset be installed or configured at the
same time. For example, if fileset A requires that fileset B is installed at the same time, fileset B
is a corequisite.
Critical Fileset A fileset containing software critical to the correct operation of the host. Critical filesets are those
with the reboot and/or kernel fileset flags. During swinstall’s load phase, critical filesets are
loaded and customized before other filesets.
268 Glossary