Configuring the agent on Windows systems

You can configure the agent on Windows operating systems by using the IBM Performance Management window.

Before you begin

Ensure that the following prerequisites are met:
  • Java is installed on the Tomcat Server where the agent is installed.
  • JDK 1.6 or later version is set on the prompt from where the agent installer is installed.
  • JMX Remote is enabled for the Tomcat Server. For details, see Enabling JMX Remote.
  • The Tomcat Server is up and running.

About this task

You can configure the agent from the command prompt. For details, follow the steps that are given in the Configuring the Tomcat agent on Linux systems topic, and run the commands with the .bat extension instead of .sh extension. The following procedure explains configuring the agent by using the agent configuration panel.

Procedure

  1. Click Start > All Programs > IBM Monitoring agents > IBM Performance Management.
  2. In the IBM Performance Management window, right-click Monitoring Agent for Tomcat.
  3. Click Configure agent.
    Attention: If Configure agent is unavailable, click Reconfigure.
  4. In the Instance Name window, specify a unique name for the Tomcat agent instance, and click OK.
    Restriction: The MSN must not exceed 32 characters.
  5. In the SERVER NAME field, enter a unique name to identify the Tomcat Server that is being monitored.
  6. In the Java Parameter Settings window, complete one of the following steps:
    • Click Next to accept the default location where Java™ is installed. The default installation path is C:\IBM\APM\java\java80_x64\jre.
    • In the Java Home field, specify the path when IBM Java is installed at a different path.
  7. In the JSR-160-Complaint Server window, specify the details of the following parameters:
    1. In the JMX user ID field, specify the ID of the user that is used to connect to the Tomcat MBean server when the JMX authorization is enabled in Tomcat.
    2. In the JMX password field, specify the password of the JMX user when the JMX authorization is enabled in Tomcat.
    3. In the JMX service URL field, enter the URL that is used for connecting to the Tomcat MBean server.
      The format of the URL is service:jmx:rmi:///jndi/rmi://host_name:port_number/jmxrmi. The default URL is valid when the server runs on the local host and uses the 8686 port as a JMX port. You can modify the host name and port number in the URL, keeping the same format.
    4. From the Data Collector Configuration list, select Yes if you want to enable collection of transaction tracking and deep dive data.
  8. In the Monitoring Agent for Tomcat window, right-click the Tomcat agent instance, and click Start.
  9. Enable the collection of Transaction Tracking and Deep Dive data and restart the Tomcat Server.

What to do next

If Tomcat agent is running as a service, after configuring the agent on Windows, configure Tomcat Data Collector. For more information, see Configuring Tomcat Data Collector.

Log in to the Cloud APM console to view data that is collected by the agent in the dashboards. For information about using the Cloud APM console, see Starting the Cloud APM console.