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 depot’s product_template ACL is generated from the host’s
global_product_template ACL (that is, the host’s template ACL for new
products).
The user running swpackage is established as the owner of the new depot and
is granted permissions as defined in the depot ACL (which come from the
global_soc_template).
New product swpackage creates an ACL for the product; the ACL is generated from the
depot’s product_template ACL.
ACL creation can be disabled by setting the create_target_acls command
option to false.
When no ACL exists for a depot, only the superuser can create new products
or add/modify depot attributes. When no ACL exists for a product, only the
superuser can modify it.
Repackaging or Modifying a Software Package
There are two types of repackaging:
1. Adding to or modifying a fileset in an existing product.
• Editing the PSF by adding a new fileset definition or changing an existing fileset’s
definition.
• Running swpackage on the edited PSF, specifying the new/changed fileset on the
command line:
# swpackage -s psf <other options> \
product.fileset @ depot
This invocation works regardless of whether subproducts are defined in the product.
• If you change a fileset by changing its tag attribute, swpackage cannot correlate the
existing, obsolete fileset with the new fileset. Both become part of the changed product.
To get rid of the obsolete (renamed) fileset, use swremove:
# swremove -d product.old_fileset @ depot
2. Modifying an entire existing product.
• Editing the PSF by adding new fileset definitions, changing existing fileset definitions,
deleting existing fileset definitions or changing the product’s definition (product-level
attributes).
• Running swpackage on the PSF, specifying the product on the command line:
# swpackage -s psf <other options> product @ depot
• If you have deleted some fileset definitions in the PSF or modified a fileset by changing
it’s tag attribute, swpackage will produce warning messages about the existing filesets
that are not part of the modified product’s definition (in the PSF). The existing filesets plus
the new filesets in the product’s definition (in the PSF) will all be contained in the modified
product.
The warnings are produced during analysis phase, and are only produced when the
whole product is being repackaged (as opposed to subsets of the product).
• To get rid of the obsolete (renamed) filesets, use swremove:
# swremove -d product.old_fileset @ depot
• You may want to swremove the product entirely before repackaging the changes:
# swremove -d product @ depot
# swpackage -s psf <other options> product @ depot
Packaging Tasks and Examples 197