6 Monitoring Oracle Enterprise Scheduling Service

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 Scheduling Service 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 Scheduling Service 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:

• Viewing Top Ten Long Running Oracle Enterprise Scheduling Service Requests

• Viewing Top Ten Oracle Enterprise Scheduling Service Jobs Ready to Be Executed

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.

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.

6.3.1 Viewing a Summary of Oracle Enterprise Scheduling Service Activity

The Oracle Enterprise Scheduling Service 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 Scheduling Service 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 Scheduling Service.

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.

   • Save the chart set, as described in Section 6.3.4.1, "Saving a Chart Set".

   • Reorder the chart set, as described in Section 6.3.4.3, "Reordering Charts".

   • Revert to an old chart set, as described in Section 6.3.4.4, "Reverting to an Old Chart Set".

   • Delete a chart set, as described in Section 6.3.4.2, "Deleting a Chart Set".

6.3.2 Viewing Current Oracle Enterprise Scheduling Service Activity

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

To view current Oracle Enterprise Scheduling Service 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 Scheduling Service Reports

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

To view historical Oracle Enterprise Scheduling Service 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 Scheduling Service 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:

• Saving a Chart Set

• Deleting a Chart Set

• Reordering Charts

• Reverting to an Old Chart Set

6.3.5 Selecting the Performance Time Period

In the Oracle Enterprise Scheduling Service 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 Scheduling Service 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.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 Scheduling Service 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.

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 Scheduling Service 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 Scheduling Service cluster. If the Oracle Enterprise Scheduling Service application is not deployed to a cluster, Fusion Middleware Control displays the messages logged in the managed server scope. However, Oracle Enterprise Scheduling Service 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 Scheduling Service Log Levels

It is possible to configure Oracle Enterprise Scheduling Service 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 Scheduling Service. Oracle Enterprise Scheduling Service 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 Scheduling Service 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 Scheduling Service logger names, log levels and a description for each level.

• Request Logging: Oracle Enterprise Scheduling Service 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 Scheduling Service as described in the Oracle WebLogic Server documentation.

6.7.5 Tracing Oracle Enterprise Scheduling Service Jobs

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

This section contains the following topics:

• Navigate to the Specify Loggers Region

• Define the Loggers

• Attach the Loggers

• Download the Trace File

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 Scheduling Service 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 Scheduling Service 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 Scheduling Service server name>-diagnostic.log.