In this section, I use some
Software Distributor commands to view existing loaded software and use
the Character Line Interface (CLI) to swinstall to load additional software. The Mission Critical Operating Environment
and some additional software products were loaded on the system on
which the following examples are run. I check the operating system
revision with uname -a and software bundles that have been loaded on the system with swlist in the following listing:
# uname -a
HP-UX npar2 B.11.23 U ia64 0210646210 unlimited-user license
# swlist
# Initializing...
# Contacting target "npar2"...
#
# Target: npar2:/
#
#
# Bundle(s):
#
B5725AA C.6.0.57 HP-UX Installation Utilities (Ignite-UX)
B6848BA 1.4.gm.46.9 Ximian GNOME 1.4 GTK+ Libraries for HP-UX
B6849AA B.02.01.02 Bastille Security Hardening Tool
B8339BA B.03.00.09 servicecontrol manager Server and Agent Bundle
B8465BA A.02.00.04.%71Q HP WBEM Services for HP-UX
B9073BA B.11.23.06.03.%IC7IO HP-UX iCOD (Instant Capacity on Demand)
B9788AA 1.3.1.13.01 Java2 1.3 SDK for HP-UX
B9789AA 1.3.1.13.01 Java2 1.3 RTE for HP-UX
B9901AA A.03.05.10.%71P HP IPFilter 3.5alpha5
BUNDLE11i B.11.23.040713 CH PI IC Bundle for 11.23 040713
Base-VXVM B.03.50.IA.008 Base VERITAS Volume Manager Bundle 3.5 for HP-UX
CDE-English B.11.23 English CDE Environment
FDDI-00 B.11.23.01.%71Q PCI FDDI;Supptd HW=A3739B;SW=J3626AA
FibrChanl-00 B.11.23.03.%71Q PCI FibreChannel;Supptd HW=A6795A,A5158A
FibrChanl-01 B.11.23.02.%71Q PCI-X FibreChannel;Supptd HW=A6826A,
A9782A,A9784A
GigEther-00 B.11.23.05.%1Q PCI GigEther;Supptd HW=A4926A/A4929A/
A6096A;SW=J1642AA
GigEther-01 B.11.23.05.%1Q PCI GigEther;Supptd HW=A6825A/A6794A/
A6847A/A8685A/A9782A/A9784A/A7109A
HPUX11i-OE-MC B.11.23.0409.%1Q HP-UX Mission Critical Operating Environment
Component
HPUXBaseAux B.11.23.0409.%1Q HP-UX Base OS Auxiliary
HPUXBaseOS B.11.23 HP-UX Base OS
IEther-00 B.11.23.05.%1Q PCI IEther;Supptd HW=A6974A
ISEEPlatform A.03.90.001 ISEE Platform
Ignite-IA-11-22 C.6.0.57 HP-UX Installation Utilities for Installing 11.22
IPF Systems
Ignite-UX-11-11 C.6.0.57 HP-UX Installation Utilities for Installing 11.11
Systems
Judy B.11.11.04.15 Judy Library - development and runtime libraries
for handling dynamic arrays
MOZILLA 1.4.0.01.04 Mozilla 1.4 for HP-UX
MOZILLAsrc 1.4.0.01.04 Mozilla 1.4 Source distribution
MySQL 3.23.54a.01 MySQL open-source database
NPar B.11.23.01.03.00.05 nPartition Provider - HP-UX
OnlineDiag B.11.23.03.14.%ic71Q HPUX 11.23 Support Tools Bundle, Sep 2004
OpenSSL A.00.09.07-d.009%ic71Q Secure Network Communications Protocol
ParMgr B.11.23.02.00.03.03 Partition Manager - HP-UX
RAID-01 B.11.23.01.5.%ic71Q RAID SA; Supptd HW=A7143A/A9890A/A9891A
Sec00Tools B.01.02.00 Install-Time security infrastructure.
SecPatchCk B.02.01 HP-UX Security Patch Check Tool
T1456AA 1.4.2.03.04 Java2 1.4 SDK for HP-UX
T1456AAaddon 1.4.2.03.04 Java2 1.4 SDK -AA addon for HP-UX
T1457AA 1.4.2.03.04 Java2 1.4 RTE for HP-UX
T1457AAaddon 1.4.2.03.04 Java2 1.4 RTE -AA addon for HP-UX
T1471AA A.03.71.006.%ic71P HP-UX Secure Shell
USB-00 B.11.23.02.%ic71P Object Oriented USB Driver
WBEMP-LAN-00 B.11.23.00.%71P LAN Provider for Ethernet LAN interfaces
.
hpuxwsApache B.2.0.49.03.%71P HP-UX Apache-based Web Server
hpuxwsTomcat B.4.1.29.02.%71P HP-UX Tomcat-based Servlet Engine
hpuxwsWebmin A.1.070.01.%71P HP-UX Webmin-based Admin
hpuxwsXml A.2.00.%71P HP-UX XML Web Server Tools
perl D.5.8.0.C.%71P Perl Programming Language
scsiU320-00 B.11.23.1.%ic71Q PCI SCSI U320; Supptd HW=A7173A
This listing shows that
HP-UX 11i version 2 update 2 has been loaded, shown as 11.23 in the
listing, and that several software bundles that we selected have been
loaded as well, including the Mission Critical Operating Environment, which is shown as HPUX11I-OE-MC in roughly the middle of the swlist output.
Many products are loaded as part of the Mission Critical Operating Environment. The following swlist shows the components of which Mission Critical Operating Environment is comprised at the time of this writing:
# swlist -l product HPUX11i-OE-MC
# Initializing...
# Contacting target "npar2"...
#
# Target: npar2:/
#
# HPUX11i-OE-MC B.11.23.0409.%1Q HP-UX Mission Critical
Operating Environment Component
HPUX11i-OE-MC.OE B.11.23.0409.%1Q HP-UX OE control script
product
HPUX11i-OE-MC.Glance C.03.85.%ic71Q HP GlancePlus/UX
HPUX11i-OE-MC.MeasureWare C.03.85.%ic71Q MeasureWare Software/UX
HPUX11i-OE-MC.MeasurementInt C.03.85.%ic71Q HP-UX Measurement Interface
for 11.23
HPUX11i-OE-MC.LVM B.11.23 LVM
HPUX11i-OE-MC.SG-Tomcat-Tool B.02.11.%71O Serviceguard Tomcat Script
Templates
HPUX11i-OE-MC.SG-Samba-Tool B.02.11.%71O Serviceguard Samba Script
Templates
HPUX11i-OE-MC.SG-Apache-Tool B.02.11.%71O Serviceguard Apache Script
Templates
HPUX11i-OE-MC.SG-Oracle-Tool B.02.11.%71O Serviceguard Oracle Script
Templates
HPUX11i-OE-MC.WLM-Toolkits A.01.07.%q06 HP-UX Workload Manager Toolkits
HPUX11i-OE-MC.OPS-Provider-MOF B.03.00.01.%71Q OPS Provider and MOF
HPUX11i-OE-MC.CM-Provider-MOF B.03.00.01.%71Q CM Provider and MOF
HPUX11i-OE-MC.Cluster-OM B.03.00.01.%71Q HP Cluster API
HPUX11i-OE-MC.Jpi13 1.3.1.13.01 Java2 1.3 Netscape Plugin
HPUX11i-OE-MC.Package-Manager A.11.16.00 HP Package-Manager
HPUX11i-OE-MC.Cluster-Monitor A.11.16.00 HP Cluster Monitor
HPUX11i-OE-MC.ServiceGuard A.11.16.00 ServiceGuard
HPUX11i-OE-MC.PRM-Sw-Lib C.02.03.%11 Process Resource Manager
PRM-Sw-Lib product
HPUX11i-OE-MC.Proc-Resrc-Mgr C.02.03.%11 Process Resource Manager
Proc-Resrc-Mgr product
HPUX11i-OE-MC.WLM-Monitor A.02.03.%q17 HP-UX Workload Manager Utilities
HPUX11i-OE-MC.Workload-Mgr A.02.03.%q17 HP-UX Workload Manager
HPUX11i-OE-MC.PAM-Kerberos C.01.23.%71N PAM-Kerberos Version 1.23
HPUX11i-OE-MC.Jpi14 1.4.2.03.04 Java2 1.4 Netscape Plugin
HPUX11i-OE-MC.CIFS-Server A.01.11.01.%71N HP CIFS Server (Samba) File and
Print Services
HPUX11i-OE-MC.CIFS-Development A.01.11.01.%71N HP CIFS Ser Source Code Files
HPUX11i-OE-MC.EMS-DBMon A.04.10.%ic71p EMS Database Monitor
HPUX11i-OE-MC.EMS-DskMon A.04.10.%ic71p EMS Disk Resource Monitor
HPUX11i-OE-MC.EMS-MIBMon A.04.10.%ic71p EMS MIB Resource Monitor Product
HPUX11i-OE-MC.SG-NFS-Tool A.11.23.02 MC/ServiceGuard NFS Script
Templates
HPUX11i-OE-MC.PAM-NTLM A.01.09.02.%71l HP NTLM Pluggable
Authentication Module
HPUX11i-OE-MC.CIFS-Client A.01.09.02.%71l CIFS Client
HPUX11i-OE-MC.PRM-Sw-Krn C.01.02 Process Resource Manager
PRM-Sw-Krn product
HPUX11i-OE-MC.OnlineJFS B.11.23.05.%1Q Online features of the VxFS
File System
#
The initial swlist output is deceiving in that the Mission Critical Operating Environment is shown as only one entry. You can see from the display of the product level details of Mission Critical Operating Environment
in the last listing that many products are included in this OE,
including ServiceGuard, Process Resource Manager, GlancePlus/UX,
CIFS/9000, and many other products.
Now that we know the
initial software that has been loaded, let's move on to load additional
products. Software Distributor-HP-UX is the
program used in HP-UX 11i to perform all tasks related to software
management. Software Distributor is a standards-based way
to perform software management. It conforms to the Portable Operating
System Interface (POSIX), which is the standard for packaging software
and utilities related to software management. The Software Distributor
product described in this section comes with your HP-UX system.
The following four phases of software installation are performed with Software Distributor:
Selection(1)
-
You can select the source and software you wish to load during
this phase. In the upcoming example, the Graphical User Interface of
Software Distributor is used, and you see how easily you can select
these.
Analysis(2)
-
All kinds of checks are performed for you, including free disk
space, dependencies, compatibility, mounted volumes, and others. One of
the useful outputs of this phase is the amount of space the software you
wish to load consumes on each logical volume. This will be shown in the
example.
Load(3) -
After you are satisfied with the analysis, you can proceed with loading the software.
Configuration(4)
-
The software you load may require kernel rebuilding and a system
reboot. Startup and shutdown scripts may also need to be modified.
I tend to use
some terminology associated with Software Distributor somewhat loosely. I
have nothing but good things to say about Software Distributor, but I
don't conform to the official Software Distributor terminology as much
as I should. For instance, I use the word "system" a lot, which could mean many different things in the Software Distributor world. For instance, Software Distributor uses "local host" (a system on which Software Distributor is running or software is to be installed or managed by Software Distributor), "distribution depot" (a directory that is used as a place for software products), and "development system" (a place where software is prepared for distribution). I will use the word system to mean the system on which we are working in the examples, because software is loaded onto the system from media.
The example of
Software Distributor in this section describes the process of loading
software from a DVD-ROM to the local system. What I show here only
begins to scratch the surface of functionality you have with Software
Distributor, but because I want to get you up and running quickly, this
overview should help. You can load software from various media as well
as across the network. You can run swinstall
through the graphical interface, the Character Line Interface (CLI)
used throughout this section, or the command line. You can use the swinstall
command from the command line specifying source, options, target, and
so on. I like using the CLI because you don't need any graphics
capability, and you get full functionality. If, however, you like to do
things the "traditional UNIX" way, you can issue the swinstall command with arguments. You can look at the manual page for swinstall
to understand its arguments and options and use this command from the
command line. There are many Software Distributor commands, including sd, swjob -i, swcopy, swremove, swlist, and swinstall.
To load software from a DVD-ROM, you must first mount the DVD-ROM. This can be done at the command line or in SAM. Figure 1 shows the SAM log file after the DVD-ROM was mounted and the directory dvdrom was searched for in the SAM log file.
Figure 3-8 shows the mount
command of the DVD-ROM that could have been issued at the command line.
If you're not sure of the device file of the DVD-ROM, you would issue ioscan -funC disk and all the disk devices including the DVD-ROM would be listed.
After the DVD-ROM has been mounted, run swinstall and select the source, as shown in Figure 2.
After the source is
specified, you can select from the software on DVD-ROM to load. At the
time of this writing, you have both an HP-UX 11i version 2 update 2 core
operating system and applications DVD-ROM. Figure 3 shows a small subset of the software on DVD-ROM.
From this screen, you can
view and select software to load from a DVD-ROM. The process of
selecting software to load is covered next for loading from an Ignite-UX
server, but the process is the same for a DVD-ROM.
This process is not much
different than the process of loading software from an Ignite-UX server,
as described next, other than the source being DVD-ROM, in this case,
rather than the Ignite-UX server.
An alternative to loading software from a DVD is to access an Ignite-UX server, and load software from one or more of the software depots on the Ignite-UX server. Figure 4 shows accessing software on an Ignite-UX server.
This figure shows the swinstall
screen contents you would enter after HP-UX is running to load
additional software. Ignite-UX server IP address is specified and so is
the full path of the depot /var/opt/ignite/depots/Rel_B.11.23/core
(which can't be fully seen in the figure). I also have an applications
depot that I could have selected as the source of this load. The next
screen you see after this are the contents of the Core OS components, as
shown in Figure 5:
Figure 3-12 shows the contents of /var/opt/ignite/depots/Rel_B.11.23/core. From this depot, you can load any of its components.
Among the advantages of
booting and installing software from an Ignite-UX server are media is
not required when software is loaded on the clients, and multiple
clients can boot from a single Ignite-UX server simultaneously. I
install many systems, so this is a big advantage for me.
When you select Match What Target Has under the Actions
menu, you can view the software currently loaded on your system. You
may receive a "Yes" in the "Marked?" column or a "Partial." "Yes" means
that all the filesets associated with your selection will be loaded, and
"Partial" means only some will be loaded. Figure 6 shows "Yes" in the "Marked?" column for software that has been selected.
A bundle of software you
select to install may be composed of products, subproducts, and
filesets. You can select any item you have "Marked" for loading to see
of what filesets it is comprised. I have done this for Pay Per Use to
see the software of which it is comprised in Figure 7.
Figure 7 shows that the Pay Per Use software is indeed composed of many components. To go back to the top, select (go up).
Selecting Install
runs analysis (Step 2 - Analysis) on the software you select to load.
After the analysis is completed, you can take a look at the logfile,
view the disk space analysis, and perform other tasks. I normally take a
look at the disk space analysis just to see the impact the software I
am loading is having on free disk space, as shown in Figure 8.
You can see in Figure 8 that Pay Per Use consumes minimal disk space.
I also look at the products to ensure that I'm loading the software I expect to load, as shown in Figure 9 for Pay Per Use.
After you are satisfied with the analysis, you can proceed with the installation (Step 3 - Load). Figure 10 shows the type of status you are provided as software is loaded on the system.
In this case, all the software has been loaded. I could view the logfile to check for errors or warnings.
After the load of your
software is complete, you can either exit the session or you are given a
message indicating that a reboot is required to complete the
configuration (Step 4 - Configuration). Not all software requires a
reboot in order for configuration to take place. Most software will run
configuration routines after the software is loaded without the need for
a reboot. If a reboot is required, you are asked if you wish to reboot;
but it could be a bad time to reboot, so you may want to wait or delay
the reboot.
The
process of loading software from media using Software Distributor is
easy and thorough. The user interface to Software Distributor makes it
easy to select and load software from media.
