Preinstallation on Windows systems

You must complete the required preinstallation tasks before you install agents on Windows systems. Some preinstallation tasks are agent-specific and other tasks apply to multiple agents.

Note: These requirements are in addition to the requirements identified in the Software Product Compatibility Reports for your agent: For the current version requirements and dependencies for your agent, see the IBM® Cloud Application Performance Management Software Product Compatibility Report for agents on Windows.

All agents

The following preinstallation tasks are applicable to all agents:

Test connectivity
Before you install agents, ensure that your system can communicate with the Cloud APM server. For information about checking connectivity to the Cloud APM server, see Network connectivity.
Installing from the command prompt on a local drive
Use the Windows command prompt to start the installation script. Do not use Windows PowerShell to start the installation script.
Copy the installation files to a local disk or a mapped network drive, and then start the installation script. Do not start the installation script from a network location.
Start the installation script from a new command prompt. Do not start the installation script from an existing command prompt because the command prompt might have outdated environment variables.
Setting the CANDLEHOME environment variable
If you used the ITM Agent Converter to install and configure an agent on the same managed system before, the CANDLEHOME environment variable changed to that directory where you installed the agent with the Agent Converter. Before you install and configure a native Cloud APM agent, you must set the CANDLEHOME environment variable to a different directory, otherwise, the native Cloud APM agent cannot start.

Specific agents

The following preinstallation tasks are applicable to the specified agents:

DataStage® agent
  1. Enable parameters in the DSODBConfig.cfg file. Complete the following steps:
    1. Open the DSODBConfig.cfg file at the following location in an editor:
      • infosphere_information_server_install_dir\Server\DSODB
    2. Uncomment the following parameters by removing # symbol:
      • MonitorLinks=1
      • JobRunUsage=1
      • ResourceMonitor=1
      • DSODBON=1
    3. Edit values of these parameters equal to 1.
  2. Copy the JDBC driver of the database that is used for metadata repository configuration on the agent computer.
    1. Type 4 JDBC 4, or later. Example: db2jcc4.jar
    2. Type 4 JDBC driver for Oracle. Example: ojdbc6.jar
    3. JDBC driver for MS SQL:
      • Sqljdbc41.jar requires a JRE of 7 and supports the JDBC 4.1 API.
      • Sqljdbc42.jar requires a JRE of 8 and supports the JDBC 4.2 API.
IBM Integration Bus agent
Make sure the user ID to install the IBM Integration Bus agent is in the mqbrkrs user group.
Internet Service Monitoring
For the Internet Service Monitoring, you must apply IBM Cloud Application Performance Management 8.1.4.0 core framework Interim Fix 3 on the APM Server from here and then preconfigure the agent. The Agent and the bridge module use ports 9510 and 9520. In case these ports are already in use the installation will not progress.
Note:
  • For existing users it is recommended to install Internet Service Monitoring agent on 64-bit platforms either Windows or Linux rather than upgrading the agent on Windows 32-bit platform to a newer version.
  • Internet Service Monitoring Agent does not support Windows 2008 R2 on Windows 64-bit platform.
MySQL agent
For the Monitoring Agent for MySQL, you must install the MySQL server and MySQL JDBC driver before you install the MySQL agent on that system. To install the JDBC driver, see MySQL Connector/J JDBC driver.
Oracle Database agent
If the Oracle Database agent monitors the Oracle database remotely, you must install the Oracle instant clients first from Oracle Technology Network - Instant Client Downloads on the following systems:
  • Windows Server 2012 64-bits
  • Windows Server 2012 R2 64-bits
  • Windows Server 2008 R2 Datacenter 64-bits
  • Windows Server 2008 R2 Enterprise 64-bits
  • Windows Server 2008 R2 Standard 64-bits
The instant clients v10.x, v11.x, and v12.x are supported by the Oracle Database agent.
Response Time Monitoring Agent

Before you install the Response Time Monitoring agent, review the installation planning section here: Planning the installation.

SAP HANA Database agent
  1. Install SAP HANA database client HDBSQL version 1.00.102.06 or later on the Windows system.
  2. Add the installation path of the SAP HANA client to the PATH environment variable.

    Example: Add C:\Program Files\sap\hdbclient to the PATH environment variable, where C:\Program Files\sap\hdbclient indicates the installation path of the SAP HANA database client.

SAP NetWeaver Java™ Stack agent
When you install SAP NetWeaver Java™ Stack Agent with Windows OS Agent on Windows Operating System, if you enter spaces in the installation directory names, then the agent data is not displayed on the APM UI. Ensure that you do not use any spaces in the directory names.
Tomcat agent
  1. Java SDK is installed on the Tomcat server where the agent is installed.
  2. The SDK path is added to the PATH variable directly or by using the set path command before installing the agent.
  3. The JAR command is working.