When you use the remote deployment for agents and patches,
place the remote deployment depot on a separate directory from your Tivoli® Monitoring installation
directory. This allows for cleaner backup and restore operations.
Note: Remote deployment is possible only for monitoring agents that
run on distributed platforms (Windows, UNIX, and Linux computers).
The remote deployment depot requires significant disk space, which
varies depending on the number of agents and the number of platforms
you use. Typically, allocate at least 2 GB of disk space for the depot.
Note: If
you create a shared deployment repository named
depot on
the server hosting the deployment depot and you create this repository
in a subdirectory of the
depot directory, the monitoring
server will not be able to find your deployment depot. Instead:
- Create the repository at the C:\IBM\ITM\CMS level of
the directory structure, not at the C:\IBM\ITM\CMS\depot level.
- Then set the DEPOTHOME keyword to DEPOTHOME=\\hubtems\centralrepository\depot in
the KBBENV file.
Otherwise you will get this error message:
KDY2077E: The specified agent bundle depot \\hubtems\depot is not a directory.
Either the agent bundle depot directory does not exist or it is not a directory.
The agent bundle depot directory does not exist because no bundles have been added.
One of the most important aspects of using remote deployment is
ensuring that the files that are distributed are at the correct version.
In large environments, there might be several remote monitoring servers
that require maintenance to ensure that all of the depots are updated.
To avoid the necessity of installing updates and maintenance on multiple
computers, consider creating one depot and making it available using
NFS or Windows shares.
If you decide to use a shared depot, make sure that the remote
monitoring server is upgraded before you upgrade the agents that are
connected to that remote monitoring server. When you deploy monitoring
agents, make sure that you configure them to connect to the desired
remote monitoring server.
If you are using a Windows monitoring
server connecting to a depot on another Windows computer, you must set the service
ID for the Windows monitoring
server to "Administrator." Also, instead of specifying a mapped drive
letter for the path to the depot directory, use the UNC path (such
as \\server\share). Use the following steps to change the service
ID:
- From the Control Panel, double-click Administrative
Tools.
- Double-click Services.
- Right-click Tivoli Enterprise Monitoring Svcs and
click Properties.
- On the Log On tab, select This
Account.
- Type Administrator in the This Account field.
- Type the password for the administrator in the Password field.
Confirm the password by typing it again in the Confirm
password field.
- Click Enable.
If the Administrator user
does not have Logon as a service right, you are prompted to add it.
Note: - In addition to remotely deploying monitoring agents, IBM® Tivoli Monitoring
lets you remotely deploy non-agent bundles (with which your
site can employ Tivoli Monitoring
components that need not connect to a Tivoli Enterprise
Monitoring Server).
- Remote deployment is not available for z/OS-based OMEGAMON® agents, nor is it supported on
nodes running the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise
Portal Server, or the Tivoli Enterprise
Portal desktop or browser client.