Software Distributor (SD-UX)

You can manage and distribute both operating system software and application software on a local system with Software Distributor (SD-UX). SD-UX consists of a set of commands and is part of the HP-UX operating system.

Some basics of SD-UX are presented here. For information about SD-UX, see Software Distributor Administration Guide.

With SD-UX, you can do the following tasks:

Install update software on local system. See “Adding Software”.
List software that is installed on a system or on various media. See “Listing Software”.
Remove software from a system. See “Removing Software”.
Build a network host (distribution depot). See “SD-UX Roles” and “Setting up a Network Host (Building a Depot)”
Copy software from a distribution source or media onto a system.
Verify compatibility of software products with your system.
Create software packages that make later software installations quicker and easier.
Configure installed software.

For a list of SD-UX commands, see Table 5-1: “SD-UX Command Summary”.

SD-UX Software Structure

SD-UX commands work on a hierarchy of software objects. Here are the terms used to describe the SD-UX objects.

Bundles

Collections of filesets, possibly from several different products, encapsulated by HP for a specific purpose. All HP-UX 11.x operating system software is packaged in bundles.

Example of a bundle is:

HPUXMinRuntime B.11.31 English HP-UX Minimum Runtime Environment

Products

Collections of subproducts (optional) and filesets. The SD-UX commands focus on products but still allow you to specify subproducts and filesets.

Example of a product is:

Networking HP-UX_LanLink_Product

Subproducts

Groups of logically related filesets within a product if the product contains several filesets.

Examples of subproducts are:

Networking.Runtime
Networking.MinimumRuntime

Filesets

Files and control scripts that make up a product. This is the smallest manageable (selectable) SD-UX software object. Filesets are only part of a single product but could be included in several different HP-UX bundles, and more than one subproduct.

The Runtime subproduct contains all the filesets in the MinimumRuntime subproduct as well as some additional filesets.

Examples of filesets are:

Networking.LAN-KRN
Networking.LAN-PRG
Networking.LAN-RUN

The Networking.LAN-KRN and Networking.LAN-RUN filesets are part of bundle HPUXMinRuntime.

The first three are included in both the subproducts,

Networking.Runtime and Networking.MinimumRuntime

The Networking.LAN-PRG fileset is also part of the HPUXMinRuntime bundle and is included in the Networking.Development subproduct.

SD-UX commands refer to this product structure in the form:

bundle[.] or product[.[subproduct.]fileset]

Location of Software

Software, packaged in SD-format, is stored in a depot. Any system can store one or more depots. A depot is a repository which holds all the needed pieces for installation of the software. You create a depot by copying software directly to it (using the SD-UXswcopy command) from either a tape or CD/DVD or by creating a software package within it (using the swpackage command). Before you can use the depot you must register it (using the swreg command). It can then be used as the source for installation tasks with the swinstall command which is executed on the target machine.

There are two types of depots:

Directory Depot

Software in a directory depot is stored under a normal directory on your file system (by default /var/spool/sw).

When using the SD-UX commands, refer to a directory depot via its top most directory. In a CD/DVD depot, the directory would be the media’s mount point.

Tape Depot

Software in a tape depot is formatted as a tar archive. Tape depots such as cartridge tapes, DAT and 9-track tape are referred to by the file system path to the tape drive’s device file.

A tape depot can only be created by usingswpackage and it cannot be verified or modified with SD-UX commands. You cannot copy software (using swcopy) directly to a tape; use swpackage for this operation.

Software in a tape depot may be installed directly on a local host, but must first be transferred to a directory depot before it can be “pulled” by other hosts on the network. A tape depot can be accessed by only one command at a time.




	NOTE: If you administer software for systems, you should create separate depots for each.

SD-UX Tasks

SD-UX commands can be executed from the command line. However, SD-UX provides a graphical and terminal user interface for the commonly used commands: swinstall, swcopy, swremove, and on 11.x, swlist -i.

The most common SD-UX tasks are:

swinstall. See “Adding Software”
swlist. See “Listing Software”
swremove. See “Removing Software”

The following table shows lists some of the other SD-UX functions.

Table 5-1 SD-UX Command Summary

Command	Purpose
swinstall	Install software
swremove	Remove software
swpackage	Package software into a depot
swcopy	Copy software from one depot to another
swlist	List software in a depot or installed on a system
swreg	Make a depot visible to other systems
swverify	Verify the integrity of installed software and depot software
swconfig	Configure and unconfigure installed software
swacl	Change access to SD-UX software objects
swagentd	Serve local or remote SD software management tasks, including invoking a swagent command
swask	Run interactive request scripts
swmodify	Modify software products
sd	Start the Job Browser GUI

For information about SD-UX, see Software Distributor Administration Guide.

Adding Software

Type /usr/sbin/swinstall.
If you have the DISPLAY variable set, swinstall will run using a graphical user interface; otherwise a terminal interface is presented.
Click onSource Host Nameand choose the system from which to install.
Click on Source Depot Path and choose a registered depot from which to install.

Select the bundle/product/fileset to be installed.

You may select:

bundles
products
filesets

To select an item, move the cursor to the bundle and press Return or Space. You can select one or more items and mark them for installation.

To see all subsets belonging to a bundle or product, chooseOpen. You can do this when only one item is selected.

To see a description of the item (if there is one), select the item and choose Show Description Of Software.

To update all parts of your operating system with new software found on the update media, select Match What Target Has.




	NOTE: By default, swinstall does not reinstall filesets if the same revision already exists on your system. If you want to reinstall the same revision (for example if some files are lost), you can change the installation options by choosing`Options/Change Option`.

Installing a product or a fileset may automatically install dependent filesets necessary to run the selected item(s).

Choose Action/Install (analysis) to start the installation process.
The installation process is divided into four phases:
Install Analysis
Checks dependencies, verifies that all files can be installed correctly and defines the sequence of installation so that, for example, only one kernel rebuild should be necessary even if there are more filesets which require a new kernel.
Execution Phase
Performs preinstall tasks if necessary and installs filesets.
Post_install
Performs post-installation activities, such as rebuilding of kernel and system reboot.
Configuration Phase
Configures installed filesets for your system. In some cases this must be done after the system is rebooted. This is done with the script /sbin/rc2.d/S120swconfig which is a link to /sbin/init.d/swconfig.
Information about the installation is logged in /var/adm/sw/swinstall.log and /var/adm/sw/swagent.log. You open the swagent.log log file during the installation process by pressing Logfile.... Check the log file for errors.

Installing Protected Software

Most HP software products are shipped to you on DVD optical media as “protected” products. That is, they cannot be installed or copied unless a “codeword” and “customer ID” are provided by you. Software that is unlocked by a codeword may only be used on computers for which you have a valid license to use that software. It is your responsibility to ensure that the codeword and software are used in this manner.

The codeword for a particular software product is found on the DVD certificate which you receive from HP. It shows the codeword along with the customer ID for which the codeword is valid. One codeword usually unlocks all the products on a DVD which you have purchased. When an additional HP software product is purchased, an additional codeword will be provided by HP. Just enter the new codeword and customer ID and they will be merged with any previously entered codewords.

A codeword for a particular customer ID and DVD only needs to be entered once per target system. The codeword and customer ID are stored for future reference in /var/adm/sw/.codewords. SD-UX will prompt you for these codewords or numbers prior to the installation of protected software. You can enter or change the numbers via the SD-UX graphical user interface (using Add New Codeword from the Actions menu) or by using the appropriate default (-x codeword=xxxx and -x customer_id=xxx) on the command line.

Here is a sample DVD certificate.

Figure 5-1 Sample DVD Certificate

Listing Software

With swlist you can do the following:

Specify the “level” (bundles, products, subproducts, filesets or files) to show in your list.
Show the product structure of software selections.
Show software attributes, such as size, revision, and vendor.
Display the depots on a specified system.

Some examples follow:

Table 5-2 Example Tasks and Commands

Example Task	Command
To list the software installed at root (/) on your local system	`swlist`
To list the software in the depot named `/mydepot`	`swlist -d @ /mydepot`
To list the depots on `appserver`	`swlist -l depot @ appserver`
To list all files that are part of the LVM product	`swlist -l file LVM`
To list files using the SD-UX graphical user interface on 11.x	`swlist -i`

You can use HP SMH to list software:

Access the HP SMH Homepage.
Select Tools, Software Management, and List Depot Software (or List Installed Software). This will display the List Depot Software page.
NOTE: If your client console is a PC, you must have an X Window Server running before executing these functions.
If needed, enter the address of the target display console. Click on the Run button. An X Window is displayed showing a list of software bundles available in the depot. If the default location for the software bundles is not correct or if you wish to list software bundles on a different system or directory, you can enter the new address.

See the swlist(1M) manpage for additional information.

Removing Software

To remove software, use /usr/sbin/swremove. You select the software to remove and the system checks dependencies between selected and remaining software. If a fileset is required by another bundle, that fileset is not removed. See the swremove(1M) manpage.

SD-UX Roles

Within your environment, an individual system can play one or more SD-UX roles: development host, local host, or network host (distribution depot). The SD-UX command determines the specific role a host plays and therefore its role can change at any time.

Software is created on the development environment and individual filesets are “packaged” for further distribution. The SD-UX swpackage command prepares software products and filesets so they can be easily distributed and managed by other SD-UX commands.

A local host is any system where software is to be installed or managed.

A network host contains one or more depots and is connected to a network. It can act as a common software installation source for other network clients. You copy software from a depot to the network host. From the network host, you can copy software to systems as needed.

Figure 5-2 SD-UX Roles