Deploying non-OS agents

You can deploy non-OS agents through the Tivoli® Enterprise Portal or from the command line.

The deployment and configuration of agents varies depending on the specific agent. The following procedures provide generic deployment information. For the exact values required for your agent, see the configuration information in Installing Response Time monitoring agents and related software.
Ensure that you have populated your agent depot, as described in Populating the agent depot, before attempting to deploy any agents.
You must have already installed an OS agent on the computer where you are now deploying the non-OS agent and the agent must be running.

Deploying agents using the Tivoli Enterprise Portal

Before you deploy an agent using the Tivoli Enterprise Portal, application support for that agent must be installed on the portal server (see Install application support for Linux and UNIX or Install application support for Windows systems).

Use the following steps to deploy an agent through the Tivoli Enterprise Portal:

Open the Tivoli Enterprise Portal.
In the Navigation tree, navigate to the computer to which you want to deploy the agent.
Right-click the computer and click Add Managed System.
In the Select a Monitoring Agent window, select the agent that you want to deploy and click OK.
In the New Managed System Configuration window, complete the configuration fields required for the agent. For information about these fields, see the configuration documentation for the agent that you are deploying.
Click Finish.
If the computer where you are deploying the agent already has a version of that agent installed, you can stop the deployment, add a new instance of the agent, if possible, or reconfigure the existing agent.

A message will tell you when the deployment finishes successfully.

Deploying agents through the command line

To deploy non-OS agents from the command line, use the tacmd addSystem command. See the IBM Tivoli Monitoring Command Reference for the full syntax of this command, including parameter descriptions. You can run the cinfo command on UNIX systems, or the kincinfo -i command on Windows systems to list the product codes for agents installed on the current computer.

For example, the following command deploys the Application Management Console using the CLI syntax tacmd addSystem {-t|--type} pc {-n|--node} MANAGED-OS {-p|--property},

where

-t|--type
: Specifies the type of agent to add to the monitoring system.

-n|--node: Identifies the node or the directory on the monitoring system where the OS agent is installed, to which you want to add the agent. The name of a node includes the computer where the OS agent is installed and the product code for the OS agent. For example, stone.ibm.com:LZ is the name of the node on computer stone.ibm.com, which has a Linux OS agent installed.

-p|--property: Specifies SECTION.NAME=VALUE pairs that identify agent configuration properties and their values, where SECTION specifies the name of the section containing the key-value pair. KEY specifies the name of the configuration property, and VALUE specifies the property value. Refer to the agent configuration chapters for the agent that you want to deploy in Installing Response Time monitoring agents and related software to obtain theKEY/VALUE pairs. See IBM Tivoli Monitoring: Installation and Setup Guide for complete details on using the property SECTION.NAME=VALUE pairs.

Each agent bundle has its own unique configuration parameters that you need to provide in this command. If you have an installed agent of the same type that you want to deploy, you can view the configuration parameters by running the following command from a monitoring server:

 tacmd describeSystemType -t pc -p platform

An agent of the same type and platform must be deployed into the depot available to the monitoring server from which the command is run. For more information about agent-specific parameters, see the configuration chapters for the agent that you want to deploy in Installing Response Time monitoring agents and related software.

Note: If you deploy a Web Response Time agent to a Windows system remotely, ensure that you restart the target system after you have deployed the agent.