IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions: common procedures

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Remotely deploying the Warehouse Proxy Agent

This function allows you to remotely deploy the Warehouse Proxy Agent. You can use this function anytime the Warehouse Proxy Agent needs to be installed remotely.

For remote management of monitoring agents in general, install the appropriate OS monitoring agent. For instance, to remotely manage a Warehouse Proxy Agent on Linux systems, install the Monitoring Agent for Linux OS on the same server. To remotely manage a Warehouse Proxy Agent on Windows systems, install the Monitoring Agent for Windows on the same server.

Also, to remotely deploy the Warehouse Proxy Agent, you must populate the remote depot with the necessary bundles (the Warehouse Proxy Agent bundle and its prerequisites) for the operating systems where the Warehouse Proxy Agent needs to be deployed. This can be done using the product installer or the tacmd addBundles command.

During this process of adding bundles, IBM Tivoli Monitoring reads the descriptor file (dsc) of the specified bundle you are adding, and identifies (among all of the files in the installation media) which files need to be copied on the agent’s depot in your monitoring server. The files loaded are copied onto the path specified in the DEPOTHOME environment variable, defined in the KBBENV environment file. The tacmd viewDepot command allows you to display the types of agents in the deployment depot. The CD image contains a deploy directory where the Warehouse Proxy Agent bundle is located. When the depot is populated, you must deploy an OS agent on the remote computer, using the tacmd createNode command.

After the node has been created and OS agent is running, you can install other non-OS agents. This installation can be done using the Tivoli Enterprise Portal or using the tacmd createNode command.

Run the following command to complete enabling this function:

Properties supported:

Windows Only:

Unix/Linux only:

A Warehouse Proxy Agent should be installed and configured on the remote system once the transaction has completed successfully. The Warehouse Proxy Agent operates as usual when it is started. Connectivity of the Warehouse Proxy Agent can be checked on the Warehouse Proxy Agent Status workspace.

The configureSystem command allows CLI configuration of a remote agent. If KHD_PARMS.KHD_WAREHOUSE_TEMS_LIST is not provided, the value will be set to an empty value.

It is the OS Agent that is used by remote deploy to do the work. The OS Agent log on the endpoint shows all the remote deploy activity (kdy component) processing. If you enable ERROR(UNIT:KDY ALL) on the endpoint's OS Agent tracing, you will see the remote deploy processing. To redeploy the same agent, run the tacmd updateagent command using the –v option.

Remote deploy will start the agent after installation which might cause situations to fire due to lack of default configuration. The configuration supplied during the remote deploy is applied after the install and start is done. The agent will be restarted after the configuration is complete.


Parent topic:

Tivoli Data Warehouse solutions: common procedures

+

Search Tips   |   Advanced Search