References > Template Reference > Oracle > Oracle WebLogic (JMX)

Oracle WebLogic (JMX)

This template monitors for Oracle WebLogic server statistics by using the JMX protocol. You can use the Orion agent for Linux or SNMP agentless to monitor.

Prerequisites

Target server configured to allow JMX queries.

Template configuration changes

The following settings in the component monitors should be changed from defaults:

  • This template is configured to send JMX requests on port 8686. For this Oracle WebLogic template, you should change the port to 7001.
  • The URL is set to /jmxrmi by default. For this template, set the URL to /jndi/weblogic.management.mbeanservers.runtime.
  • The JMX protocol default setting for this template is rmi. For this template, change the JMX protocol to ioop.

Credentials

Dependent upon JMX configuration.

Configurations for Orion agent for Linux

For JMX configurations, you need to install and configure WebSphere per your Linux distribution. For details, see the IBM WebSphere documentation site.

The overall steps include:

  1. Get and install WebSphere. You may require credentials for the installation.
  2. During installation, you can turn off the secure storage option as this is not needed. You may need to create a new package group. Make sure to select the Application Server during installation. You may also need to create an administrator account.
  3. Start and stop the WebSphere AppServer.
  4. Access the WebSphere AppServer console to continue configurations. You can access by pointing a browser to http://<websphere-host>:9060/ibm/console. You may need to open a port to 9060 on the websphere host. Use the credentials for the account created during installation.
  5. You need to expose the JMX platform mbeans in the WebSphere AppServer using the console. Click Servers > Server Types > WebSphere application servers and select the listed application server.
  6. Locate the Java and Process Management > Process definition. In the dialog box titled "Generic JVM arguments" enter the following:

    Djavax.management.builder.initial=

    There is nothing after the = sign.

    Dcom.sun.management.jmxremote=true

    Dcom.sun.management.jmxremote.port=8686

    Dcom.sun.management.jmxremote.ssl=false

    Dcom.sun.management.jmxremote.authenticate=false

  7. Restart the AppServer.

Monitored Components

For details on monitors, see SAM Component Monitor Types.

All components may vary in a running environment. You can add your own threshold limits as needed.

Classes Loaded Count

This monitor returns the number of classes that are currently loaded in the Java virtual machine.

Classes Total Loaded Count

This monitor returns the total number of classes that have been loaded since the Java virtual machine has started execution.

Classes Unloaded Count

This monitor returns the total number of classes unloaded since the Java virtual machine has started execution.

Memory Pending Final Count

This monitor returns the approximate number of objects for which finalization is pending.

Memory Heap Init Size (B)

This monitor returns the initial amount of memory in bytes that the Java virtual machine allocates; or -1 if undefined.

Memory Heap Used (B)

This monitor returns the amount of used memory in bytes. The amount of used memory in the returned memory usage is the amount of memory occupied by both live objects and garbage objects that have not been collected, if any.

Memory Heap Committed (B)

This monitor returns the amount of committed memory in bytes.

Memory Heap Max Size (B)

This monitor returns the maximum amount of memory in bytes that can be used; or -1 if undefined.

Memory Non Heap Init Size (B)

This monitor returns the initial amount of memory in bytes that the Java virtual machine allocates; or -1 if undefined.

Memory Non Heap Used (B)

This monitor returns the amount of used memory in bytes.

Memory Non Heap Committed (B)

This monitor returns the amount of committed memory in bytes.

Memory Non Heap Max Size (B)

This monitor returns the maximum amount of memory in bytes that can be used; or -1 if undefined.

Memory Garbage Collections Count

This monitor returns the approximate accumulated collection elapsed time in milliseconds.

Memory Garbage Collection Time (ms)

This monitor returns the approximate accumulated collection elapsed time in milliseconds.

Memory Pool Init Size (B)

This monitor returns the initial amount of memory (in bytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined.

Memory Pool Used (B)

This monitor returns the amount of memory currently used (in bytes).

Memory Pool Committed Size (B)

This monitor returns the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.

Memory Pool Max Size (B)

This monitor returns the maximum amount of memory (in bytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory).

Memory Pool Peak Used (B)

This monitor returns the peak amount of memory currently used (in bytes).

Memory Pool Peak Committed (B)

This monitor returns the peak amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.

Memory Pool Peak Max Size (B)

This monitor returns the maximum peak amount of memory (in bytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory).

Threads Total Started Count

This monitor returns the total number of threads created and also started since the Java virtual machine started.

Current Thread Count

This monitor returns the current number of live threads including both daemon and non-daemon threads.

Current Thread Cpu Time

This monitor returns the total CPU time for the current thread in nanoseconds.

Current Thread User Time

This monitor returns the CPU time that the current thread has executed in user mode in nanoseconds.

Runtime Uptime (ms)

This monitor returns the uptime of the Java virtual machine in milliseconds.

Compiler Time (ms)

This monitor returns the approximate accumulated elapsed time (in milliseconds) spent in compilation.

JVM Runtime: Heap Free Current

This monitor returns the current amount of memory (in bytes) that is available in the JVM heap.

JVM Runtime: Heap Free Percent

This monitor returns the percentage of the maximum memory that is free.

JVM Runtime: Heap Size Current

This monitor returns the current size (in bytes) of the JVM heap.

JVM Runtime: Heap Size Max

This monitor returns the maximum free memory configured for this JVM.

JVM Runtime: Uptime

This monitor returns the number of milliseconds that the Virtual Machine has been running.

JTA Recovery Runtime: Initial Recovered Transactions

This monitor returns the total number of transactions that are recovered from the transaction log initially.

JTA Recovery Runtime: Recovered Transaction Completion Percent

This monitor returns the percentage of transactions that are recovered from the transaction log initially.

Server Security Runtime: Invalid Login Attempts

This monitor returns the total number of invalid logins that have been attempted on this server instance.

Server Security Runtime: Current Locked Users

This monitor returns the current number of locked users on this server instance.

Server Security Runtime: Login Attempts While Locked

This monitor returns the total number of invalid logins that have been attempted on this server instance while a user was locked.

Server Security Runtime: Unlocked Users

This monitor returns the total number of times a user of this server instance has been unlocked.

Server Security Runtime: User Lockout

This monitor returns the total number of user lockouts that have occurred on this server instance.

JTA Coordinator: Threads Constraint Runtime: Out Of Order Executions

This monitor returns the number of requests executed out of turn to satisfy this constraint.

JTA Coordinator: Threads Constraint Runtime: Current Wait Time

This monitor returns the last measured time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.

JTA Coordinator: Threads Constraint Runtime: Executing Requests

This monitor returns the number of requests that are currently executing.

JTA Coordinator: Threads Constraint Runtime: Must Run

This monitor returns the number of requests that must be executed to satisfy the constraint.

JTA Coordinator: Threads Constraint Runtime: Pending Requests

This monitor returns the pending requests that are waiting for an available thread.

JTA Coordinator: Request Class: Pending Request

This monitor returns the number of requests waiting for a thread to become available. A request class represents a class of work. Work using the same request class shares the same priority.

JTA Coordinator: Work Manager: Pending Requests

This monitor returns the number of waiting requests in the queue of Work Manager.

JTA Runtime: Active Transactions

This monitor returns the number of active transactions on the server.

JTA Runtime: Total Transaction

This monitor returns the total number of transactions processed. This total includes all committed, rolled back, and heuristic transaction completions since the server was started.

JTA Runtime: Total Rolled Back Transactions

This monitor returns the number of transactions that were rolled back since the server was started.

User Lockout: Threads Constraint Runtime: Deferred Requests

This monitor returns the number of requests that are denied a thread for execution because the constraint is exceeded.

User Lockout: Threads Constraint Runtime: Executing Requests

This monitor returns the number of requests that are currently executing.

User Lockout: Work Manager: Pending Requests

This monitor returns the number of waiting requests in the queue.

User Lockout: Work Manager: Stuck Thread Count

This monitor returns the number of threads that are considered to be stuck on the basis of any stuck thread constraints.

WLS Admin Server: Allocated IO Buffer Bytes

This monitor returns the amount of off-heap (native) memory, in bytes, reserved for file store use.

WLS Admin Server: Allocated Window Buffer Bytes

This monitor returns the amount of off-heap (native) memory, in bytes, reserved for file store window buffer use.

WLS Admin Server: Object Count

This monitor returns the number of objects contained in the store.