Show Table of Contents
D.3. BEA WebLogic 6.x and higher
The probes in this section (with the exception of JDBC Connection Pool) can be configured to monitor the properties of any BEA WebLogic 6.x and higher server (Administration or Managed) running on a given host, even in a clustered environment. Monitoring of a cluster is achieved by sending all SNMP queries to the Administration Server of the domain and then querying its Managed Servers for individual data.
In order to obtain this higher level of granularity, the BEA Domain Admin Server parameter must be used to differentiate between the Administration Server receiving SNMP queries and the Managed Server undergoing the specified probe. If the host to be probed is the Administration Server, then the BEA Domain Admin Server parameter can be left blank, and both the SNMP queries and the probe will be sent to it only.
If the host to be probed is a Managed Server, then the IP address of the Administration Server should be provided in the BEA Domain Admin Server parameter, and the Managed Server name should be included in the BEA Server Name parameter and appended to the end of the SNMP Community String field. This causes the SNMP queries to be sent to the Administration Server host, as is required, but redirects the specific probe to the Managed Server host.
It should also be noted that the community string needed for probes run against Managed Server hosts should be in the form of
community_prefix@managed_server_name in order for the SNMP query to return results for the desired Managed Server. Finally, SNMP must be enabled on each monitored system. SNMP support can be enabled and configured through the WebLogic Console.
Please see the documentation that came with your BEA server or information on the BEA website for more details about BEA's community string naming conventions: http://e-docs.bea.com/wls/docs70/snmpman/snmpagent.html
D.3.1. BEA WebLogic::Execute Queue
The BEA WebLogic::Execute Queue probe monitors the WebLogic execute queue and provides the following metrics:
- Idle Execute Threads — The number of execution threads in an idle state.
- Queue Length — The number of requests in the queue.
- Request Rate — The number of requests per second.
This probe's transport protocol is User Datagram Protocol (UDP).
Table D.4. BEA WebLogic::Execute Queue settings
| Field | Value |
|---|---|
| SNMP Community String* | public |
| SNMP Port* | 161 |
| SNMP Version* | 1 |
| BEA Domain Admin Server | |
| BEA Server Name* | myserver |
| Queue Name* | default |
| Critical Maximum Idle Execute Threads | |
| Warning Maximum Idle Execute Threads | |
| Critical Maximum Queue Length | |
| Warning Maximum Queue Length | |
| Critical Maximum Request Rate | |
| Warning Maximum Request Rate |
D.3.2. BEA WebLogic::Heap Free
The BEA WebLogic::Heap Free probe collects the following metric:
- Heap Free — The percentage of free heap space.
This probe's transport protocol is User Datagram Protocol (UDP).
Table D.5. BEA WebLogic::Heap Free settings
| Field | Value |
|---|---|
| SNMP Community String* | public |
| SNMP Port* | 161 |
| SNMP Version* | 1 |
| BEA Domain Admin Server | |
| BEA Server Name* | myserver |
| Critical Maximum Heap Free | |
| Warning Maximum Heap Free | |
| Warning Minimum Heap Free | |
| Critical Minimum Heap Free |
D.3.3. BEA WebLogic::JDBC Connection Pool
The BEA WebLogic::JDBC Connection Pool probe monitors the Java Database Connection (JDBC) pool on a domain Admin Server only (no Managed Servers) and collects the following metrics:
- Connections — The number of connections to the JDBC.
- Connections Rate — The speed at which connections are made to the JDBC, measured in connections per second.
- Waiters — The number of sessions waiting to connect to the JDBC.
This probe's transport protocol is User Datagram Protocol (UDP).
Table D.6. BEA WebLogic::JDBC Connection Pool settings
| Field | Value |
|---|---|
| SNMP Community String* | public |
| SNMP Port* | 161 |
| SNMP Version* | 1 |
| BEA Domain Admin Server | |
| BEA Server Name* | myserver |
| JDBC Pool Name* | MyJDBC Connection Pool |
| Critical Maximum Connections | |
| Warning Maximum Connections | |
| Critical Maximum Connection Rate | |
| Warning Maximum Connection Rate | |
| Critical Maximum Waiters | |
| Warning Maximum Waiters |
D.3.4. BEA WebLogic::Server State
The BEA WebLogic::Server State probe monitors the current state of a BEA Weblogic Web server. If the probe is unable to make a connection to the server, a CRITICAL status results.
This probe's transport protocol is User Datagram Protocol (UDP).
Table D.7. BEA WebLogic::Server State settings
| Field | Value |
|---|---|
| SNMP Community String* | public |
| SNMP Port* | 161 |
| SNMP Version* | 1 |
| BEA Domain Admin Server | |
| BEA Server Name* |
D.3.5. BEA WebLogic::Servlet
The BEA WebLogic::Servlet probe monitors the performance of a particular servlet deployed on a WebLogic server and collects the following metrics:
- High Execution Time — The highest amount of time in milliseconds that the servlet takes to execute since the system was started.
- Low Execution Time — The lowest amount of time in milliseconds that the servlet takes to execute since the system was started.
- Execution Time Moving Average — A moving average of the execution time.
- Execution Time Average — A standard average of the execution time.
- Reload Rate — The number of times the specified servlet is reloaded per minute.
- Invocation Rate — The number of times the specified servlet is invoked per minute.
This probe's transport protocol is User Datagram Protocol (UDP).
Table D.8. BEA WebLogic::Servlet settings
| Field | Value |
|---|---|
| SNMP Community String* | public |
| SNMP Port* | 161 |
| SNMP Version* | 1 |
| BEA Domain Admin Server | |
| BEA Server Name* | myserver |
| Servlet Name* | |
| Critical Maximum High Execution Time | |
| Warning Maximum High Execution Time | |
| Critical Maximum Execution Time Moving Average | |
| Warning Maximum Execution Time Moving Average |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.