Configuring WebLogic monitoring

The Monitoring Agent for WebLogic provides you with a central point of monitoring for the health, availability, and performance of your WebLogic server environment. The agent displays 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).

Before you begin

  • The product version and the agent version often differ. The directions here are for the most current release of this agent. For information about how to check the version of an agent in your environment, see Agent version command. To access the documentation for earlier agent releases, see the Table 1 table.
    Table 1. Agent versions
    Agent version Documentation
    8.1.4, 8.1.4.1 8.1.4
    8.1.3.2 IBM Performance Management 8.1.3 1

    1 The link opens an on-premises Knowledge Center topic.

  • Make sure that the system requirements for the WebLogic agent are met in your environment. For the up-to-date system requirement information, see the Software Product Compatibility Reports (SPCR) for the WebLogic agent.
  • Before you configure the WebLogic agent, the Oracle WebLogic server first must be configured by completing the following tasks:
    Note: Most of the Oracle WebLogic server configuration is done by using the administrative console, typically at http://weblogic-server:7001/console.
    1. Set up a monitor user in the Monitors group.
      1. Select the domain to monitor/edit.
      2. Select Security Realms.
      3. Select your security realm (or create one if one does not exist).
      4. Create a user that will be used to communicate with WebLogic over JMX.
      5. Add this user the Monitors group.
      6. Save the changes to the domain.
    2. Enable the Listen Ports.
      1. Select the domain to monitor/edit.
      2. On each server that you want to monitor, click Environment > Servers > Select a server .
      3. Ensure that the Listen Port is enabled and note its port number.
      4. If you want to enable SSL, then ensure that the SSL Listener Port is enabled and set a port for SSL as well.
    3. Enable the JMX MBean Server Connections.
      1. Select the domain that you want to monitor/edit.
      2. Select Configure > Advanced.
      3. Check Platform Mbean Server Enabled.
      4. Save the change.
    4. Enable the IIOP Protocol option.
      1. Select the domain that you want to monitor/edit.
      2. On each server that you would like to monitor, click Environment > Servers then select a server.
      3. Select the Protocol Tab > Select IIOP.
      4. Under the Advanced section, enter the default IIOP user name and password.
      5. Save the change.
    5. Enable SSL.
      1. Enable HTTP Tunneling.
        1. Go to Environment > Servers > Select a server > Protocol > General.
        2. Check Enable HTTP Tunneling.
      2. Enable SSL Listen Port.
        1. Go to Environment > Servers > Select a server > Configuration > General.
        2. Configure a port number.

About this task

The WebLogic agent is both a multiple instance agent and also a multiple subnode agent. You can create one agent instance with multiple subnodes – one for each WebLogic server, or you can create an agent instance for each WebLogic server with one subnode for that server. Or you can create a combination of each type of configuration. After you configure agent instances, you must start each agent instance manually.

Procedure

  1. To configure the agent on Windows systems, use the IBM Performance Management window or the silent response file with the agent configuration batch file.
  2. To configure the agent on Linux and UNIX systems, run the agent configuration script and respond to prompts, or use the silent response file.

What to do next

Log in to the Cloud App Management user interface to view monitoring data. For more information, see Starting the Cloud App Management UI.

If you are unable to view the data in the agent dashboards, first check the server connection logs and then the data provider logs. The default paths to these logs are as follows.
  • Linux /opt/ibm/apm/agent/logs
  • Windows C:\IBM\APM\TMAITM6_x64\logs