|
|
United States-English | |
|
|
 |
|
Managing HP-UX Software With SD-UX: HP 9000 Computers > Chapter 1 Introduction to Software Distributor
Understanding SD-UX Terms and Concepts |
|
|
Throughout this guide, the term host is used to mean an individual computer, standing alone or connected to a network of other computers. The local host is the system on which you are invoking the SD-UX commands. Hosts may also be called nodes, servers, clients or systems. This book also refers to target, which is the destination host or directory (root or depot) on which the SD-UX operation is to be performed. For most SD-UX operations, the target is the local host or depots that are on it. A software source is a physical medium (CD-ROM or Tape) or directory location (depot) that contains software that is to be installed. The role of SD-UX controller is assumed by the local host on which you invoke the SD-UX commands. Controller programs are the front ends in the SD-UX process, providing the user interface for the management tasks. A controller's role is to collect and validate the data it needs to start a task, and to display information on the task's status. The SD-UX controller programs communicate with hosts and depots through the SD-UX agent called swagent. An agent is the part of SD-UX that actually performs the basic software management tasks. The SD-UX daemon that executes the agent is called swagentd. On HP-UX 11.0 systems, the SD-UX controller and agent both run on the local host. There are three roles an individual host may play in the SD-UX software management process - Local Host, Distribution Depot (or Server) and Development System. The role a host plays depends on which command is used. A local host is any system on which software is to be installed or managed using the SD-UX commands. It is sometimes referred to as the controller host. However, a local host that contains a depot could play a source as well as a destination or target role when other client systems obtain software from that depot via the network. A depot is a directory location on the local host which is used as a "gathering place" for software products. It is a customizable source of software used for direct installations by the local host or by other hosts on the network. A depot is created by copying software directly to it from the physical media (using the SD-UX swcopy command) or by creating a software package on it (using the swpackage command) and then "registering" the depot with swreg, see Chapter 10 “Creating Software Packages”. It can then be used as the source for installation tasks by the swinstall command which is executed on the target machine. There are two types of depots: Title not available (Distribution Depots )
A depot usually exists as a directory location (that is, a directory depot). Therefore, a host may contain several depots. For example, a designated software distribution server on your network might contain a depot of word processing software, a depot of CAD software, and a spreadsheet software depot, all on the same server. If a depot resides on a system that is connected to a network, then that system can be a network source for software. Other systems on the network can install software products from that server instead of installing them each time from a tape or CD-ROM. A network source offers these advantages over installing directly from tape or CD-ROM:
As a software application is developed, files are taken from the programmer's environment and placed on a developer host where they are "integrated" for distribution. The SD-UX swpackage command prepares these software files by organizing them into specific product, subproduct and fileset structures. It also uses special information files (see “Creating a Product Specification File (PSF)” in Chapter 10 “Creating Software Packages”) that are used to help other commands identify, distribute and manage the application. After it is organized, the software on a developer host is then "mastered" or copied onto CD-ROMs or tapes for further distribution to users or customers. The resulting package can also be made network-accessible to users. Most HP software products are shipped to you on CD-ROM 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 customer ID uniquely identifies the owner of the codeword. The codeword for a particular software product is found on the CD-ROM certificate you received from HP. It shows the codeword along with the customer ID for which this codeword is valid. One codeword usually unlocks all the products on a CD-ROM 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. The customer_id, also found on the Software Certificate, lets you restrict installation to a specific owner. SD-UX provides defaults in which you may specify your codeword and customer_id via the command line or the SD-UX Interactive User Interface. See Appendix A “Default Options and Keywords ” and “Using Software Codewords and Customer IDs ” in Chapter 2 “Installing and Copying Software ” for more information on codeword and customer_id defaults. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
