The Concurrent Processing Dashboard

Introduction

The Concurrent Processing Dashboard provides you with details in concurrent processing in your Oracle E-Business Suite system. The dashboard gives you a complete picture of concurrent processing on your system, both current activities as well as usage statistics.

The Concurrent Processing Dashboard is available from the Performance tab of the main page for an Oracle E-Business Suite instance, under Concurrent Processing.

You can add a user-defined concurrent program as a target to the Oracle E-Business Suite composite target. You can then monitor related activities of the registered individual concurrent programs for your own specified thresholds.

You can also add a user-defined concurrent manager as a target to the Oracle E-Business Suite composite target. You can then monitor related activities of the registered individual concurrent managers for your own specified thresholds.

In addition to the features described in this chapter, links are provided under Related Links for the following Oracle Application Manager features:

Overview Tab

the picture is described in the document text

The General region lists the status of the Concurrent Processing Service

The Hourly Completed Requests region shows a pie chart for requests by status (Successful, Warning, and Errored).

The Activity Summary graph illustrates active requests in the following statuses

The Components region lists components of the Concurrent Processing service. The table shows the following for each component:

The Incidents region lists any incidents that were triggered recently, with the following information for each:

At the bottom of the dashboard are Related Links:

The first three links provide metrics on requests and processes:

The last three links take you to Oracle Applications Manager pages for the Oracle E-Business Suite instance:

Current Activity Tab

the picture is described in the document text

The Concurrent Requests by Status region lists the number of requests for each status:

Click on the number for a status to find out more about the metric trend.

The Hourly Completed Requests region lists statistics for requests that have completed in the past hour, including:

Click on the number for each statistic to find out more details.

The Concurrent Managers by Requests lists all concurrent managers, in order of the number of requests it has in the specified status, either Running or Pending.

With "Running" selected, the following is shown for each concurrent manager:

With "Pending" selected, the following is shown for each concurrent manager:

The Top Concurrent Requests region shows the top ten (10) requests for the specified status of Running, Pending, or Scheduled.

The Top Applications region lists the top ten (10) applications for running requests or pending requests, as specified.

The Top Users region lists the top ten (10) users by number of running or pending requests, as specified.

Usage Tab

the picture is described in the document text

This tab provides a summary of how the concurrent programs and managers have been utilized over a period of time.

The top ten (10) concurrent requests for the following categories are listed:

the picture is described in the document text

The top ten (10) applications for the following categories are listed:

The top ten (10) users by total number of requests are also listed, in descending order of number of requests.

User-Defined Targets Tab

the picture is described in the document text

You can add concurrent managers and programs as targets to monitor. Use this tab to get details about these targets as well as add more custom targets.

Concurrent Programs

For custom concurrent program targets, the following columns are shown:

Click on "Show" in the Details column to see the following metrics for the given concurrent program target. (More details can be seen from the Target home page > All Metrics):

Use the Add button under Concurrent Programs to add a new program target.

Concurrent Managers

For concurrent manager targets, the following columns are shown:

Click on "Show" in the Details column to see the following for the given concurrent manager target:

Use the Add button under Concurrent Managers to add a new manager target.

Adding a Concurrent Program Target

You can add a concurrent program custom target so that the system will collect metrics on activity and usage for the concurrent program.

Note: You cannot add a custom concurrent program target using Internet Explorer 8. Please use a different version, or different browser such as Mozilla Firefox.

  1. To add a concurrent program custom target, navigate to the Concurrent Processing Dashboard, User Defined Targets tab, and click Add under Concurrent Programs.

    the picture is described in the document text

  2. For your new target, define the following:

    • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated.

    • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field.

    • Target Type - The system automatically provides the value "Custom Oracle Concurrent Program".

    • Concurrent Program Short Name - Use the LOV icon to search for and select the program short name. In searching for the program name you can search by concurrent program short name, concurrent program name, or application.

    • Monitoring Host

    For the Basic Properties region, values for the following should default in. These values are used as credentials by the target for metrics collection:

    • SID

    • Machine

    • Port

    • (Database) User name

    • (Database) Password

    • ConnectString

  3. For metrics collection, you need to define the thresholds for several metrics. Define instance parameters that will be used to categorize requests for the following:

    A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes".

    A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.1*"Long Running Tolerance Percentage")*Average Running Time of the Concurrent Program.

  4. When you are done, click Add to add the target.

Custom Concurrent Program Target Metrics

Once you have added a custom concurrent program target, you can monitor it. It should be listed on the User Defined Targets tab. Click on its name link to view details.

the picture is described in the document text

Click on the Show link under Details for links to drill down on the following:

From here, you can access the metrics collected for this target by navigating to Target menu > Monitoring > All Metrics. The collected metrics are listed below.

Metrics Collected

The following metrics are collected:

Basic Information

This page lists metrics for the following:

Concurrent Requests by Status

The numbers for requests in each status below are listed.

Hourly Completed Requests

Long Pending Requests

Long Running Requests

Pending Requests

Requests Completed with Error

Requests Completed with Warning

Running Requests

Adding a Concurrent Manager Target

You can add a concurrent manager custom target so that the system will collect metrics on activity and usage for requests run by the concurrent manager.

  1. To add a concurrent manager custom target, navigate to the Concurrent Processing Dashboard > User Defined Targets tab, and click Add under Concurrent Manager.

    the picture is described in the document text

  2. For your new target, define the following:

    • Target Name Prefix - This value is determined by the system based on the instance name and cannot be updated.

    • Target Name - Enter in a target name "suffix". The actual target name will be composed of the Target Name Prefix (above) and the value of this field.

    • Target Type - The system automatically provides the value "Custom Oracle Concurrent Manager".

    • Concurrent Manager Short Name - Use the LOV icon to search for and select the concurrent manager short name. In searching for the manager name you can search by concurrent manager short name, concurrent manager name, or application.

    • Monitoring Host

    For the Basic Properties region, values for the following should default in. These values are used as credentials by the target for metrics collection:

    • SID

    • Machine

    • Port

    • (Database) User name

    • (Database) Password

    • ConnectString

  3. For metrics collection, you need to specify values for three Instance Properties that will be used to categorize requests for the following:

    A request will be termed Long Pending if it is in Pending status for longer than the "Long Pending Request Threshold In Minutes".

    A request will be considered Long Running if it runs for longer than the "Long Running Request Threshold In Minutes" and (1+0.1*"Long Running Tolerance Percentage")*Average Running Time of the Concurrent Program.

    You can also change these properties by clicking the "Monitoring Configuration" link on the Target Home page.

  4. When you are done, click Add to add the target.

Monitoring a Custom Concurrent Manager Target

Once you have added a custom concurrent manager target, you can monitor for it. It should be listed on the User Defined Targets tab. Click on its name link to view details.

the picture is described in the document text

From here, you can also monitor the metrics for this target by navigating to Target menu > Monitoring > All Metrics.

Active Processes

Pending Requests

Running Requests

Concurrent Processing Metrics

the picture is described in the document text

This section lists the concurrent processing metrics available from the All Metrics page. Navigate to the All Metrics page by selecting Target menu > Monitoring > All Metrics.

For each type of metric below, the details listed for each record are shown.

Active Concurrent Requests by Application

Applications by Errored Executions

Applications by Executions

Applications by Pending Requests

Applications by Running Requests

Programs by Average Running Time

Programs by Errored Executions

Programs by Executions

Programs by Total Running Time

Top Pending Requests

Top Running Requests

Top Scheduled Requests

Top Users (Requests Submitted)

Users by Pending Requests

Users by Running Requests

Setting Long Running and Long Pending Requests Parameters for Metrics and Incidents

Oracle Application Management Pack for Oracle E-Business Suite allows you to define parameters for long running and long pending requests. Follow the procedure below to do so.

  1. From the Concurrent Processing Dashboard, add a custom concurrent program or concurrent manager target.

  2. For the custom target, enter in values for these fields:

    • Long Pending Request Threshold in Minutes

    • Long Running Request Threshold in Minutes

    • Long Running Tolerance Percentage

    The three parameters above are instance parameters for categorizing a request as long running or long pending.

    A request will be considered long pending if it is pending for more than the "Long Pending Threshold in Minutes" value.

    A request will be considered long running if it runs for more than the "Long Running Request Threshold in Minutes" value AND for longer than (1 + 0.01*[Long Running Tolerance Percentage]*[Average Running Time of the Concurrent Program]).

  3. After you have set these parameters, you can go to the All Metrics page to see these categories listed. Navigate to the All Metrics page by navigating to the Target Menu, selecting Monitoring, then selecting All Metrics.

    For Long Pending Requests, the following details are available through drilling down:

    • Request ID

    • Concurrent Program Short Name

    • Concurrent Program Name

    • Request Start Date

    • Username

    • Phase

    • Status

    • Pending Time

    • Concurrent Manager

    For Long Running Requests, the following are available through drilling down:

    • Request ID

    • Concurrent Program Short Name

    • Concurrent Program Name

    • Request Start Date

    • Username

    • Phase

    • Status

    • Running Time

    • Concurrent Manager

    For Long Running and Long Pending Requests, you can drill down to get a count for each.

  4. On the same All Metrics page, click on Metric and Policy Settings to edit the incident threshold for long pending and long running requests. Choose to view "All Metrics" from the View dropdown list and set the incidents count for Long Pending Requests and Long Running Requests.