Software Distributor Administration Guide for HP-UX 11i

Installing Software
Installation with swinstall
Chapter 278
CAUTION Most HP-UX products have preinstall and postinstall scripts without
accompanying undo scripts. This negates any advantage of using the
autorecover_products option. Use autorecover_products only with
software that has the associated undo scripts.)
Installing Software That Requires a System Reboot
Software packaged with the is_reboot attribute set to true requires the
host to be rebooted after the software is installed. However, when
installing to alternate root file systems, the host will not be rebooted.
If a local installation entails a reboot, the system reboots the target and
the controller, so there is no process left to report success or failure.
(SD-UX does not automatically reconnect to the target after a reboot.)
To find out if a software product requires the local host to be rebooted,
get a description of the software either from the Software Selection
window, using the menu item
Show Description of Software, or from the
Analysis dialog using the
Product Summary and Product Description
buttons.
Using Software Codewords and Customer IDs
To protect software from unauthorized installation, HP (and other
vendors) use special codewords and customer identification numbers to
“lock” the software to a particular owner. These codewords and customer
IDs are provided to you when you purchase the software (or receive it as
update). HP lists them on the Software Certificate which is packaged
with the software.
To properly store the customer_id/codeword for a CD-ROM, you can run
swinstall (or swcopy or swlist) on the host serving the CD-ROM. After
the codeword has been stored, clients installing software using that host
and CD-ROM as a source will no longer require a codeword or
customer_id.
SD searches the .codewords file on the server that is providing
protected software to other hosts. It looks for valid customer_id/codeword
pairs. In doing so, SD eliminates the need for you to enter codewords and
customer_ids on every host that is “pulling” the software.
This is a time saver if you are updating multiple systems.