Oracle® Enterprise Manager Oracle Application Server Metric Reference Manual 10g Release 2 (10.2) Part Number B25987-01 |
|
|
View PDF |
There are various metrics which can be used to monitor Oracle Forms Services.
The JVM Controllers category provides information about all the JVM controllers. The following table lists the metrics and their descriptions.
Table 14-1 Jvm Controllers Metrics
Metric | Description |
---|---|
Classpath |
Classpath of this JVM Controller |
CPU |
This metric is calculated from the total amount of CPU utilized by this Forms JVM controller |
Forms Sessions |
Number of Forms sessions this JVM Controller is handling |
JVM Options |
JVM options this JVM controller was started with |
JVMs |
Number of JVMs this JVM controller is handling |
Logfile |
Location of the logfile for this JVM controller |
Logging |
Specified whether the Logging is turned on or off for this JVM controller |
Max Processes |
maximum number of Forms Runtimes Processes this JVM controller can service before creating a child JVM |
Private Memory |
This metric is calculated from the total amount of private memory used by this Forms JVM controller |
Start Time |
Start time of this JVM controller |
The JVM Load category provides information about the present Load generated by the Forms JVM processes. The following table lists the metrics and their descriptions.
Table 14-2 Jvm Load Metrics
Metric | Description |
---|---|
Total CPU (%) |
This metric is calculated from the total amount of CPU being used by all the Forms JVM processes. By default, the thresholds for this metric is not defined. The value for the thresholds can be edited as required. |
Total Memory |
This metric is calculated from the total amount of private and shared memory being used by all the Forms JVM processes. |
Total Private Memory |
This metric is calculated from the total amount of private memory being used by all the Forms JVM processes. |
Total Shared Memory |
This metric is calculated from the total amount of shared memory being used by all the Forms JVM processes. |
The Load category provides information about the present Load generated by Forms processes.
This metric is calculated from the total amount of CPU being used by all the Forms processes. By default, the thresholds for this metric are not defined The value for the thresholds can be edited as required.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 14-3 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Minute |
After Every 12 Samples |
> |
Not Defined |
Not Defined |
1 |
CPU Utilization is %value%%% |
Data Source
The value of this metric is calculated using operating system specific commands.
This metric is calculated from the total amount of private and shared memory being used by all the Forms processes.
By default, this metric has a critical threshold of 90 and a warning threshold of 80. A critical alert is generated when the metric value exceeds the critical threshold value 1 time. A warning alert is generated when the metric value exceeds the warning threshold value 1 time. The value for the thresholds can be edited as required.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 14-4 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Minute |
After Every 12 Samples |
> |
80 |
90 |
1 |
Memory Utilization is %value%%% |
Data Source
The value of this metric is calculated using operating system specific commands.
This metric reports the total number of Forms sessions being monitored by Enterprise Manager.
Metric Summary
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Minute |
Data Source
This value of this metric is based on the number of Forms processes executing on the host. The current value of this metric can also be seen under Response and Load on the Forms Overview Page.
The Response category provides information about the responsiveness of the Forms Servlet.
This metric displays the response time in milliseconds for the Oracle Forms Servlet.
By default, this metric has a critical threshold of 1000 and a warning threshold of 500. A critical alert is generated when the metric value exceeds the critical threshold value 1 time. A warning alert is generated when the metric value exceeds the warning threshold value 1 time. The value for the thresholds can be edited as required.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 14-5 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Minute |
After Every 12 Samples |
> |
500 |
1000 |
1 |
The Forms Listener response time is unacceptable. |
Data Source
The value of this metric is obtained by measuring the response to the Servlet URL shown on the Forms Overview Page.
By default, this metric has a critical threshold of 0 indicating that the Forms Servlet is unreachable. A critical alert is generated when the metric value equals the critical threshold value once. It is advisable that this threshold be left at the default value.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 14-6 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Minute |
After Every 12 Samples |
= |
Not Defined |
0 |
1 |
The Forms instance is not accessible. |
Data Source
The value of this metric is obtained by measuring the availability of the Servlet URL shown on the Forms Overview Page. The current value of this metric can also be seen under Response and Load on the Forms Overview Page.
User Action
Check whether the OC4J_BI_Forms oc4j instance has been started and if so that the application forms90app.ear has been deployed successfully.