Configuring your environment
If your monitoring agent requires configuration or you want to review the default settings for an agent, follow the steps provided for your agent.
- Configuring agents
After installation, some agents are configured and started automatically, while some agents require manual configuration but start automatically. Some agents must be configured and started manually. Multiple instance agents require creating a first instance and starting manually. - Using agent commands
The same scripts that you use to install monitoring agents are also used to check the status of an installed agent, stop or start it, or uninstall the agent. - Using the IBM Performance Management window on Windows systems
Windows supported agents have a GUI utility that you can use to perform agent configuration and check the connection status. - Agent Configuration page
Use the Agent Configuration page to centrally configure settings for such agents as the Response Time Monitoring Agent and WebSphere® Applications agent. - Configuring agents as a non-root user
If you want to configure your agent as a non-root user, create a common group on the system and make each user a member of this group. - Connecting agents to a different server
If you want to change the Performance Management server that the agents connect to, run the agent2server script to establish communications with a different server. - Configuring agents to communicate through a forward proxy
If your firewall rules do not allow transparent outbound HTTPS connections to external hosts, you can configure IBM® monitoring agents to send traffic to a forward proxy. Edit the KDH_FORWARDPROXY environment variable to configure agents to communicate through the forward proxy. - Configuring certificates between the server and agents
To enable communication between the Performance Management server and agents, you can configure default, custom, or self-signed certificates. - Configuring the Cisco UCS agent
The Monitoring Agent for Cisco UCS monitors the Cisco UCS Virtual Infrastructure by connecting to the Cisco UCSM. You must configure the Cisco UCS agent so that the agent can collect the Cisco UCS data. - Configuring the Citrix VDI agent
The Citrix VDI agent provides a central point of monitoring for your Citrix XenDesktop or XenApp resources, including delivery groups, catalogs, applications, desktops, users, and sessions. Before the agent can be used, you must configure the agent to collect data through the delivery controller. - Configuring DataPower monitoring
To monitor DataPower appliances, you need to first configure the Monitoring Agent for DataPower®, then complete some configuration tasks on your appliances. - Configuring the DB2 agent
The Monitoring Agent for DB2® monitors the availability and performance of the DB2 server. You can monitor multiple servers from the Performance Management console; each server is monitored by a DB2 agent instance. - Configuring the Hadoop agent
You must configure the Monitoring Agent for Hadoop so that the agent can collect data from the Hadoop cluster that is being monitored. - Configuring the HMC Base agent
The HMC Base agent provides you with the capability to monitor the Hardware Management Console (HMC). The agent monitors the availability and health of the HMC resources: CPU, memory, storage, and network. The agent also reports on the HMC inventory and configuration of Power® servers, CPU pools, and LPARs. The CPU utilization of the Power servers, LPARs, and pools are monitored by using HMC performance sample data. - Configuring the HTTP Server agent
The Monitoring Agent for HTTP Server starts automatically. You must review the configuration file that the agent creates for the IBM HTTP Server. Then, you must add the data collector configuration manually to the server configuration file. To gather more response time information for the HTTP Server agent, you can install the Response Time Monitoring Agent. - Configuring the IBM Integration Bus agent
The IBM Integration Bus agent is a multiple instance agent. You must create a first agent instance and start it manually. - Configuring the JBoss agent
The JBoss agent monitors the resources of JBoss application servers and the JBoss Enterprise Application platform. Use the dashboards that are provided with the JBoss agent to identify the slowest applications, slowest requests, thread pool bottlenecks, JVM heap memory and garbage collection issues, busiest sessions, and other bottlenecks on the JBoss application server. This agent is a multiple instance agent; you must create the instance first and then start the agent manually. - Configuring the Linux KVM agent
The Monitoring Agent for Linux KVM supports connection to both the Enterprise Linux based KVM hypervisor and Red Hat Enterprise Virtualization Manager (RHEVM) environments. You can use the same configuration script to configure instances for these environments. - Configuring the Microsoft Active Directory agent
The Monitoring Agent for Microsoft Active Directory is automatically configured and started after installation. - Configuring the Microsoft Cluster Server agent
You must configure the Monitoring Agent for Microsoft Cluster Server so that the agent can collect the cluster server data. Use the silent response file to configure the agent. - Configuring the Microsoft Exchange Server agent
You must configure the Monitoring Agent for Microsoft Exchange Server to monitor the availability and performance of Exchange Servers. - Configuring the Microsoft Hyper-V Server agent
When you install the Monitoring Agent for Microsoft Hyper-V Server, the agent is automatically configured and started with the default configuration settings. Use the silent response file to modify the default configuration settings. - Configuring the Microsoft IIS agent
When you install the Microsoft IIS agent, the agent is automatically configured and starts with the default configuration settings. - Configuring the Microsoft Lync Server agent
When you install the Microsoft Lync Server agent, the agent is automatically configured and started with default values in the configuration panel. - Configuring the Microsoft .NET agent
The Microsoft .NET agent starts automatically after installation to collect the resource monitoring data. However, to collect the transaction tracking and diagnostic data, you must manually configure the data collector, which is a component of the Microsoft .NET agent. The data collector gathers the transaction tracking and diagnostics data and passes the data to the monitoring agent. - Configuring the Microsoft SharePoint Server agent
When you install the Monitoring Agent for Microsoft SharePoint Server, the agent is automatically configured and started with the default configuration settings. Use the silent response file to modify the default configuration settings. - Configuring the Microsoft SQL Server agent
You must configure the Monitoring Agent for Microsoft SQL Server so that the agent can collect data from the application that is being monitored. - Configuring the MongoDB agent
The MongoDB agent requires an instance name. You must manually configure and start the agent instance. - Configuring the MySQL agent
The Monitoring Agent for MySQL requires an instance name and the MySQL server user credentials. You can change the configuration settings after you create the first agent instance. - Configuring the Node.js agent
You must add one or more plug-ins to your Node.js application and restart it before the agent can begin monitoring your application. - Configuring the Oracle Database agent
The Oracle Database agent provides monitoring capabilities for the availability, performance, and resource usage of the Oracle database. You can configure more than one Oracle Database instance to monitor different Oracle databases. The remote monitoring capability is also provided by this agent. - Configuring the OS agents
The Monitoring Agent for Linux OS, Monitoring Agent for UNIX OS, and Monitoring Agent for Windows OS agents are configured automatically. However, you can configure log file monitoring for the OS agents so that you can monitor application log files. Also, you can run the OS agents as a non-root user. - Configuring the PHP agent
You must configure the Monitoring Agent for PHP so that the agent can collect data from the PHP application that is being monitored. - Configuring the PostgreSQL agent
You must configure the Monitoring Agent for PostgreSQL so that the agent can collect data from the PostgreSQL database that is being monitored. - Configuring the Python agent
You must configure the Monitoring Agent for Python so that the agent can collect data from the Python application that is being monitored. - Configuring the Response Time Monitoring agent
You can customize the data that is collected by the Response Time Monitoring agent for display in the End User Transactions dashboards. - Configuring the Ruby agent
The Monitoring Agent for Ruby is a multiple instance agent; you must create the first instance and start the agent manually. The following web servers are supported by Ruby agent: WEBrick, Thin, Puma, Unicorn, and Passenger. - Configuring the SAP agent
To monitor a SAP system, the Monitoring Agent for SAP Applications must connect to an application server in the system to be monitored so that the agent can access the Advanced Business Application Programming (ABAP) code that is provided with the product. - Configuring the SAP HANA Database agent
You must configure the SAP HANA Database agent so that the agent can collect data of the SAP HANA database server that is being monitored. - Configuring the Synthetic Playback agent
You must configure the Synthetic Playback agent so that the agent can collect data on the availability and performance of internal web applications. This data is displayed in the Application Performance Dashboard. - Configuring the Tomcat agent
The Tomcat agent monitors the resources of Tomcat application servers. This agent requires an instance name, so you must create the first agent instance and start the agent manually. - Configuring the VMware VI agent
The VMware VI agent monitors the VMware Virtual Infrastructure by connecting to the VMware Virtual Center. You must configure the VMware VI agent so that the agent can collect the VMware data. - Configuring the WebLogic agent
The WebLogic agent provides a central point of monitoring for the health, availability, and performance of your WebLogic server environment. The agent provides a comprehensive set of metrics to help you make informed decisions about your WebLogic resources, including Java virtual machines (JVMs), Java messaging service (JMS), Java Database Connectivity (JDBC), and more. Before the agent can be used, you must configure the agent. - Configuring the WebSphere Applications agent
Configuring the WebSphere Applications agent mainly involves configuring the data collector, which is a component of the agent. - Configuring the WebSphere Infrastructure Manager agent
Configure the WebSphere Infrastructure Manager agent to monitor the performance of WebSphere Deployment Manager and Node Agent. - Configuring the WebSphere MQ agent
The WebSphere MQ agent supports only WebSphere MQ 7.1 or later. Before you can start the agent, you must assign an instance name to the agent and complete the several configuration tasks for the user ID, managed system names, or transaction tracking optionally.