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

Registration provides a type of public recognition for the packaged depot:
• You can see the depot in the swinstall/swcopy GUI and see it in swlist depot-level
listings.
• You can read products from the depot (for example, to install).
For more information about registering depots, see “Registering and Unregistering Depots (swreg)
” (page 93).
NOTE: If the only use of a depot created with swpackage is local access by the packaging
user, depot registration is not required.
Creating and Mastering a CD-ROM Depot
When swpackage creates a new depot or packages a new product, it always creates an ACL
for the depot/product. If you were to create a depot and then master it onto a CD-ROM, the
CD-ROM would contain all those ACLs, which could cause the following problems:
• it may result in too-restrictive permissions on the CD-ROM depot.
• you could have too many user-specific ACLs on the CD-ROM.
To solve these problems, you can tell swpackage to not create ACLs in the depot by setting the
create_target_acls option to false.
This feature is provided only for the superuser because only the local superuser can change, delete,
or add ACLs to a depot that has no ACLs. The local superuser always has all permissions.
Setting the create_target_acls to false causes swpackage to skip the creation of ACLs for
each new product being packaged (and for the depot, if it is new). This option has no impact on
the ACLs that already exist in the depot.
When a depot is used as a source for other SD-UX operations, its ACLs (or lack of ACLs) have no
bearing on the ACLs created for the targets of the operation. Source ACLs are not related to target
ACLs.
The swpackage command never creates ACLs when software is packaged onto a tape.
Compressing Files to Increase Performance
The packaging process may pass large amounts of data back and forth over the network and
might slow down network performance. The compress_files option can improve performance
by first compressing files that are to be transferred. This performance gained depends on the type
of files transferred. Binary files compress less than 50%, text files generally compress more.
Improvements are best when transfers are across a slow network (approximately 50Kbytes/second
or less).
If set to true, compress_files compresses files (if they have not been compressed previously
by SD-UX) before transfer from a source. You may also specify a compression type with the
compression_type option or specify a compression command with the compression_command
option.
This option should be set to true only when network bandwidth is clearly restricting total throughput.
If it is not clear that this option will help, compare packaging operations both with and without
compression before consistently using this option. See Appendix A (page 227) for more information
on using command options.
NOTE: swpackage cannot compress files when writing to a tape.
Packaging Security
SD-UX provides Access Control Lists (ACLs) to authorize who has permission to perform specific
operations on depots. Because the swpackage command creates and modifies local depots only,
Packaging Tasks and Examples 195