Fortinet Document Library

Version:


Table of Contents

User Guide

21.4.0
Copy Link

Oracle Weblogic (Windows)

You can use the JMX plugin for Windows to monitor several performance and availability metrics on your Oracle WebLogic application server.

Enable JMX for WebLogic

  1. To enable JMX for WebLogic monitoring, add the following lines to C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin\setDomainEnv.cmd

2. Create the jmxremote.access and jmxremote.password files in C:\Program files\Java\jdk1.8.0_241\jre\lib\management

jmxremote.access – The file should be created as follows.

jmx.password – The file should be created as shown in the example below. Set permission to read-only

3. Both files should appear in the directory as shown below:

4. Open PowerShell and run startWebLogic.cmd.

a. The path is C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain

b. Review the command output for errors. If an error is encountered, resolve the error before continuing.

5. Check MBeans with JConsole.

a. Open JConsole from the command prompt.

b. Select Remote Process then enter the <hostname>:<port>. Use the port configured while enabling JMX in setDomainEnv.cmd.

c. Use the Username and Password set on the jmxremote.password file.

6. Click Connect. Once connected, click the MBeans tab and verify that the data values match the values in the following:

Agent configuration

After installing the Windows Agent, edit the Agent configuration file to add your JMX credentials. The steps are detailed in JMX (Windows) Agent configuration.

Control Panel configuration

The next step is to add and configure the JMX plugin.

  1. Add JMX from the Monitoring Catalog.

  2. Add the Custom JMX Metric.

  3. Enter the following information:
    FieldValuemBean stringEnter java.lang:type=Threading/ThreadCountMetric Name OverrideEnter Thread Count

  4. Click Save.

  5. Verify that the FortiMonitor Agent log has the following output.

Oracle Weblogic (Windows)

You can use the JMX plugin for Windows to monitor several performance and availability metrics on your Oracle WebLogic application server.

Enable JMX for WebLogic

  1. To enable JMX for WebLogic monitoring, add the following lines to C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin\setDomainEnv.cmd

2. Create the jmxremote.access and jmxremote.password files in C:\Program files\Java\jdk1.8.0_241\jre\lib\management

jmxremote.access – The file should be created as follows.

jmx.password – The file should be created as shown in the example below. Set permission to read-only

3. Both files should appear in the directory as shown below:

4. Open PowerShell and run startWebLogic.cmd.

a. The path is C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain

b. Review the command output for errors. If an error is encountered, resolve the error before continuing.

5. Check MBeans with JConsole.

a. Open JConsole from the command prompt.

b. Select Remote Process then enter the <hostname>:<port>. Use the port configured while enabling JMX in setDomainEnv.cmd.

c. Use the Username and Password set on the jmxremote.password file.

6. Click Connect. Once connected, click the MBeans tab and verify that the data values match the values in the following:

Agent configuration

After installing the Windows Agent, edit the Agent configuration file to add your JMX credentials. The steps are detailed in JMX (Windows) Agent configuration.

Control Panel configuration

The next step is to add and configure the JMX plugin.

  1. Add JMX from the Monitoring Catalog.

  2. Add the Custom JMX Metric.

  3. Enter the following information:
    FieldValuemBean stringEnter java.lang:type=Threading/ThreadCountMetric Name OverrideEnter Thread Count

  4. Click Save.

  5. Verify that the FortiMonitor Agent log has the following output.