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
Applies to swcopy and swinstall.
• return_warning_exitcode=false
This option controls the exit code returned by SD's controller commands. It is applicable only
for a single target operation and is ignored when multiple targets are used. When set to the
default value of false, swinstall returns:
◦ 0 If there were no errors, with or without warnings.
◦ 1 If there were errors.
When set to true, swinstall returns:
◦ 0 If there were no warnings, and no errors.
◦ 1 If there were errors.
◦ 2 If there were warnings but no errors.
• reuse_short_job_numbers=true
When assigning job ID numbers, SD-UX uses numbers less than 10,000. Typically, old jobs
are removed long before job number 9,999 is reached, so the job number quickly rolls over
from 9999 back to 1. When you execute a large numbers of jobs that are not removed before
the ID numbers reach 9,999, SD-UX may have performance delays while it searches for unused
job numbers.
Setting reuse_short_job_numbers to false causes SD-UX to begin using numbers above
10,000. This avoids possible searching delays and lets the job ID numbers increase to 8 digits
(99,999,999) if necessary. (This prevents roll-over from 9999 back to 1, so is usually not
desirable.)
See also the autoremove_job option.
Applies to swconfig, swcopy, swinstall, swremove, and swverify.
• rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
Determines on what protocol sequence(s) and endpoint(s) the swagentd daemon listens. If the
connection fails for one protocol sequence, the next is attempted. SD-UX supports both the tcp
and udp protocols on most platforms.
The value can have the following form:
◦ A DCE string binding containing a protocol sequence and an endpoint (a port number).
The syntax is:
protocol_sequence: [ endpoint ]
◦ The name of a DCE protocol sequence with no endpoint specified. This syntax is:
ncadg_ip_udp or ncacn_ip_tcp
Since no endpoint is specified, the DCE endpoint mapper rpcd must be running and is
used to find the endpoint registered by swagentd
◦ The literal string all. This entry means to use all protocol sequences supported by the
DCE Remote Procedure Call (RPC) runtime. It should be the only entry in the list. The rpcd
must be running.
Applies to all commands except swask, swmodify, and swpackage.
• rpc_binding_info_alt_source=ncadg_ip_udp:[2121]
Defines the protocol sequence(s) and endpoint(s) used when the agent attempts to contact an
alternate source depot specified by the alternate_source option. SD-UX supports both
the udp(ncadg_ip_udp:[2121]) and tcp(ncacn_ip_tcp:[2121])protocol
sequence/endpoint.
Applies to swagent.
Options Listed Alphabetically 247