IBM Performance Management

Installing agents

You can install any combination of monitoring agents on a managed system. For example, if you install the Monitoring Agent for MySQL for monitoring MySQL servers, you might want to also install the Response Time Monitoring Agent to gather more response time information for your Ruby applications. You might also want to install the Monitoring Agent for Windows OS to monitor other aspects of your system, such as the overall CPU, memory, and disk.

Your offering determines which monitoring agents are available for installation. For a list of the agents included in each offering, see Offerings, add-ons, and agents.

For a list of the agents that run on a Windows system, see Preinstallation on Windows systems.

Before you begin

Download the agents. For details about the options for downloading the agent images, see Download instructions.

Review the information in System requirements to make sure that you have the requirements for the agents you plan to install.

Ensure that you have adequate permission to run the agent installation script and agent commands. You must be logged in using one of the following user account types: the default windows administrator user account, an administrator user account, a user account which is a member of the administrators group, a user account that is registered as administrator in Active Directory services.

Review the agent prerequisite tasks before you install the agents. For details, see Preinstallation on Windows systems.

Before you install new agents, Windows Installer temporarily stops all agents currently running in the installed product location. After installation completes, the installer restarts any agents that were stopped. You must manually restart any monitoring agent that is not automatically configured and started by the installer. Review the information in Agent deployment for a preview of the tasks that are required after you complete the installation steps.

Before you install the agents, you must configure the agent images with the connection details for the Performance Management server. If you downloaded the agent installation images to the same directory as the server installation image, the agent installation images are configured automatically. Otherwise, follow the procedure in Configuring the installation images.

Agent coexistence is supported. You can install IBM Performance Management agents on the same computer where IBM Tivoli® Monitoring agents are installed. However, both agent types cannot be installed in the same directory. For more information about agent coexistence, see Performance Management agent and Tivoli Monitoring agent coexistence.

Procedure

Complete these steps to install monitoring agents on VMs and systems where the Windows operating system is installed:

On your system, navigate to the directory where your configured agent images are located.
Extract the agent installation files for your offering (or offerings) to the location where you want to install the monitoring agent software.
- IBM Application Performance Management Advanced: 64-bit ipm_apm_advanced_agents_win_8.1.3.zip; 32-bit ipm_apm_advanced_agents_win32_8.1.3.zip
- IBM Application Performance Management: 64-bit ipm_apm_agents_win_8.1.3.zip; 32-bit ipm_apm_agents_win32_8.1.3.zip
- IBM Monitoring: 64-bit ipm_monitoring_agents_win_8.1.3.zip; 32-bit ipm_monitoring_agents_win32_8.1.3.zip
- IBM Application Diagnostics: 64-bit ipm_app_diag_agents_win_8.1.3.zip; 32-bit ipm_app_diag_agents_win32_8.1.3.zip
The .bat installation script is extracted to a directory named for the archive file and version. For example: offering_Agent_Install_8.1.3. Agent binary and configuration-related files are extracted into subdirectories within that directory.
Open a command prompt as administrator.
1. From the Start menu, type command in the search box.
2. Right-click Command Prompt from the list that displays and select Run as administrator.
From the command prompt, run the installation script with Administrator privileges from the directory that is named for the archive file and version:
```
cd offering_Agent_Install_version
installAPMAgents.bat
```
The installer checks that the agent images were configured with parameters for connecting to the Performance Management server. If the agents images were not configured, the installation is stopped. You must configure the agent images (Configuring the installation images) and start the agent installation procedure from step 1.
Restriction: For the WebSphere® Applications agent, the Administrator privileges must be the same privileges that were used to install the WebSphere Application Server.
To install the agents in silent mode, see Installing agents silently.
If you are installing the agents, provide the name of the installation directory. The default installation path is C:\IBM\APM. The name of the installation directory cannot exceed 80 characters or contain non-ASCII, special, or double-byte characters. Directory names in the path can contain only the following characters: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ _\:0123456789()~-./.
If you are upgrading the agent, this step is skipped, and the agent installs into the previous installation directory.

Microsoft .NET agent: If you do not install the agent into the same directory as the previous version of the agent, you must change the bin path of the Profiler service after you upgrade the agent. For details, see Upgrading your agents. Alternatively, either install the agent into a new directory or uninstall and reinstall the agent. For uninstall instructions, see Uninstalling your agents
When you are asked if you accept the license agreement, enter 1 to accept the agreement and continue, or enter 2 to decline. After you enter 1 (accept), a prerequisite scan of your environment starts and takes a few moments to complete. If any requirements are missing, a message directs you to a log file with the reason for the failure. A prerequisite, such as a missing library or insufficient disk space, stops the installation. You must address the failure, and start the installation script again.
After installation is complete and the command prompt is available, repeat these steps to install more monitoring agents.

What to do next

Configure the agent as required. If your monitoring agent requires configuration as described in Agent deployment or if you want to review the default settings, see Configuring your environment.

If a firewall is enabled, ensure that TCP port 80 for HTTP or 443 for HTTPS on the monitoring agent is open for incoming connections from the Performance Management server. These ports are the default firewall ports for incoming HTTP and HTTPS requests and are likely open.
If you upgraded an agent from a previous version, identify any reconfiguration or migration tasks that you must complete before you log in to the Performance Management console. For information about those tasks, see Upgrading your agents.

Use one of the following methods to start the agent:

Click Start > All Programs > IBM Monitoring agents > IBM Performance Management. Right-click on an agent and click Start.
Run the following commands
```
./name-agent.bat start
```

For information about the monitoring agent commands, including the name to use, see Using agent commands. For information about which agents are started automatically and manually, see Agent deployment

After an upgrade, you must restart any agent that is not both automatically configured and started by the installer.

After you configure and start the agent, view the data that the agent is collecting.

If you are not logged in, follow the instructions in Starting the Performance Management console.
If you want to view managed systems from your IBM Tivoli Monitoring domain in the Application Performance Dashboards, complete the tasks that are described in Integrating with Tivoli Monitoring.