Applications Manager supports monitoring of Oracle Application Servers 10g.
Applications Manager uses the Dynamic Monitoring Service(DMS) provided by Oracle Application Server to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system where the Applications Manager is running. Refer Prerequisites Section.
To create a Oracle Application Server Monitor
Click on New Monitor link.
Select Oracle AS.
Enter the IP Address or hostname of the host where Oracle Application Server runs.
Enter the SubNetMask of the network.
Enter the Port number for eg., 7200.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which, you want to associate Oracle Application Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Oracle Application Server from the network and starts monitoring them.
Oracle Application servers are monitored based on the attributes listed below. The monitoring details of Oracle Application server are represented graphically that helps to understand the parameters with ease. You can also configure thresholds to the attributes monitored by the server based on these details.
Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations. Click on the individual monitors listed, to view the following information.
|Port||The port at which the Oracle Application server listens.|
|Last Polled at||Specifies the time when the monitoring of the server was started.|
|Availability||Shows the current status of the server - available or not available.|
|Throughput||Number of requests processed per unit of time in the server.|
|Current Active Connection||Shows the current active connections|
|Average Connection Process Time||Gives the average processing time of the connections|
|Current Active Request||Shows the number of requests that are active currently|
|Server Response Time|
|Response Time||Refers to the time required for the server to respond while monitoring.|
|Data Throughput||Refers to how much data is transferred per unit time|
|Data Processed||Refers to how much data is processed per request|
|Servlets||Total number of servlets|
|OPMN Process Memory Stats (Memory statistics of the OPMN processes like dcm-daemon, WebCache, WebCache Admin, HTTP_Server, home)|
|Used Memory||Gives the total physical memory used by the process|
|Status||Gives the availability status of the process|
oc4j JVM Statistics
|Active Thread Groups||Shows the number of Active Thread groups in the JVM|
|Active Threads||Shows the number of Active Threads in the JVM|
|Heap Usage||Shows current heap memory usage of the process|
|JDBC Connections||Gives the total number of JDBC Connections|
|Transactions||Gives the total number of open, committed and aborted JDBC transactions|
|Servlets||Total number of servlets in the web application|
|Throughput||Number of requests processed per unit of time in the web application|
|Process Request||Time taken to process the request|
|Active Request||Current number of active requests for the web application|
|Active Session||Number of active sessions of the web application|
|Session time||Total time for which the sessions have been active|
|Deque Avg||Average time to deque messages|
|Enque Avg||Average time to enque messages|
|Pending Message||Total number of message waiting to be processed|
|Message Dequeued||Total number of messages dequeued|
|Message Enqueued||Total number of messages enqueued|
|Message Count||Number of messages in the JMS Destination|
|EAR Name||Name of the Enterprise Application Resource|
|Process||Name of the oc4j process to which the EJB belongs to|
|Type||Gives the type of the EJB|
|Create Count||Number of EJBs created|
|Active Count||Number of active EJBs|
|Passive Count||Number of passive EJBs|
|Pooled Count||Number of pooled EJBs|
|Response Summary||Gives the count for the various HTTP responses|