HP -UX B6941-90001, Справочное руководство администратора

Страница: 90 / 548

90 Chapter 2
Installing ITO Agents on the Managed Nodes
General Installation Tips for Managed Nodes
❏
Note that PATH cannot be changed during runtime on OS/2 managed
nodes. All actions, montiors, and commands must be either fully
qualified or must reside in PATH. PATH must be set before the ITO
agents are started.
Manual OS/2 Agent Installation
In some situations, it may be desirable to install the OS/2 agent software
without using the management server. A manual installation prepares
the system so that it is ready to become an ITO managed node when it is
later connected to the network. This may be useful if many systems are
prepared in a central location, or if you want to avoid the root connection
over the network that is necessary for a standard agent installation.
Note that RPCD/DCED must be running if the ITO agent software is
installed manually, so that the management server may be informed
about a successful installation. If it is not running, a warning is
displayed along with instructions concerning how to inform the
management server manually.
1. Copy the following files from the management server to a temporary
directory on the OS/2 managed node:
• installation script
opcinst.cmd
/var/opt/OV/share/databases/OpC/mgd_node/vendor/\
ibm/intel/os2/A.05.00/RPC_DCE_TCP/install/\
opcinst.cmd
• package
opc_pkg.z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/\
ibm/intel/os2/A.05.00/RPC_DCE_TCP/opc_pkg.z
opc_pkg.z
can be unpacked by running the OS/2 utility
unpack
.
2. Add the managed node to the
ITO Node Bank
.
Note: if you do not do this step now, the installation script will issue a
warning, and tell you how to notify the management server of the
new managed node using the command
itonotfy.exe
.
3. Run the installation script
opcinst.cmd
in one of the following ways
on the managed node:
• using the command line options: