Agent and data collector 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 you download your data collectors, you must manually configure each data collector.
- 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 Cloud APM console as a result. To determine which agents are multiple instance agents, see Table 1.
- OS agents and log file monitoring
- The Linux OS agent, UNIX OS agent, and Windows OS agent are configured and started automatically. However, you can configure log file monitoring for the OS agents, so that you can monitor application log files. For more information, see Configuring OS agent log file monitoring.
- Agent and data collector configuration, startup, and instance characteristics
-
Table 1. Postinstallation checklist Agent or data collector Configured and started automatically Configured manually and started automatically Configured and started manually Multiple instance (started manually) Amazon EC2 agent 



Amazon ELB agent 



Azure Compute agent 



Cassandra agent 



Cisco UCS agent 



Citrix VDI agent 



DataPower® agent 



DataStage® agent 



Db2® agent 



Hadoop agent 



HMC Base agent 



HTTP Server agent 
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.



IBM® Cloud agent 



IBM Integration Bus agent 



J2SE data collector 



JBoss agent 



Liberty data collector 



Linux KVM agent 



Linux OS agent 



Microsoft Active Directory agent 

This agent is started automatically. However, you must configure the agent to view data for some attributes.


Microsoft Cluster Server agent 



Microsoft Exchange Server agent 

This agent is started automatically. However, you must configure the agent to view data for all attributes.


Microsoft Hyper-V Server agent 



Microsoft IIS agent 



Skype for Business Server agent (formerly known as Microsoft Lync Server agent) 

This agent is started automatically. However, you must configure the agent to view data for some attributes.


Microsoft Office 365 agent 



Microsoft .NET agent 

The data collector must be configured before data is reported.


Microsoft SharePoint Server agent 



Microsoft SQL Server agent 



Each agent instance must be configured and started manually.
MQ Appliance agent 



MongoDB agent 



MySQL agent 



NetApp Storage agent 



Node.js agent 

The agent must be configured before data is reported. You must add a monitoring plug-in to your Node.js application.


Node.js data collector 



OpenStack agent 



Oracle Database agent 



PHP agent 



PostgreSQL agent 



Python data collector 



RabbitMQ agent 



Response Time Monitoring Agent 



Ruby agent 



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.
Ruby data collector 



SAP agent 



SAP HANA Database agent 



SAP NetWeaver Java™ Stack agent 



Siebel agent 



Sterling Connect Direct agent 



Sterling File Gateway agent 



Sybase agent 



Synthetic Playback agent 
The agent is configured and started automatically for public, external-facing applications, but transactions must be created in the Synthetic Script Manager before data is reported.

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.


Tomcat agent 



UNIX OS agent 



VMware VI agent 



WebLogic agent 



WebSphere® Applications agent 

The agent is started automatically but the data collector must be configured before data is reported.


WebSphere Infrastructure Manager agent 



WebSphere MQ agent 



Windows OS agent 


