IBM Performance Management

Agent deployment

Agents vary in the tasks that are required between installation and viewing the data that they collect. Some tasks are automatic and other tasks are manual.

After installation, some agents are configured and started automatically.
For any agent that is started, the agent is configured with the default settings.
To determine which agents are configured and started manually, see Table 1.
After installation, some agents require manual configuration but start automatically.
For information about how to configure your agents, see Configuring your environment.
To determine which agents are configured manually and started automatically, see Table 1.
After installation, some agents must be configured and started manually.
For any agent that is not started automatically, you must configure the agent before it can be started.
To determine which agents are configured and started manually, see Table 1.
Multiple instance agents require creating a first instance and starting manually.
You must create the first instance and start the agent manually. A multiple instance agent means that a single installation of the agent instantiates a unique monitoring instance for each unique application instance. These instances are visualized from the Performance Management console as a result.

To determine which agents are multiple instance agents, see Table 1.

Table 1. Agent postinstallation checklist
Agent Configured and started automatically Configured manually and started automatically Configured and started manually Multiple instance (started manually)
Monitoring Agent for Cisco UCS No No No Yes
Monitoring Agent for Citrix Virtual Desktop Infrastructure No No No Yes
Monitoring Agent for DataPower® No No No Yes
Monitoring Agent for DB2® No No No Yes
Monitoring Agent for Hadoop No No Yes No
Monitoring Agent for HMC Base No No No Yes
Monitoring Agent for HTTP Server
Yes
You must review the configuration file that the agent creates for the HTTP Server. Then, you must add the data collector configuration manually to the server configuration file.		 No No No
Monitoring Agent for IBM® Integration Bus No No No Yes
Monitoring Agent for JBoss No No No Yes
Monitoring Agent for Linux KVM No No No Yes
Monitoring Agent for Linux OS Yes No No No
Monitoring Agent for Microsoft Active Directory No
Yes
This agent is started automatically. However, you must configure the agent to view data for some attributes.		 No No
Monitoring Agent for Microsoft Cluster Server No No Yes No
Monitoring Agent for Microsoft Exchange Server No
Yes
This agent is started automatically. However, you must configure the agent to view data for all attributes.		 No No
Monitoring Agent for Microsoft Hyper-V Server Yes No No No
Monitoring Agent for Microsoft Internet Information Services Yes No No No
Monitoring Agent for Microsoft Lync Server Yes No No No
Monitoring Agent for Microsoft .NET No
Yes
The data collector must be configured before data is reported.		 No No
Monitoring Agent for Microsoft SharePoint Server Yes No No No
Monitoring Agent for Microsoft SQL Server No No No
Yes
Each agent instance must be configured and started manually.
Monitoring Agent for MongoDB No No No Yes
Monitoring Agent for MySQL No No No Yes
Monitoring Agent for Node.js No
Yes
The agent must be configured before data is reported. You must add a monitoring plug-in to your Node.js application.		 No No
Monitoring Agent for Oracle Database No No No Yes
Monitoring Agent for WebLogic No No No Yes
Monitoring Agent for PHP No No No Yes
Monitoring Agent for PostgreSQL No No No Yes
Monitoring Agent for Python No No No Yes
Monitoring Agent for Ruby No No No
Yes
For deep-dive diagnostics, the agent must be configured before data is reported. To enable the diagnostics dashboards, you must install and configure the diagnostics data collector.
Monitoring Agent for SAP Applications No No No Yes
Monitoring Agent for SAP HANA Database No No No Yes
Monitoring Agent for Synthetic Playback
No
Yes

The agent is started automatically but the agent must be configured for private, internal-facing applications. Transactions must be created in the Synthetic Script Manager before data is reported.

 No Yes
Monitoring Agent for Tomcat No No No Yes
Monitoring Agent for UNIX OS Yes No No No
Monitoring Agent for VMware VI No No No Yes
Monitoring Agent for WebSphere® Applications No
Yes
The agent is started automatically but the data collector must be configured before data is reported.		 No No
Monitoring Agent for WebSphere Infrastructure Manager No No No Yes
Monitoring Agent for WebSphere MQ No No No Yes
Monitoring Agent for Windows OS Yes No No No
Response Time Monitoring Agent Yes No No No