In some situations, you may want to install an HTTPS agent on a
system manually, without using the management
server. HTTPS agent installation packages are available, which
you can copy or transfer to a system. You can then start the agent
installation locally. You must use the correct installation package
for the node's
architecture and operating system. The command
ovpmutil
enables you to download the correct
installation package. You can also find installation packages in
the following folder on the management server:
%OvShareDir%Packages\HTTPS
\
Subfolders below this contain different packages for each
supported agent platform. (For up-to-date information on supported
agent platforms, see the support matrix at HP Software Support Online.) The
subfolders below %OvShareDir%Packages\HTTPS
\ conform
to the following structure:
<os type>\<os vendor>\<os
versions>\<agent binary
format>\Operations-agent\<agent
version>\<os bit length>\https
%OvShareDir%
on the management server is
\Documents and Settings\All Users\Application Data\HP\HP BTO
Software\shared\
. An alternative path may have been
configured during installation.The HTTPS agent packages contain subpackages for all supported locales. This means, for example, that you can download an agent package from a management server that runs in the English locale, and then install it on a node that runs in the Japanese locale.
If the node does not exist in the console, or does not have any custom configuration, you can manually install an agent using the default configuration. Otherwise, if you have already created the node in the console and configured it, you can copy its profile to the system to use during the installation process. You can also preinstall HTTPS agents, and then configure and start them at a later time.
Every node that you manage with an HTTPS agent requires a certificate. If you are manually installing HTTPS agents, you should also plan certificate deployment before you begin.
Related Topics: