Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Enterprise Scheduler
11g Release 1 (11.1.1.7)

Part Number E24712-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

6 Monitoring Oracle Enterprise Scheduler

This chapter describes how you can monitor performance of Oracle Enterprise Scheduler job requests and server instances. You can also get component status and log information.

This chapter includes the following sections:

6.1 Overview of Monitoring Oracle Enterprise Scheduler

Much of the monitoring you'll do is related to job requests, where Oracle Enterprise Scheduler work is done. You can get a snapshot of recent work done as job requests, including the load those requests are placing on the system. You can also view the status of current and pending requests.

For an Oracle Enterprise Scheduler instance, you can find out how it is performing currently and how it has performed historically.

You can get the status of a service instance, as well as service components such as the request dispatcher and processor.

Finally, you can get log information about job requests and Oracle Enterprise Scheduler.

Use Fusion Middleware Control to do most of the monitoring you'll need. It's user interface provides data about system performance in both graphical and tabular form.

6.2 Monitoring Oracle Enterprise Scheduler Request Activity

You can monitor job requests using Oracle Enterprise Manager Fusion Middleware Control Console. On the console's Scheduling Service Home page, you can get the following information:

6.2.1 Viewing Top Ten Long Running Requests and Top Ten Ready Requests

In the Oracle Enterprise Manager Fusion Middleware Control Console, the Oracle Enterprise Scheduler home page displays two important categories of information: data about the top ten long running scheduled jobs and data about the top ten job requests awaiting execution. These are displayed on separate tabs.

By default, only the job requests within the current scheduling service display. However, you can change the scope such that all relevant scheduled jobs running on all scheduling services sharing the Oracle Enterprise Scheduler repository display in the tabs.

Each of the tabs includes a table that displays a short list of job requests. The Show All Ready or Show All Running link at the bottom of the region displays a search page in which it is possible to search for a more comprehensive list of relevant job requests.

Each tab displays the following information about scheduled job requests:

  • Request ID: The ID associated with the job request.

  • Run Time/Wait Time: The period of time during which the job request has been running or awaiting execution, respectively.

  • Job Definition: The job definition associated with the job request.

  • Submitted by: The name of the user who submitted the job request.

  • Application: The name of the application with which the job request is associated.

  • Execution Type: The category of job being executed—Java, SQL or process job.

  • Description: An optional description of the scheduled job request.

This section contains the following topics:

6.2.1.1 Viewing Top Ten Long Running Oracle Enterprise Scheduler Requests

The Top Ten Long Running Requests tab displays the top ten long running scheduled job requests, including request ID, job run time, job definition used, executing application, job execution type and description. You can set the scope of the top ten long running requests displayed to the current scheduling service only, or all scheduling services sharing the Oracle Enterprise Scheduler repository.

Use the Top Ten Long Running Job Requests tab to view the job requests that have been running for the longest period of time on the Oracle Enterprise Scheduler service. You can alternatively change the scope of the region to display the top ten long running job requests on all scheduling services sharing the same repository.

The job requests displayed will all have a status of RUNNING.

To view the top ten long running requests:

  1. From the navigation pane, expand the Scheduling Services folder and select the Oracle Enterprise Scheduler application.

  2. At the top of the Oracle Enterprise Scheduler home page, click the Top 10 Long Running Requests tab to display the ten job requests that have been running the longest.

  3. To display all running job requests, click Show All Running at the bottom of the chart. This displays a search form that searches for all requests that are currently running. Click Search to display the requests.

6.2.1.2 Viewing Top Ten Oracle Enterprise Scheduler Jobs Ready to Be Executed

The Top Ten Ready Job Requests tab displays the top ten scheduled job requests that await execution. The tab displays the same information as the Top Ten Long Running Requests tab, except the wait time displays for each job rather than the run time.

Use the Top Ten Ready Job Requests tab to view the job requests that are awaiting execution on the Oracle Enterprise Scheduler. You can also change the scope of the region to display the top ten ready job requests on all scheduling services sharing the same repository.

The job requests displayed will all have a status of READY.

To view the top ten ready job requests:

  1. From the navigation pane, expand the Scheduling Services folder and select the Oracle Enterprise Scheduler application.

  2. At the top of the Oracle Enterprise Scheduler page, click the Top 10 Ready Requests tab to display the ten job requests with the status READY.

  3. To display all ready job requests, click Show All Ready at the bottom of the chart. This displays a search form that searches for all requests with the status READY. Click Search to display the requests.

6.2.2 Viewing Completed Job Requests

You can view the status of completed job requests on the Scheduling Service home page of the Fusion Middleware Control. There, in the Completed Job Requests region, each completion status is shown as a percentage of the total of job requests completed in the last hour. Status shown includes Success, Warning, Error, and Cancelled.

6.2.3 Viewing Job Request Response and Load

You can view the information about the processing load that has been required to complete job requests on the Scheduling Service home page of the Fusion Middleware Control. In the Response and Load region, you can view performance monitoring statistics regarding the time required to process to job requests.

Table 6-1 describes the performance monitoring statistics in the Response and Load region.

Table 6-1 Response and Load Statistics

Statistic Description

Average Processing time for Last Hour

This metric specifies the average time required to process jobs during the last hour.

Requests Completed Per Hour

This metric specifies the number of scheduled job requests completed within the last hour.


6.2.4 Viewing Performance as Processing and Wait Times

You can view job request processing and wait times on the Scheduling Service home page of the Fusion Middleware Control.

Table 6-2 describes the performance monitoring statistics in the Performance region.

Table 6-2 Performance Statistics

Statistic Description

Maximum Processing Time

The maximum amount of time required to process a scheduled job.

Average Processing Time

The average amount of time required to process a scheduled job.

Maximum Wait Time

The maximum amount of time during which a scheduled job waits before running.

Average Wait Time

The average amount of time during which a scheduled job waits before running.


6.3 Monitoring the Performance of a Single Oracle Enterprise Scheduler Instance

You can monitor the performance of an Oracle Enterprise Scheduler instance, specifically current and historical performance data, as well as a summary of all performance data. Performance data displays in a chart set that you can save, delete, and reorder. You can also modify the time period for which performance data displays.

This section contains the following topics:

6.3.1 Viewing a Summary of Oracle Enterprise Scheduler Activity

The Oracle Enterprise Scheduler Performance Summary page displays current charts of job requests such as requests completed per hour, running requests, requests by processing time and requests by status.

To view a summary of Oracle Enterprise Scheduler activity:

  1. From the Scheduling Service menu, choose Performance > Service Summary.

    By default, this page displays job requests running during a selected time period in the following categories:

    • Requests completed per hour

    • Processing times, average, minimum and maximum

    • Running requests and maximum running requests

    • Requests over the past hour with the status SUCCESS, WARNING, ERROR or CANCEL.

    You can change the metrics displayed on the Service Summary performance page. Click the Show Metric Palette button to display the metric palette for Oracle Enterprise Scheduler.

  2. You can change the duration for which performance data display.

  3. Optionally, you can change the display format of performance data on the page.

    Choose View > Grid to remove the grid display format from the charts.

    Click the Table View link to display the performance data in table format.

  4. You can overlay an additional scheduler service over the current service performance metrics.

    1. Choose Overlay > Another Scheduler Service.

      In the Search and Select: Targets window, enter the name of the target and host server and click Go to search for the relevant service.

    2. From the search results table, select the relevant service and click Select to choose the scheduler service to overlay.

  5. Additionally, you can take any of the following actions.

6.3.2 Viewing Current Oracle Enterprise Scheduler Activity

The Oracle Enterprise Scheduler Current Activity page displays pending and running requests by user and application.

To view current Oracle Enterprise Scheduler activity:

  1. From the Scheduling Service menu, choose Performance > Current Activity.

  2. You can view pending and running requests by user or application, or workload by work assignment.

    To view pending and running requests by user, choose View > Requests By User.

    To view pending and running requests by application, choose View > Requests By Application.

    To view workloads by work assignment, choose View > Workload By Work Assignment. For more information about work assignment details, see Section 5.3.1.1, "Creating or Editing a Work Assignment."

6.3.3 Viewing Historical Oracle Enterprise Scheduler Reports

The Oracle Enterprise Scheduler Historical Reports page displays completed job requests by user, application and work assignment.

To view historical Oracle Enterprise Scheduler reports:

  1. From the Scheduling Service menu, choose Performance > Historical Reports.

  2. From the View list, choose one of the following report views:

    • Completed Request Statistics By Job Name

    • Completed Request Statistics By User

    • Request Metrics By Work Assignment

    • Completed Request Statistics

  3. Adjust the filter criteria as required. The filter criteria vary depending on the report view you choose.

    Table 6-3 Completed Request Statistics by Job Name

    Filter Criterion What to Do...

    Application

    From the list, choose the application whose statistics you want to view.

    Minimum Run Time

    Enter the shortest run time period for jobs whose statistics you want to view. Use the text field to enter a number, and select a unit of time from the list: Seconds, Minutes, Hours or Days.

    Completed between

    Use the calendar icons on either side of the text fields to select a start and end date and time.


    Table 6-4 Completed Request Statistics by User

    Filter Criterion What to Do...

    Application

    From the list, choose the application whose statistics you want to view.

    Minimum Total Run Time

    Enter the shortest total time period for jobs whose statistics you want to view. Use the text field to enter a number, and select a unit of time from the list: Seconds, Minutes, Hours or Days.

    Completed between

    Use the calendar icons on either side of the text fields to select a start and end date and time.


    Table 6-5 Request Metrics By Work Assignment

    Filter Criterion What to Do...

    Application

    From the list, choose the application whose statistics you want to view.

    Completed after

    Use the calendar icon to choose the date and time after which the work assignment has completed.


    Table 6-6 Completed Request Statistics

    Filter Criterion What to Do...

    Application

    From the list, choose the application whose statistics you want to view.

    Completed between

    Use the calendar icons on either side of the text fields to choose a start and end date and time.


  4. Click Go to search for and display the historical data.

6.3.4 Managing Chart Sets

You can save or delete the chart set displayed in the Oracle Enterprise Scheduler Performance Summary page. You can also re-organize the order of a chart and revert to an old chart set.

This section contains the following topics:

6.3.4.1 Saving a Chart Set

You can save the chart set displayed in the Oracle Enterprise Scheduler Performance Summary page. Saving a chart set allows preserving a specific set of metrics selected for display, as opposed to the default metrics.

To save a chart set:

  1. Display the Oracle Enterprise Scheduler Performance Summary page.

  2. Choose View > Save Chart Set.

  3. In the Save Chart Set dialog box, enter a name for the chart set and click OK.

  4. Once you have saved the chart set, you can display it by choosing Chart Set > My Chart Set.

6.3.4.2 Deleting a Chart Set

You can delete saved chart set files created in the Oracle Enterprise Scheduler Performance Summary page.

To delete a chart set:

  1. Display the Oracle Enterprise Scheduler Performance Summary page.

  2. Choose View > Delete Chart Sets.

  3. In the Delete Chart Sets dialog box, select the name of the chart set to be deleted and click OK.

6.3.4.3 Reordering Charts

You can organize the display of performance charts in the Oracle Enterprise Scheduler Performance Summary page. Charts can be moved up or down, or removed entirely.

To reorder chart sets:

  1. Display the Oracle Enterprise Scheduler Performance Summary page.

  2. Choose View > Reorder Charts.

  3. In the Reorder Charts popup window, select the chart you want to move and click Move Up or Move Down, respectively.

    To delete a chart from the Performance Summary page, select the chart and click Delete.

  4. Click OK.

6.3.4.4 Reverting to an Old Chart Set

If you have re-organized your chart sets, you can revert to the chart set as you had originally saved it.

To revert chart sets:

  1. Display the Oracle Enterprise Scheduler Performance Summary page.

  2. From the Chart Set list, choose the chart you want to revert to its original display.

  3. Choose View > Revert Chart Set.

6.3.5 Selecting the Performance Time Period

In the Oracle Enterprise Scheduler Performance Summary page, you can change the time period for which the performance summary displays.

To select the performance time period:

  1. Display the Oracle Enterprise Scheduler Performance Summary page.

  2. Change the duration for which job requests display.

    • All: Click to display all job requests within a specified, finite period.

    • 15 minutes: Click to display all job requests within the past fifteen minutes.

    • Slider: Click to display a slider that enables scrolling horizontally to show job requests from a specified period. The slider defaults to whichever time segment is selected, "all," 2 hours, or 15 minutes.

    • Calendar: Click the calendar icon to select a time period for which you want to display job requests.

6.4 Monitoring Key Performance Metrics for Oracle Enterprise Scheduler

Use Table 6-7 to locate the key performance metrics for Oracle Enterprise Scheduler.

Table 6-7 Oracle Enterprise Scheduler Key Performance Metrics

Metric Name Location in Fusion Middleware Control

Number of active processor threads for each instance

  1. From the navigation pane, expand Scheduling Services.

  2. Select the Oracle Enterprise Scheduler component.

  3. From the Scheduling Service menu, choose Performance > Current Activity.

  4. From the View list, choose Workload by Work Assignment.

  5. In the Work Assignments with active Workshifts report, view the Thread Allocation columns.

Processing Time (for jobs)

Wait Time

  1. From the navigation pane, expand Scheduling Services.

  2. Select the Oracle Enterprise Scheduler component.

  3. From the Scheduling Service menu, choose Performance > Historical Reports.

  4. In the Historical Reports page, from the View list, choose Request Metrics By Work Assignment.

  5. In the Results section, view the Wait Time and Processing Time columns.

Job running time

  1. From the navigation pane, expand Scheduling Services.

  2. Select the Oracle Enterprise Scheduler component.

  3. From the Scheduling Service home page, in the Top 10 Long Running Request tab, select a job.

  4. In the Request Detail page, under Execution Trail, view the Run Time metric.


6.5 Viewing General Oracle Enterprise Scheduler Instance Information

You can view information about a particular Oracle Enterprise Scheduler instance by using the Scheduling Service General Information popup window in Fusion Middleware Control. The popup window displays the locations of Oracle Fusion Middleware home, the domain and the target application, as well as the version of Oracle Fusion Middleware currently running and the URI of the hosting server.

To view general information about Oracle Enterprise Scheduler:

  1. From the Scheduling Service menu, select one of the following:

    • From the Scheduling Service menu, select General Information.

    • In Cloud Control, from the Scheduling Service menu, select Target Information.

  2. Fusion Middleware Control displays the following information.

    • Target Name: The location of the target application, in this case, Oracle Enterprise Scheduler, running on the domain.

    • Version: The version number of Oracle Fusion Middleware.

    • Middleware Home: The location of the Oracle Fusion Middleware directory.

    • Domain Home: The full path of the domain.

    • Host: The URI of the hosting server.

6.6 Viewing Scheduler Component Status

You can view status for components of Oracle Enterprise Scheduler. On the Scheduling Service home page of Fusion Middleware Control, the Scheduler Components region displays status for the job request processor and dispatcher. The region displays the status (such as whether it's started or stopped) of each component, the name of the server to which it is deployed, and whether or not the component is enabled. You can start and stop each component there.

6.7 Managing Logging for Oracle Enterprise Scheduler

You can search for and view log data for individual job requests, as well as set log levels for Oracle Enterprise Scheduler. You can also save job request logs to a file, and trace job requests for additional troubleshooting information.

This section contains the following topics:

Note:

The Oracle WebLogic Server logger (logging.xml) only shows logs written by Oracle Enterprise Scheduler job running in Oracle WebLogic Server. Once Oracle Enterprise Scheduler transfers control of running PL/SQL to the PL/SQL process, PL/SQL job logging data is not written to the Oracle Enterprise Scheduler logs as they run in a separate process.

6.7.1 Viewing Log Information for the Domain

You can use the Fusion Middleware Control to view log messages for the domain on which Oracle Enterprise Scheduler is deployed.

To view domain logs:

  • From the Scheduling Service menu, select Logs > View Log Messages.

For more information, see the Oracle Fusion Middleware Administrator's Guide.

6.7.2 Viewing Job Request Logs

You can view the log for a particular job request from the Request Details pane.

Note:

On Windows, request log output is formatted as a single line without line breaks.

To view job request logs:

  1. Search for the relevant job requests as described in Section 4.2.2.1

  2. In the table displaying the job request search results, select the job request whose log you want to view.

  3. To view job request details, click the job request ID. Alternatively, click the parent ID associated with the job request to view the details of the job set with which the job is associated.

  4. In the job request details page, select Action and then select Request Log to display log information for the job request.

6.7.3 Viewing Log Messages for Scheduled Job Requests

You can use the Oracle Enterprise Scheduler log messages page to view logging information regarding scheduled job requests.

To view log messages for scheduled job requests with Fusion Middleware Control:

  1. From the navigation pane, expand the farm, and then Scheduling Services.

  2. Select the ESSAPP application for the appropriate Managed Server.

  3. In the Scheduling Service home page, from the Scheduling Service menu, choose Logs and then select View Log Messages.

  4. Search for the relevant log messages using the Date Range, Message Types and Message fields. You can optionally add additional search fields.

  5. You can use the ECID to retrieve more information about a given job request. The Execution Context ID (ECID) is a global unique identifier of the execution of a particular request in which the originating component participates. You can use the ECID to correlate error messages from different components

  6. By default, when view the logs for a request, Fusion Middleware Control displays only messages logged in the scope of the Oracle Enterprise Scheduler cluster. If the Oracle Enterprise Scheduler application is not deployed to a cluster, Fusion Middleware Control displays the messages logged in the managed server scope. However, Oracle Enterprise Scheduler propagates the ECID associated with the job request across sub-systems such as SOA, ADF, and so on.

    To view messages logged by other sub-systems, broaden the target scope to display messages logged across the domain or farm. Click Broaden Target Scope and select the target whose log messages you want to view.

6.7.4 Setting Oracle Enterprise Scheduler Log Levels

It is possible to configure Oracle Enterprise Scheduler server logging for a Oracle WebLogic Server by modifying the logging.xml file of that Oracle WebLogic Server. By default, there is no explicit logger entry for Oracle Enterprise Scheduler. Oracle Enterprise Scheduler inherits the logging level and log handlers configured for the parent logger, typically the oracle logger or the root logger.

By default, the log messages for the Oracle Enterprise Scheduler logger can be found in the Oracle WebLogic Server diagnostic log file for that Oracle WebLogic Server. The logging.xml file is located under DOMAIN_HOME/config/fmwconfig/servers/WebLogic_Server_Name, where DOMAIN_HOME is the domain home directory for the Oracle WebLogic Server domain and WebLogic_Server_Name is the name of the Oracle WebLogic Server that uses the logging.xml file.

Table 6-8 shows the Oracle Enterprise Scheduler logger names, log levels and a description for each level.

Table 6-8 Loggers and log levels for Oracle Enterprise Scheduler

Logger Name Log Level Description

oracle.as.ess

SEVERE

Problems encountered by Oracle Enterprise Scheduler runtime in the context of request processing that result in the request errors. Errors include exceptions thrown by the job code, unchecked exceptions when running the job code and exceptions when running Oracle Enterprise Scheduler code.

Problems encountered by Oracle Enterprise Scheduler runtime outside the context of request processing, such as dispatching, system event handling, and so on.

 

WARNING

Less severe problems encountered by Oracle Enterprise Scheduler runtime during or outside of request processing, which might not cause requests to enter error state.

 

INFO

Messages for request state transitions.

Messages related to work assignment activities.

Messages about batch delete failures.

Start and stop of Oracle Enterprise Scheduler resource adapter.

 

CONFIG

Application endpoint activation and de-activation for Oracle Enterprise Scheduler resource adapter.


  • Request Logging: Oracle Enterprise Scheduler job implementation might write business-specific job request execution log information to the job request log file. This log file is specific to each request, and is automatically enabled by default. For more information about viewing the log file for a job request, see Section 6.7.2.

For information about setting the log levels for Oracle WebLogic Server, see Section 6.7.5.

Set the log levels for the Oracle WebLogic Server running Oracle Enterprise Scheduler as described in the Oracle WebLogic Server documentation.

6.7.5 Tracing Oracle Enterprise Scheduler Jobs

Enabling tracing for Oracle Enterprise Scheduler jobs provides additional information regarding job requests, which can then be relayed to Oracle technical support to help solve any Oracle Enterprise Scheduler-related issues.

This section contains the following topics:

Before You Begin

Before enabling tracing, note that tracing log messages may produce a considerable amount of output. By default, traces go to the Oracle WebLogic Server console stdout. If the stdout is re-directed to a file, it may occupy a significant amount of disk space and possibly affect server performance.

To enable tracing for Oracle Enterprise Scheduler jobs:

Task 1   Navigate to the Specify Loggers Region

Navigate to the Log Configuration pane and expand the Specify Loggers region.

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.

  2. Click the WebLogic Server menu and select Logs and then select Log Configuration.

    The Log Configuration pane displays.

  3. In the Log Levels tab, from the View dropdown list select Loggers with Persistent Log Level State. Expand the Specify Loggers region toward the bottom of the pane.

Task 2   Define the Loggers

Create the following loggers: oracle.as.scheduler.security.internal.SecurityExecutorFactory and oracle.as.scheduler.security.internal.SecurityHelper.

  1. In the Name text field, enter the name of the logger.

  2. From the Oracle Diagnostic Logging Level (Java Level) dropdown list, select the desired logging level.

  3. Repeat for the second logger name.

Task 3   Attach the Loggers

Attach the loggers to the Oracle Diagnostic Logging Handler.

  1. In the Log Configuration pane, click the Log Files tab.

  2. From the list of handlers, select odl-handler and click Edit Configuration.

  3. From the Loggers to Associate dropdown list, select the loggers you created and click OK.

Task 4   Download the Trace File

Download the trace file.

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.

  2. Click the WebLogic Server menu and select Logs and then select View Log Messages.

    The Log Messages pane displays.

  3. In the Search field, expand the Selected Targets region and select the relevant Oracle Enterprise Scheduler target.

  4. Select the relevant date range, message type and so on, and click Search.

  5. From the list of log messages that displays, select the relevant message.

  6. In the Log File column, click the name of the log file.

    The View Log File pane displays.

  7. Next to the name of the log file, click Download to download the file.

6.7.6 Saving Job Request Logs

It is possible to save job request log data to the server log file. Job request logs are normally stored to Oracle WebCenter Content. However, when setting the log level to FINER, all job request logs are copied to the server log file.

To save job request logs to the server diagnostic file:

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.

  2. Click the WebLogic Server menu and select Logs and then select Log Configuration.

    The Log Configuration pane displays.

  3. In the Log Configuration pane, click the Log Levels tab.

  4. In the Search text field, search for oracle.as.scheduler. and find the oracle.as.scheduler.security.internal.SecurityExecutorFactory logger.

  5. Set the log level to FINER and click Apply.

  6. Run a diagnostic test, as described in Oracle Fusion Middleware Administrator's Guide. The log messages are now saved to the <server>-diagnostic.log file.

    The logs are saved to the server diagnostic file, <Oracle Enterprise Scheduler server name>-diagnostic.log.

6.8 Managing Alerts for Oracle Enterprise Scheduler in Cloud Control

Cloud Control enables you to configure, view and manage alerts for Oracle Enterprise Scheduler entities including the scheduling service itself, work assignments and job definitions. Alerts are based on performance metrics for Oracle Enterprise Scheduler. Each metric includes monitored objects with upper and lower thresholds indicating warning or critical states for that particular metric. For example, you can configure an alert on number of job requests that have entered a state of error, such that 10 errors constitute a warning state, and 20 errors a critical state.

Once you have configured alerts, alerts will be generated automatically and its details can be viewed from Incident Manager provided in Cloud Control. Any changes to configuration made within a specified period of time can also be tracked as described in Section 3.5, "Searching for Configuration Changes to Oracle Enterprise Scheduler in Cloud Control".

Table 6-9 lists the alerts available for Oracle Enterprise Scheduler.

Table 6-9 Oracle Enterprise Scheduler Alerts

Alert Scope Collected Data Alert Automatically Cleared?

Alert for job requests in ready state and the average wait time for job requests in ready state.

Work assignment

The number of job requests in ready state and average wait time of the ready job requests by work assignment.

No. The alert is only cleared when the number of ready job requests is smaller than the threshold. The same is true for alerts pertaining to the average wait time of a ready job request.

Alert for job requests that have entered a state of error.

Work assignment

The number of job requests that have entered an error state following the last collection.

Yes. The alert is automatically cleared if the delta value of the subsequent collection is below the threshold.

Alert for long running job requests.

Job definition

The longest running time of a job request listed by job definition. The data is queried for only those job definitions for which a threshold is specified.

No. The alert is cleared when the long running request transitions to another state.

Alert for job requests that have gone to a state of ERROR_MANUAL_RECOVERY.

Scheduling service

The number of job requests in a state of ERROR_MANUAL_RECOVERY.

No. An administrator must recover the job request in order to clear the alert.

Alert for timed out job requests.

Scheduling service

The number of timed out job requests.

No. An administrator must cancel or recover the job request in order to clear the alert.

Alert for job requests that have gone into ERROR state.

Scheduling service

The number of job requests that have gone into ERROR state during the last hour.

Yes. The alert automatically clears if the delta value in the subsequent collection is below the threshold.

Alert for blocked job requests.

Scheduling service

The number of job requests in BLOCKED state.

No. An administrator must cancel the job request, or the job request must be selected for processing in order to clear the alert.


This section contains the following topics:

6.8.1 Configuring Metric Alerts for Oracle Enterprise Scheduler in Cloud Control

You can configure the thresholds for each object monitored by the metric. For a given metric, you can configure alert rules as follows:

  • Select an object that the metric monitors, such as job requests in an errored state.

  • Configure the values at which the object reaches warning and critical states, including an operator value such as greater than (>) or less than (<).

  • Enter a corrective action to be taken in the event that the alert criteria are fulfilled.

  • Arrange the alert rules in the order you desire.

To configure metric alerts for Oracle Enterprise Scheduler in Cloud Control:

  1. Navigate to the scheduling service.

    1. From the Targets menu, choose Middleware.

    2. Navigate to the Oracle Fusion Middleware farm with Oracle Enterprise Scheduler deployed.

    3. In the Target Navigation pane, expand the Scheduling Services folder.

    4. Click on the Oracle Enterprise Scheduler cluster target or individual Oracle Enterprise Scheduler target.

  2. From the Scheduling Service Targets menu, select Monitoring and then click Metric and Collection Settings.

    A list of metrics displays.

  3. Select All metrics from the View dropdown to view all metrics.

  4. Select the metric for which you want to configure alert thresholds and click the Edit icon. For example, you can configure the thresholds for the Average Wait Time for Requests in Ready State (in seconds) metric.

    The Edit Advanced Settings page displays, including the Monitored Objects list.

  5. In the Edit Advanced Settings page, click Add to add a row to the list of monitored objects.

  6. Select the object you want to monitor.

    1. In the Name field of the new row, click the Search button.

      The Search and Select Objects window displays.

    2. Search for the object you want to use and click Select.

  7. In the spaces provided, enter the values to be used for the Critical and Warning thresholds.

  8. Click Continue, then click OK to save your settings.

  9. Configure any additional thresholds as required.

For more information about configuring alerts, see the following topics in the Cloud Control online help:

  • "Incident Rules—Common Tasks"

  • "Incident Rules—Advanced Tasks"

6.8.2 Viewing Alerts for Oracle Enterprise Scheduler in Cloud Control

The Oracle Enterprise Scheduler Service home page displays a summary of alerts. You can navigate to the Incident Manager page to view additional information about incidents by clicking the number of incidents displayed in the Monitoring and Diagnostics area.

To view alerts for Oracle Enterprise Scheduler with Cloud Control:

  1. Navigate to the scheduling service.

    1. From the Targets menu, choose Middleware.

    2. Navigate to the Oracle Fusion Middleware farm with Oracle Enterprise Scheduler deployed.

    3. In the Target Navigation pane, expand the Scheduling Services folder.

    4. Click on the Oracle Enterprise Scheduler cluster target or individual Oracle Enterprise Scheduler target.

  2. The Scheduling Service home page displays. The Monitoring and Diagnostics pane displays the following information.

    • Incidents: The number of incidents that have occurred in the scheduling service instance displays here. The number of incidents is determined by those incidents collected as a result of configuring job request alerts. For more information about configuring job request alerts, see Section 6.8.1. If the number of incidents is greater than zero, click the number for more information about the incidents that have occurred.

    • Descendant Target Incidents: The number of incidents that have occurred anywhere in the scheduling service cluster displays here. If the number of incidents is greater than zero, click the number for more information about the incidents that have occurred.

    • Configuration Changes: The number of changes that have been made to alert configurations displays here. Click the number of configuration changes to search for the changes made within a particular period of time. The default time period is seven days.

  3. Click the number of incidents to display detailed information about the alerts in the Incident Manager pane. If there are no incidents, the Incident manager can be opened from the Scheduling Service target menu by selecting Monitoring and then clicking Incident Manager.

    Description of schedule_ess_incident_mng.png follows
    Description of the illustration schedule_ess_incident_mng.png

    The Incident Manager displays incidents in a table, with the following information listed for each incident: severity, summary, target, priority, status, last updated, owner, acknowledged, escalated, type and category.

    You can click an incident to display its details. For more information about using Incident Manager, see the following topics in the Cloud Control online help:

    • "Incident Manager—Common Tasks"

    • "Incident Manager—Advanced Tasks"

6.9 Auditing Administrative Actions

You can have administrative actions recorded for later review. With this record, you can audit administrative steps when needed. Auditing provides a measure of accountability and answers the "who has done what and when" types of questions.

Auditing support is built into Oracle Enterprise Scheduler. To learn more about how auditing works generally, see the Application Security Guide.

You can configure auditing support by using WLST commands. For more information, see WebLogic Scripting Tool Command Reference.

For reference information about commands supported by Oracle Enterprise Scheduler, see Appendix C, "Audit Reference for Oracle Enterprise Scheduler".

This section includes the following:

6.9.1 Getting the List of Auditable Events

You can get the full list of auditable events from the WLST command line. After using the connect command to connect WLST to the server instance, use the listAuditEvents command to display the list of events. In the command, specify "ESS" as the component type to list supported event types for Oracle Enterprise Scheduler:

listAuditEvents(componentType="ESS")

This and other useful commands are described in WebLogic Scripting Tool Command Reference.

Table 6-10 includes a partial described list of event categories and the auditable events available in them. Be sure to use the listAuditEvents command for a full list.

Table 6-10 Oracle Enterprise Scheduler Audit Event Categories

Category Description

Security Check

Includes events related to security checks, including checking data security privileges, checking metadata permission, checking runtime permission, switching user context, and querying requests based on a data security check.

Operations to Requests

Includes request events related to requests, including executing, deleting, cancelling, holding, locking, purging, releasing, replacing, submitting, and updating.

Metadata Configuration

Includes metadata events such as creating, deleting, and updating schedules, triggers, incompatibilities, exclusions, job definitions and job sets.

Configuration Change

Includes events such as adding, deleting, and updating ESS configuration properties.

Administrative Operations to RequestProcessor

Includes events such as enabling and disabling the request processor.

Administrative Operations to RequestDispatcher

Includes events such as starting and stopping the request dispatcher.


6.9.2 Specifying Which Events Get Logged

You can use WLST to specify filter present level for audit event logging, and so specify which events are logged. You do this by setting the filter preset level to one of three levels: low, medium, or high.

You can set the filter preset level by using the following WLST command:

setAuditPolicy(componentType='ESS', filterPreset="Medium")

Table 6-11 describes the filter preset levels:

Table 6-11 FilterPreset Levels for Event Auditing

Level Description

low

The fewest and more important events will be logged. These include the following:

  • Submit and Execute events from the Operations to Requests category.

medium

A medium level for events between the fewest and most verbose settings. This includes all events from the following categories:

  • Operations to Requests

  • Metadata Configuration

  • Configuration Change

  • Administrative Operations to RequestProcessor

  • Administrative Operations to RequestDispatcher

high

The most verbose level, including all events from the following categories:

  • Security Check

  • Operations to Requests

  • Metadata Configuration

  • Configuration Change

  • Administrative Operations to RequestProcessor

  • Administrative Operations to RequestDispatcher


For more on the event categories, see Section 6.9.1, "Getting the List of Auditable Events".

6.9.3 Viewing Event Audit Data

Data generated by event auditing is stored either in a database or a file, depending on how auditing is configured.

For more on configuring auditing, see the Application Security Guide..

If data is being written to a file, the file's default location will be the following:

DOMAIN_HOME/servers/SERVER_NAME/logs/auditlog