HP System Management Homepage Installation Guide, May 2005
Chapter8.Installing In-Place on
Linux Using Linux Deployment
Utility
This chapter provides steps to install System Management Homepage in-place on the Linux operating
system using the Linux Deployment Utility.
●
“Installing System Management Homepage with Pre-configuration” (page 41)
❍
“Pre-configuring the System Management Homepage Component” (page 41)
❍
“Installing the System Management Homepage as a Single Component” (page 43)
●
“Installing the System Management Homepage without Pre-configuration” (page 43)
The previous chapter provides steps to install System Management Homepage in-place on Linux
IA-32 systems and x86-64 systems.
●
“Installation for Linux on IA-32 and x86_64” (page 33)
❍
“Installing System Management Homepage on Linux IA_32 Systems” (page 33)
❍
“Installing System Management Homepage on x86_64” (page 34)
❍
“Configuring System Management Homepage” (page 34)
Installing System Management Homepage
with Pre-configuration
The Linux Deployment Utility provides an easy and efficient method to upgrade and manage system
software. The utility enables you to deploy and maintain ProLiant Support Pack software on local
servers through use of the terminal window and on remote servers through use of the ssh (secure
shell) utility. The Linux Deployment Utility is shipped with the Linux ProLiant Support Pack, which is
available on the SmartStart CD. The Linux Deployment Utility enables you to install components or
ProLiant Support Packs in-place, but not remotely.
The Linux Deployment Utility parses the .XML files associated with each component and verifies
whether the installation of those components is supported on the specific environment. The
components that are supported for installation are listed with a status icon indicating whether the
component should to be installed, and whether it should be configured. Configuring or
pre-configuring the System Management Homepage component is optional.
Pre-configuring the System Management Homepage
Component
Note: All pre-configuration settings are saved in the component XML file.
41