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
Request script An interactive control script that gets a response from the user. A request script prompts the user
for a response, reads the user’s answer, and stores the results in a response file. Request scripts
can be run by the swask, swconfig, and swinstall commands.
Response file A file that is generated by an interactive request script and contains the user’s response.
Revision This keyword defines the “revision” attribute for the product object. The revision information
(release number, version) for the product.
Root The root directory of a system (/). See Root Directory.
Root Directory The directory on a target host in which all the files of the selected products will be installed. The
default (/), can be changed to install into a directory that will eventually act as the root to another
system. See Alternate Root Directory.
RPC Remote Procedure Call. DCE technology for distributed communications and data transfer.
sd The command that invokes the Job Browser, a GUI program that lets you create, monitor, schedule,
and delete jobs. The swjob command lets you monitor jobs from the command line. You can also
activate the Job Browser with the swjob -i command.
SD format See SD-UX format.
SD-UX format The format and syntax of SD-UX software in depots.
Secret In SD-UX security, a password used to verify the authenticity of the caller’s host. SD-UX manages
sets of hosts by restricting and changing the default secret on all controller and target hosts in
the network. See shared secrets file.
Security Controlling access to software objects. In SD-UX, security is achieved by a combination of Access
Control Lists (ACLs) associated with objects and commands, and the security inherent in the file
system permissions on which the software is stored. See Access Control List.
Selection, Selection
Phase
The first phase of a software installation, copy, remove, or verify operation, during which the
user selects the software products to be installed, copied, or removed from the host.
Server A system on the network that acts as a software source for other systems on the network.
Session/Session
File
Each invocation of a SD-UX command defines a session. Most SD commands let you use the -C
session_file option to save command options, source information, software selections, and
host selections and reuse this information with the -S session_file option. You can also save
and reuse session information from the GUI programs.
Shared Secrets File In SD-UX security, a file containing the passwords used to encrypt and decrypt distributed
communications for added security.
Single Point
Administration
(SPA)
The ability to simultaneously distribute to, manage, or monitor multiple remote targets from a
single controller system. See remote operations.
Software depot An SD-UX format structure that contains one or more software products that can be installed on
other systems or copied to other depots.
Software file An input file of previously defined software selections to be used as operands for a command.
You specify a software file with the -f software_file command line option.
Software group A group of software selections read or saved from the GUI programs.
Software object The objects packaged, distributed, installed, or managed by SD-UX. A software object may be
a file, fileset, bundle, or product. Most operations are performed on filesets.
Software selection A group of software objects you have selected for an operation. You can save these software
selections for later reuse. See software group.
Software Selection
Window
A GUI window that lets you select the software files you want to install, copy, or remove.
Software source A depot used as the source of a swinstall or swcopy operation.
Source See software source.
SPA See Single Point Administration.
Staged installation See staging.
Staging A way of setting up intermediate depots that are local to each group of targets on local area
networks. This can reduce the amount of network traffic.
273