Application class icons and functions
Following table provides the icon for each application class, the application class name, and a brief description of its function.
Application class icons and functions
Icon | Application class name | Function |
---|---|---|
Oracle WebLogic Server application class | ||
| BEAWLS_SERVER | Represents an Oracle WebLogic Admin Server application instance. At the BMC PATROL Console level, the icon represents the entire WebLogic monitoring environment. This icon is created for all monitored environments. |
Setup application class | ||
BEAWLS_CLUSTER | Represents WebLogic clustering. This is an optional environment supported in Oracle WebLogic Server and does not apply when you monitor a single Managed Server. | |
Portal cache management application class | ||
BEAWLS_EJBCACHE | This class is used for monitoring an XML Cache. | |
Enterprise Java Bean application class | ||
BEAWLS_EJB | Represents all deployed EJBs deployed on a given server | |
Execution queues application class | ||
BEAWLS_EXEC_QUEUE | Monitors and manages the execution queues on each server. Queues are monitored for queue length, thread activity, and requests processed This icon is always be created for all monitored environments. | |
J2EE application class | ||
BEAWLS_J2EE_APPS | Shows the deployed J2EE application under the monitored WebLogic environment*Note:* This application class applies only to Oracle WebLogic Server 8.1 SP1 and later environments | |
JCA application class | ||
BEAWLS_JCA | Supports the J2EE Connector Architecture (JCA); monitors configuration and run time information from a JCA connection pool in Oracle WebLogic Server 8.1, 9.x, 10. x, 11.x, and 12.x environments | |
Java database connection pool application class | ||
BEAWLS_JDBC | Represents all deployed JDBC connection pools and is created at main discovery regardless of the number of configured connection pools | |
JMS application class | ||
BEAWLS_JMS | Monitors and manages the JMS server, which enables communication between applications in Oracle WebLogic Server 8.1, 9.x, 10. x, 11.x, and 12.x. | |
JMS destination application class | ||
BEAWLS_JMS_DESTINATION | Monitors the JMS destinations | |
JMS server application class | ||
BEAWLS_JMSSERVER | Monitors and manages the JMS server, which enables communication between applications in Oracle WebLogic Server 8.1, 9.x, 10. x, 11.x, and 12.x. | |
Jolt for WebLogic application class | ||
BEAWLS_JOLT | Represents configured Jolt connection pools deployed in the WebLogic environment Jolt is a Java client API that manages requests for Oracle Tuxedo services | |
JROCKIT application class | ||
BEAWLS_JROCKIT | Represents the Oracle WebLogic JRockit JVM 1.4.1 or later. | |
Monitoring JVM profiling using JMX | ||
| BEAWLS_JVMJMX | The BEAWLS_JVMJVX application class represents the JVM JMX monitoring. |
Local managed application class | ||
BEAWLS_LOCAL_MANAGED | Monitors and manages a WebLogic Managed Server that is running on the same host as the PATROL Agent (see also the Managed Server Application Class, BEAWLS_MANAGED) | |
Managed Server application class | ||
BEAWLS_MANAGED | Monitors and manages a "managed" WebLogic Server that is remote to a given PATROL Agent (see also Local Managed Server application class, LOCAL_MANAGED) In an environment with multiple WebLogic Server instances, one server will be designated the Admin Server and the other servers designated as Managed Servers | |
HTTP and JSP servlet application class | ||
BEAWLS_SERVLET | Represents HTTP, Java Server Page (JSP), and servlets HTTP, JSP, and servlets represent server-side logic in e-commerce applications Servlets are not automatically discovered. Instances of this application class are created only after you have selected theMonitor Servlets command. | |
SAF service application class | ||
| BEAWLS_SAF | Monitors the SAF service This icon is created under each WebLogic Server instance of a monitored domain which includes SAF Agents |
SAF agent application class | ||
| BEAWLS_SAFAGENT | Monitors the SAF agents This icon is created under each BEAWLS_SAF instance. |
Threadpool application class | ||
| BEAWLS_THREADPOOL | Monitors the thread pool of all Oracle WebLogic servers inside the domain Note: This application class is supported only on WebLogic Server 9. x,10. x, 11.x, and 12.x. |
Tuxedo Connector application class | ||
BEAWLS_TUXEDO_ CONNECTOR | Monitors the WebLogic Tuxedo Connector service in all Oracle WebLogic Servers inside the domain*Note*: This application class is supported only on WebLogic Server 9.1, 10. x, 11.x, and 12.x. | |
Web applications application class | ||
BEAWLS_WEBAPP | Monitors and manages resources used by a web application running on a configured and managed Oracle WebLogic Server Monitors all deployed web applications and can monitor specific servlets for a given application | |
Web service application class | ||
BEAWLS_WS | Represents the deployed web services under the monitored Oracle WebLogic Server. | |
Web service operation application class | ||
BEAWLS_WS_OPER | Describes the operation state of the deployed web services under the monitored Oracle WebLogic Server | |
Workload application class | ||
| BEAWLS_WORKLOAD | Monitors the overload condition of the J2EE application Work Managers |
JMX_MAIN application class | ||
BEAWLS_MAIN | Provides menu commands used to configure BMC PATROL for Oracle WebLogic This icon is created for all monitored environments. | |
JMX_DOMAIN application class | ||
BEAWLS_DOMAIN | Each instance represents a grouping of MBeans; from this icon, you can manage all MBeans that have the same domain name | |
JMX_SERVER application class | ||
BEAWLS_JMX_SERVER | Each instance represents an MBean server; MBean servers for Oracle WebLogic are automatically registered | |
JMX_CONDITION application class | ||
BEAWLS_JMX_CONDITION | Each instance represents a monitored condition that you have previously defined. |