| Oracle® Pulse User's Guide Release 19.4 E89716-10 |
|
 Previous |
 Next |
Use the Transactions menu in the navigation menu to see all transactions that are being monitored across your organization's services, as explained in the following sections:
|
Note: The Transactions Dashboard is displayed on the navigation bar only for services where BTM has been enabled.If BTM has not been enabled, the Transactions Dashboard is hidden at the Customer and Service levels. BTM metrics are sourced from Oracle® Enterprise Manager, which, in turn, interrogates the supported Oracle applications. BTM supports Oracle® E-Business Suite and PeopleSoft batch jobs, which are taken from Oracle® E-Business Suite and PeopleSoft. Oracle Pulse can be configured to report on specific targets that Oracle® Enterprise Manager monitors. Your Oracle SDM can work with you to set up and identify your key business transactions for monitoring. The terms batch job and concurrent program are used interchangeably in Oracle Pulse. |
The Transactions menu ( 
) provides information about the performance of your BTM transactions, as well as details about the stability and performance of each of your services or locations.
By default, the reports on the Transactions dashboard are generated in the GMT time zone. However, you can identify potential issues in your own time zone, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse". This allows you to easily relate performance metrics reflected by the reports to anomalies occurring across the selected environment. Moreover, the data in the corresponding exported output is also reported in your preferred time zone.
Where charts are available, you can click the Open Table View icon ( 
) to see the data. You can use the tables on the Transactions dashboard to:
sort records, as explained in the Sorting Records section in Chapter 3, "Working with Oracle Pulse".
export data, as explained in the Exporting Data section in Chapter 3, "Working with Oracle Pulse".
The Transactions dashboard is available at both Customer and Service Level, and can be accessed as explained below:
Use the Transactions menu at Customer Level to see all transactions that are being monitored across your organization's services. To access the Transactions dashboard at Customer Level:
Sign in to Oracle Pulse as explained in the Accessing Oracle Pulse section in Chapter 1, "Introduction".
The Pulse Dashboard is displayed by default.
Click Transactions in the navigation menu.
The Transactions List page opens.
Use the Transactions menu at Service Level to see all transactions that are being monitored for the selected service. To access the Transactions dashboard at Service Level:
Sign in to Oracle Pulse as explained in the Accessing Oracle Pulse section in Chapter 1, "Introduction".
The Pulse Dashboard is displayed by default.
Click the Service Tree View icon ( 
) in the upper left corner and select the service you want to access.
The Availability Dashboard page at Service level opens.
Click Transactions in the navigation menu.
The Transactions page opens.
Alternatively, the Transactions dashboard at Service Level can also be accessed from the Transactions dashboard at Customer Level:
Click the Service Tree View icon ( ) in the upper left corner and select the service you want to access.
OR
Click a service name in the table in the Status tab.
This section describes how to use the Transactions List view, displayed by default when opening the Transactions dashboard at Customer and Service Level, to get a complete list of your transactions, allowing you to determine the BTM transactions that are experiencing a degradation in performance. For each batch job or user interaction record, the Transactions List view shows the transaction and service name, the environment running the job, the status of the latest request for the job, and the performance details. The Transactions List view also shows the response time of the last request for a batch job. The information on the Transactions List view is automatically refreshed every 15 minutes.
For more information about the reports available for each transaction type, see the following sections:
For each Oracle E-Business Suite batch job, the Transactions List view shows the transaction and service name, the Oracle E-Business Suite environment running the job, the status of the latest concurrent request for the batch job, and the performance details for all collected data. The Transactions List view also shows the response time of the last concurrent request for the batch job.
You can open detailed reports of recent and historical concurrent requests at both the individual batch job and batch job system levels, as well as detailed performance profile for each user interaction. For details on how to relate performance metrics reflected by the BTM reports to anomalies occurring across an environment, see Analyzing Oracle E-Business Suite Metrics.
Run By
The Run By column on the Transactions List view tracks the Oracle E-Business Suite environment running the batch job.
Detailed View: Click an Oracle E-Business Suite batch job to open detailed reports of all recent and historical concurrent requests for the corresponding batch job. The reports show concurrent requests in the job system run by the Oracle E-Business Suite environment that runs the batch job. For more information, see Analyzing Oracle E-Business Suite Metrics.
Status
The Status column on the Transactions List view shows the phase and status of the last concurrent request for the monitored batch job in Oracle Applications.
The Status column has the following values:
|
Note: These tables were correct on date of publication. The Concurrent Request Phase and Status section of the Oracle Applications documentation lists the latest definitions. |
| Phase | Status | Description |
|---|---|---|
| PENDING: Request is waiting to be run | Normal | Request is waiting for the next available manager. |
| Standby | Program to run request is incompatible with other program(s) currently running. | |
| Scheduled | Request is scheduled to start at a future time or date. | |
| Waiting | A child request is waiting for its parent request to mark it ready to run. For example, a request in a request set that runs sequentially must wait for a prior request to complete. | |
| RUNNING: Request is running | Normal | Request is running normally. |
| Paused | Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete. | |
| Resuming | All requests submitted by the same parent request have completed running. The parent request resumes running. | |
| Terminating | Request is terminated using the Cancel Request button in Requests window. | |
| COMPLETED: Request has finished | Normal | Request completed successfully. |
| Error | Request failed to complete successfully. | |
| Warning | Request completed with warnings. For example, a request is generated successfully but fails to print. | |
| Canceled | Pending or inactive request is cancelled using the Cancel Request button in the Requests window. | |
| Terminated | Request is terminated using the Cancel Request button in the Requests window | |
| INACTIVE: Request cannot be run | Disabled | Program to run request is not enabled. Contact your system administrator. |
| On Hold | Pending request is placed on hold using the Hold Request button in the Requests window. | |
| No Manager | No manager is defined to run the request. Check with your system administrator.
This status also appears when all managers are locked by run-alone requests. |
Footnote 1 Running requests that do not finish with a Success, Warning or Error status are marked as Completed/Canceled.
Detailed View: Click an Oracle E-Business Suite batch job to open detailed reports of all recent and historical concurrent requests for monitored batch jobs at the job level. For more information, see Analyzing Oracle E-Business Suite Metrics.
Last Response
The Last Response column on the Transactions List view shows the response time recorded when the batch job was last run as a concurrent request, with the date and time when the response was measured:
(Upper) Last response time recorded for the batch job.
(Lower) Date and time when the last response was recorded, in days, hours, minutes and seconds.
Performance
The Performance column on the Transactions List view shows the maximum runtime and the average response time for all collected data:
(Upper) Average response time of all concurrent requests for the batch job for all collected data.
(Lower) Maximum runtime measured from all concurrent requests for the batch job for all collected data.
For each PeopleSoft batch job, the Transactions List view shows the transaction and service name, the PeopleSoft environment running the job, the status of the latest request for the batch job, and the performance details for all collected data. The Transactions List view also shows the response time of the last request for the batch job.
You can open detailed reports of recent and historical requests at both the individual batch job and system batch job levels. For details on how to relate performance metrics reflected by the BTM reports to anomalies occurring across an environment, see Analyzing PeopleSoft Metrics.
Run By
The Run By column on the Transactions List view tracks the PeopleSoft environment running the batch job.
Detailed View: Click any PeopleSoft batch job to open detailed reports of all recent and historical requests for the corresponding batch job. The reports show requests in the job system run by the PeopleSoft environment that runs the batch job. For more information, see Analyzing PeopleSoft Metrics.
Status
The Status column on the Transactions List view shows the distribution and run status of the last request for the monitored batch job in PeopleSoft.
The run status indicates the current state of your process, while the distribution status indicates where the distribution agent resides in the report distribution process. Knowing the status of your job helps you see where it is in the queue or identify a problem if the process has an error.
|
Note: These tables were correct on date of publication. The Viewing the Status of Processes section of the PeopleSoft PeopleTools documentation lists the latest definitions. |
| Run Status | Description |
|---|---|
| Error | The program associated with the process request encountered an error while processing transactions within the program. In this case, delivered programs are coded to update the run status to Error prior to terminating. |
| Initiated | Indicates a Process Scheduler Server has acknowledged the new request. At this time, the Process Scheduler validates all the parameters associated with this request and submits the command line to start the process. |
| Not Successful | The program encountered an error within the transaction. Not Successful is different from Error because the process is marked as restartable. Application Engine is the only delivered process type that is restartable. |
| Processing | The Process Scheduler has successfully initiated the program. A status Processing indicates the program is running. |
| Queued | Status assigned to a new process request. The process request will remain Queued until a Process Scheduler Server has picked up the new request. |
| Success | The job finished successfully. |
| Success with Warning | The job finished successfully but with warnings. |
| Distribution Status | Description |
|---|---|
| Posted | The job result was posted successfully. |
| Posting | The job result is being posted. |
| Scheduled | The job result is scheduled to post. |
| Unable to Post | The job result cannot be posted. |
Detailed View: Click any PeopleSoft batch job to open detailed reports of all recent and historical requests for monitored batch jobs at the job level. For more information, see Analyzing PeopleSoft Metrics.
Last Response
The Last Response column on the Transactions List view shows the response time recorded when the batch job was last run as a request, with the date and time when the response was measured:
(Upper) Last response time recorded for the batch job.
(Lower) Date and time when the last response was recorded, in minutes and seconds.
Performance
The Performance column on the Transactions List view shows the maximum runtime and the average response time for all collected data:
(Upper) Average response time of all requests for the batch job for all collected data.
(Lower) Maximum runtime measured from all requests for the batch job for all collected data.
User interaction records, which show transactions that require action from the user in order to complete, can be accessed only from the Transactions List view. For each user interaction, BTM tracks the Oracle Enterprise Manager beacon running the transaction and the transaction status. BTM also records the last response time of the user interaction, and shows the difference between this response and both the baseline threshold and the 30-day average, as a measure of performance. With a tap you can open a detailed performance profile for each user interaction, charting the transaction's performance with respect to the threshold and other measures. Then flip to the table view to check the underlying metric data.
For each user interaction record, the Transactions List view shows the transaction and service name, the environment running the job, the status of the latest request for the job, and the performance details. BTM also shows the response time of the last request for the user interaction, as well as any alerts related to the transaction. For details on how to relate performance metrics reflected by the BTM reports to anomalies occurring across an environment, see Analyzing User Interaction Metrics.
Alert
The Alert column on the Transactions List view shows the user interaction transactions that require your attention. The 
icon helps you easily identify low performing transactions, while the 
icon highlights transactions undergoing a sustained stress period.
Run By
The Run By column on the Transactions List view shows the name of the Oracle Enterprise Manager beacon that runs the user interaction transaction. An Oracle Enterprise Manager beacon can be installed to one or more sites from which the customer wishes to execute their transaction(s). Running transactions from a specific beacon provides better insight into the user experience from that beacon site.
Status
The Status column on the Transactions List view shows the status of the user interaction transaction, having one of the following values:
Succeeded: The transaction completed successfully.
Completed with Error: The transaction completed with errors.
Failed: The transaction did not complete or failed to start.
Running: The transaction is running.
Unavailable: The transaction is not available to be run.
Last Response
The Last Response column on the Transactions List view shows the response time recorded when the user interaction was last run, at the date and time listed.
(Upper) Response time recorded when the user interaction was last run.
(Lower) Date and time when the last response was recorded, in days, hours, minutes, and seconds.
Detailed View: Click any user interaction record to open a detailed performance profile for the transaction. For more information, see Analyzing User Interaction Metrics.
Performance
The Performance column on the Transactions List view compares the last response time recorded for the user interaction with the baseline threshold, set in Oracle Enterprise Manager, and with the average response time for the interaction:
(Upper) Compares the last response time recorded for the user interaction with the baseline threshold, set in Oracle Enterprise Manager.
(Lower) Compares the last response time recorded for the user interaction with the average response time for the user interaction over the last 90 days.
LTM transactions, which detect application access issues that may arise in relation to infrastructure components, capacity, performance, and access, can be accessed only from the Transactions List view. For each LTM transaction, BTM tracks the Oracle Enterprise Manager beacon running the transaction and the transaction status. BTM also records the last response time of the LTM transaction, and shows the difference between this response and both the baseline threshold and the 30-day average, as a measure of performance. With a tap you can open a detailed performance profile for each LTM transaction, charting the transaction's performance with respect to the threshold and other measures. Then flip to the table view to check the underlying metric data.
For each LTM transaction, the Transactions List view shows the transaction and service name, the environment running the job, the status of the latest request for the job, and the performance details. BTM also shows the response time of the last request for the transaction. For details on how to relate performance metrics reflected by the BTM reports to anomalies occurring across an environment, see Analyzing User Interaction Metrics.
Run By
The Run By column on the Transactions List view shows the name of the Oracle Enterprise Manager beacon that runs the LTM transaction. An Oracle Enterprise Manager beacon can be installed to one or more sites from which the customer wishes to execute their transaction(s). Running transactions from a specific beacon provides better insight into the user experience from that beacon site.
Status
The Status column on the Transactions List view shows the status of the user interaction transaction, having one of the following values:
Succeeded: The transaction completed successfully.
Completed with Error: The transaction completed with errors.
Failed: The transaction did not complete or failed to start.
Running: The transaction is running.
Unavailable: The transaction is not available to be run.
Last Response
The Last Response column on the Transactions List view shows the response time recorded when the LTM transaction was last run, at the date and time listed.
(Upper) Response time recorded when the LTM transaction was last run.
(Lower) Date and time when the last response was recorded, in days, hours, minutes, and seconds.
Detailed View: Click any LTM transaction to open a detailed performance profile for the transaction. For more information, see Analyzing User Interaction Metrics.
Performance
The Performance column on the Transactions List view compares the last response time recorded for the LTM transaction with the baseline threshold, set in Oracle Enterprise Manager, and with the average response time for the transaction:
(Upper) Compares the last response time recorded for the LTM transaction with the baseline threshold, set in Oracle Enterprise Manager.
(Lower) Compares the last response time recorded for the LTM transaction with the average response time for the user interaction over the last 90 days.
For each SOA service, the Transactions List view shows the transaction and service name, the environment running the job, the status of the latest request for the job, and the performance details for all collected data. The Transactions List view also shows the response time of the last request for the job. For details on how to relate performance metrics reflected by the BTM reports to anomalies occurring across an environment, see Analyzing SOA Metrics.
Run By
The Run By column on the Transactions List view shows the SOA environment being reported on.
Detailed View: Click a SOA transaction to open detailed reports covering composite status, tablespace usage, faulted component details, and long running component details. For more information, see Analyzing SOA Metrics.
Status
The Status column on the Transactions List view gives the overall status of the last completed environment of a particular SOA partition.
| Status | Description |
|---|---|
| Faulted | One or more composites within the partition have encountered a fault. |
| Succeeded | All composites within the partition have succeeded. |
Detailed View: Click a SOA transaction to see additional detail about the SOA partition, including a status and performance summary over the last 2 and 24 hours. For more information, see Analyzing SOA Metrics.
Last Response
The Last Response column on the Transactions List view shows the response time recorded when SOA metrics were last collected for composites within a particular partition, with the date and time when the response was measured:
(Upper) Last response time recorded for the SOA metrics.
(Lower) Date and time when the last response was recorded, in minutes and seconds.
Performance
The Performance column on the Transactions List view provides average run time of the composite and the maximum run time of the composite:
(Upper) Average response time of all runs for the composite.
(Lower) Maximum runtime measured from all runs for the composite.
This section describes how to use the filter in the upper right part of the Transactions Status view to analyze stability and performance for each service or location relevant to you, as follows:
Select the User Experience by Location option to see the stability and performance status for each location available for your organization's services which were specifically configured to be monitored by the Oracle Pulse BTM functionality. Click any service stability or performance status indicator to open the Transactions List view at Service Level, filtered by the interactions for that location.
Select the System Status: EBiz Suite option, which is only available for customers running EBS transactions, to see the stability and performance status for each Oracle E-Business Suite concurrent manager and concurrent program (job) that is monitored by Oracle Pulse:
Oracle E-Business Suite concurrent managers are background processes designed to manage concurrent requests and batch processing within Oracle Applications. Note that a concurrent manager is itself a concurrent program.
Oracle E-Business Suite concurrent programs (jobs) are executable files that run simultaneously with other concurrent programs and with online operations, fully utilizing your hardware capacity. Typically, a concurrent program is a long-running, data-intensive task, such as posting a journal or generating a report.
Click any hyperlinked value in the Service column to open the Transactions List view at Service Level.
Select the System Status: PeopleSoft option, which is only available for customers running PeopleSoft transactions, to see your organization's PeopleSoft batch processes (also referred to as batch jobs) that are in need of attention, the state of the processes in order to identify if further investigation is necessary, as well as the request and error history in order to set the current state in a historical context and manage capacity. It shows the stability and performance status for each PeopleSoft process scheduler and job that is monitored by Oracle Pulse:
PeopleSoft process schedulers are centralized tools that enable application developers, system administrators, and application users to manage PeopleSoft batch processes. When an application user submits a request to run a process, the request is entered into a database table that lists all of the requests. Process schedulers read requests from the table and start programs running.
PeopleSoft batch jobs are requests to run batch processes.
Click any hyperlinked value in the Service column to open the Transactions List view at Service Level.
Select the System Status: SOA option to see the overall availability and performance status for each SOA partition monitored by the BTM functionality in Oracle Pulse. Availability is based on the UP/DOWN status of the composites within a partition, while performance is based on the number of faulted composites within a partition.
Click any hyperlinked value in the Service column to open the Transactions List view at Service Level.
The stability and performance status for each of these services and locations is described by means of indicators carrying mouse-over tooltips, as shown below:
Red: This is an issue that requires attention.
Amber: There is a potential issue.
Green: All is as expected.
Grey: This component is not functioning as required – it has not been possible to collect recent performance and stability data from the target component.
Black: This component is under a planned outage.
This section describes how to use the charts on the Transactions List view to analyze Oracle E-Business Suite metrics:
the Analyzing Oracle E-Business Suite Batch Job System Metrics section describes how to use the charts on the Run By tab to analyze Oracle E-Business Suite batch job system metrics.
the Analyzing Oracle E-Business Suite Batch Job Metrics section describes how to use the charts on the Status tab to analyze Oracle E-Business Suite batch job metrics.
This section describes how to use the reports on the Run By tab to analyze Oracle E-Business Suite batch job system metrics. Click any Oracle E-Business Suite batch job transaction record to see detailed metrics for batch jobs at system level, as explained in the following sections:
The Latest Requests subtab shows a breakdown of the statuses assigned to the processes that execute the requests, as well as all the batch job executions in order of execution for the selected environment, as explained in the following sections:
EBS Status Breakdown Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( 
) is displayed by default. Click any EBS batch job transaction record associated with an environment. The Run By tab is displayed by default, showing the Latest Requests subtab, with the EBS Status Breakdown table at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The EBS Status Breakdown table shows a breakdown of the statuses assigned to the processes that execute the requests.
Each record in the EBS Status Breakdown table provides the following information:
Process Name: Specifies the name of each batch process in each process scheduler domain supporting the selected environment.
Status: Specifies the state of the process executing jobs the selected environment. Available options include:
Up
Down
Top Longest Batch Requests Run by <environment name> Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment. The Run By tab is displayed by default. Scroll down the Latest Requests subtab to see the Top Longest Batch Requests Run by <environment name> table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Top Longest Batch Requests Run by <environment name> table shows all the batch job executions in order of execution for the selected environment.
Each record in the Top Longest Batch Requests Run by <environment name> table provides the following information:
Program Name: Specifies the name of the program required to run the concurrent request.
Program Short Name: Specifies the short name of the program required to run the concurrent request.
Request ID: Specifies the concurrent request ID.
Manager Name: Specifies the name of the concurrent manager running the request.
EBS Request Start Date: Specifies the date and time when the concurrent request's start message was received.
Running Time: Specifies for how long the request has been running, in days, hours, minutes, and seconds, as applicable.
Phase: Specifies the Oracle Applications transaction phase. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.
Status: Specifies the Oracle Applications transaction status. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.
Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.
The Historical Requests subtab shows the top concurrent programs for the batch job, listed by runtime, during the period between the specified dates and times. Use the drop-down list in the upper left corner of the page to see only specific batch job programs, as explained in the following sections:
Top Concurrent Programs by Runtime Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Historical Requests. The Top Concurrent Programs by Runtime table is displayed by default. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Top Concurrent Programs by Runtime table shows the batch job programs with the highest runtime, allowing you to easily identify batch jobs with the longest execution time. By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Each record in the Top Concurrent Programs by Runtime table provides the following information:
Program Short Name: Specifies the short name of the program required to run the concurrent request.
Program Name: Specifies the name of the program required to run the concurrent request.
Successful Executions (%): Shows the percentage of concurrent requests that completed successfully - that is, without warnings or errors.
Total Executions: Shows the total number of concurrent requests run for the batch job.
Total Runtime: Shows the total runtime for all concurrent requests run for the batch job.
Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.
Top Concurrent Programs by Count Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Historical Requests and select Top Concurrent Programs by Count from the list. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Top Concurrent Programs by Count table shows the batch jobs with the greatest number of concurrent requests during the report interval. By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Each record in the Top Concurrent Programs by Count table provides the following information:
Program Name: Specifies the name of the program required to run the concurrent request.
Program Short Name: Specifies the short name of the program required to run the concurrent request.
Total Executions: Shows the total number of concurrent requests run for the batch job.
Successful Executions (%): Shows the percentage of concurrent requests that completed successfully.
Errored Executions (%): Shows the percentage of concurrent requests that did not complete successfully.
Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.
This section describes how to use the charts on the Status tab to analyze Oracle E-Business Suite batch job metrics. Click any Oracle E-Business Suite batch job transaction record to see recent and historical status reports for a specific batch job, as explained in the following sections:
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status. The Current View tab is displayed by default, with the Last 1 Hour Status table at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Current View tab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of the runtime of the jobs completed successfully in the last hour.
Each record in the Last 1 Hour Status table provides the following information:
Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.
Inactive No Manager: Shows the number of requests that could not be run in the last hour and for which no concurrent manager has been defined.
Inactive On Hold: Shows the number of pending requests that could not be run in the last hour.
Pending Normal: Shows the number of requests run in the last hour that are waiting for the next available concurrent manager.
Pending Standby: Shows the number of requests run in the last hour for which the required program is incompatible with other program(s) currently running.
Running: Shows the number of requests that have been running in the last hour.
Completed Warnings: Shows the number of requests run in the last hour that completed with warnings.
Completed Errors: Shows the number of requests run in the last hour that failed to complete successfully.
Completed Success: Shows the number of requests run in the last hour that completed successfully.
Total Requests: Shows the total number of requests run in the last hour.
Normal Runtime: Shows the number of requests run in the last hour that completed successfully and whose runtime is below the 75th percentile of the runtime of the jobs completed successfully in the last 31 days.
Above Average Runtime: Shows the number of requests run in the last hour that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the runtime of the jobs completed successfully in the last 31 days.
High Runtime: Shows the number of requests run in the last hour that completed successfully, whose runtime is greater than or equal to the 95th percentile of the runtime of the jobs completed successfully in the last 31 days.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Last 24 Hours subtab. The 24 Hours Summary chart is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Last 24 Hours subtab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of historical runtime.
Chart View: The chart view shows the number of concurrent programs of each status for each hour in the previous 24 hours.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the 24 Hours Summary table view in expanded mode.
Table View: The table view shows the number of concurrent programs of each status for each hour in the previous 24 hours.
Each record in the 24 Hours Summary table provides the following information:
Collection Date: Shows the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.
Inactive No Manager: Shows the number of requests that could not be run in the last 24 hours and for which no concurrent manager has been defined.
Inactive On Hold: Shows the number of pending requests that could not be run in the last 24 hours.
Pending Normal: Shows the number of requests run in the last 24 hours that are waiting for the next available concurrent manager.
Pending Standby: Shows the number of requests run in the last 24 hours for which the required program is incompatible with other program(s) currently running.
Running: Shows the number of requests that have been running in the last 24 hours.
Completed Warnings: Shows the number of requests run in the last 24 hours that completed with warnings.
Completed Errors: Shows the number of requests run in the last 24 hours that failed to complete successfully.
Completed Success: Shows the number of requests run in the last 24 hours that completed successfully.
Total Requests: Shows the total number of requests run in the last 24 hours.
Normal Runtime: Shows the number of requests run in the last 24 hours that completed successfully and whose runtime is below the 75th percentile of the historical runtime.
Above Average Runtime: Shows the number of requests run in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the historical runtime.
High Runtime: Shows the number of requests run in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 95th percentile of the historical runtime.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Last 31 Days subtab. The 31 Days Summary chart is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Last 31 Days subtab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of historical runtime in the previous 31 days.
Chart View: The chart view shows the number of concurrent programs of each status for each of the last 31 days.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the 31 Days Summary table view in expanded mode.
Table View: The table view shows the number of concurrent programs of each status for each of the last 31 days.
Each record in the 31 Days Summary table provides the following information:
Calendar Date: Indicates the date when the requests were run.
Inactive No Manager: Shows the number of requests that could not be run in the last 31 days and for which no concurrent manager has been defined.
Inactive On Hold: Shows the number of pending requests that could not be run in the last 31 days.
Pending Normal: Shows the number of requests run in the last 31 days that are waiting for the next available concurrent manager.
Pending Standby: Shows the number of requests run in the last 31 days for which the required program is incompatible with other program(s) currently running.
Running: Shows the number of requests that have been running in the last 31 days.
Completed Warnings: Shows the number of requests run in the last 31 days that completed with warnings.
Completed Errors: Shows the number of requests run in the last 31 days that failed to complete successfully.
Completed Success: Shows the number of requests run in the last 31 days that completed successfully.
Total Requests: Shows the total number of requests run in the last 31 days.
Normal Runtime: Shows the number of requests run in the last 31 days that completed successfully and whose runtime is below the 75th percentile of the historical runtime.
Above Average Runtime: Shows the number of requests run in the last 31 days that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the historical runtime.
High Runtime: Shows the number of requests run in the last 31 days that completed successfully, whose runtime is greater than or equal to the 95th percentile of the historical runtime.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Historical Request subtab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Historical Request subtab shows the requests that completed with error, the long pending requests, the pending requests, the requests that completed with warning, as well as the requests that completed with success over the 24 hours before the specified date. You can see table data for each of the aforementioned reports using the ALL category, which facilitates comparison across the categories, and may help you determine the conditions under which specific jobs can be more successful.
By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Use the drop-down list in the upper left corner of the page to see only specific requests for the selected batch job:
ALL: Shows all requests that were run over the 24 hours before the specified date. This is the default selection.
Requests Completed with Error: Shows concurrent requests that were completed with error over the 24 hours before the specified date. Oracle recommends that you investigate any errors.
Long Pending Requests: Shows concurrent requests with a long Pending phase over the 24 hours before the specified date.
Pending Requests: Shows concurrent program requests that have been in Pending phase over the 24 hours before the specified date, with any of the associated status values.
Requests Completed with Warning: Shows concurrent program requests that were completed with one or more warnings over the 24 hours before the specified date. Oracle recommends that you investigate any warnings.
Requests Completed Successfully: Shows concurrent program requests that were successfully completed over the 24 hours before the specified date.
Each record in the Historical Request report provides the following information:
Request ID: Specifies the concurrent request identifier.
Request Manager: Indicates the concurrent manager handling the concurrent request. Depending on how the batch job is configured in Oracle Enterprise Manager and Oracle E-Business Suite, this field may be blank.
Requested by User: Specifies the identifier of the user who submitted the concurrent request.
Phase: Specifies the Oracle Applications transaction phase. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.
Status: Specifies the Oracle Applications transaction status. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.
Program Name: Specifies the name of the program required to run the concurrent request.
Program Short Name: Specifies the short name of the program required to run the concurrent request.
EBS Request Start Date: Specifies the date and time when the concurrent request was started.
Execution Time: Specifies the date and time when the concurrent request was run.
This section describes how to use the charts on the Transactions List view to analyze PeopleSoft metrics:
the Analyzing PeopleSoft Batch Job System Metrics section describes how to use the charts on the Run By tab to analyze PeopleSoft batch job system metrics.
the Analyzing PeopleSoft Batch Job Metrics section describes how to use the charts on the Status tab to analyze PeopleSoft batch job metrics.
This section describes how to use the reports on the Run By tab to analyze PeopleSoft batch job system metrics. Click any PeopleSoft batch job transaction record to see detailed metrics for batch jobs at system level, as explained in the following sections:
The Current Status subtab shows the current process status breakdown, the jobs currently in alert state since the last data collection, and the jobs in alert state within the last 7 days, as explained in the following sections:
Process Status Breakdown Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment. The Run By tab is displayed by default, showing the Current Status subtab, with the Process Status Breakdown table at the top. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Process Status Breakdown table provides a list of the processes that execute the requests and their assigned statuses, offering a starting point from where to analyze a batch issue. Each record in the Process Status Breakdown table provides the following information:
Process Name: Specifies the name of each batch process in each process scheduler domain supporting the selected environment.
Domain Name: Specifies the name of the domain of the process scheduler.
Host: Specifies the host where the process is run.
Status: Specifies the state of the process. Available options include:
Up
Down
Jobs in Alert State Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment. The Run By tab is displayed by default. Scroll down the Current Status subtab to see the Jobs in Alert State table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Jobs in Alert State table shows the jobs that have failed, the jobs that have had the InitiatedPendingJobs, InPostingJobs, UnableToPostJobs or QueuedPendingJobs status for more than 30 minutes, or the jobs that are running for more than 10% of the average runtime. Each record in the Jobs in Alert State table provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current run request state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and time when the PeopleSoft batch job started.
End: Specifies the date and time when the PeopleSoft batch job ended.
Running Time (Mins): Specifies the duration required for the PeopleSoft batch job to end, in minutes.
Host: Specifies the host where the PeopleSoft batch job is run.
Transaction ID: Specifies the identification number of the transaction.
Jobs in Alert State History - Last 7 Days Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment. The Run By tab is displayed by default. Scroll down the Current Status subtab to see the Jobs in Alert State History - Last 7 Days table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Jobs in Alert State History - last 7 Days table shows a 7-day history of the Jobs in Alert State report, allowing you to look at the history of the jobs that have failed, the jobs that have had the InitiatedPendingJobs, InPostingJobs, UnableToPostJobs or QueuedPendingJobs status for more than 30 minutes, or the jobs that are running for more than 10% of the average runtime over the last 7 days, and providing historical context to the current report. Each record in the Jobs in Alert State History - last 7 Days table provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current run request state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and time when the PeopleSoft batch job started.
End: Specifies the date and time when the PeopleSoft batch job ended.
Running Time (Mins): Specifies the duration required for the PeopleSoft batch job to end, in minutes.
Host: Specifies the host where the PeopleSoft batch job is run.
Transaction ID: Specifies the identification number of the transaction.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click Process Scheduler. The Process Scheduler table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Process Scheduler subtab shows the jobs that are currently queued in the job system, providing important details on the scheduling processes. Export information on the offending schedulers and send it to concerned parties to gather information about the function of the scheduling processes. This will further allow you to determine whether it is safe to restart the DOWN processes in order to free the resources currently being consumed and to have the system return to normal execution.
Each record in the Process Scheduler table provides the following information:
Scheduler: Indicates the process scheduler for the jobs in the specified environment.
Host: Specifies the host where the PeopleSoft batch job is run.
Status: Specifies the current run request state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Max CPU %: Specifies the current CPU usage as a percentage of the total CPU available.
Disk Space Used (MB): Specifies the amount of disk space used by the Process Scheduler, in megabytes.
Start: Specifies the date and the time when the PeopleSoft batch job started.
Queued Jobs: Specifies the number of jobs that are in line to run by the process scheduler but have not been started yet.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click 24HR Summary. The 24 Hours Summary table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The 24HR Summary subtab shows the number of job requests of various statuses within the last 24 hours, allowing you to determine whether a slowdown in the system performance is related to a certain scheduled process or to a process occuring during regular working hours.
Chart View: The chart view shows the count of each status hour by hour for the last 24 hours.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the 24 Hours Summary table view in expanded mode.
Table View: The table view shows the count of each status hour by hour for the last 24 hours and those that have completed within the median, 75th percentile, and 95th percentile of historical runtime in the last 24 hours.
Each record in the 24 Hours Summary table provides the following information:
Collection Date: Shows the date and time when these metrics were collected from Oracle Enterprise Manager and PeopleSoft.
Error: Shows the number of jobs that encountered an error while processing transactions within the program.
Failed: Shows the number of jobs that failed.
Successful With Warnings: Shows the number of jobs that finished successfully but with warnings.
Pending: Shows the number of jobs that are waiting for the previous item in the PeopleSoft job before being released by the PeopleSoft Process Scheduler.
Initiated Pending: Shows the number of jobs that have been initiated to run and are gathering runtime parameters.
Unposted: Shows the number of jobs for which the Distribution Agent was not able to transfer the reports to the Report Manager.
Processing: Shows the number of jobs that are currently running.
Posted: Shows the number of jobs that finished and were posted.
Success: Shows the number of jobs that completed successfully.
Not Successful: Shows the number of jobs that encountered an error while processing transactions within the program and are marked as restartable.
Total: Shows the total number of jobs run every hour in the last 24 hours.
Normal Runtime: Shows the number of jobs run every hour in the last 24 hours that completed successfully and whose runtime is below the 75th percentile of the historical runtime.
Above Avg. Runtime: Shows the number of jobs run every hour in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the historical runtime.
High Runtime: Shows the number of jobs run every hour in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 95th percentile of the historical runtime.
This section describes how to use the charts on the Transactions dashboard to analyze PeopleSoft batch job metrics. Click any PeopleSoft batch job transaction record to see recent and historical status reports for a specific batch job, as explained in the following sections:
The Request History subtab shows the last 10 runs of a specific job, as well as the runs of each status of a specific job in the last 24 hours and 31 days, as explained in the following sections:
Request Summary - Latest Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click Status. The Request History subtab is displayed by default, with the Request Summary - Latest table at the top. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Request Summary - Latest table shows the last 10 runs of each status of a specific job. Each record in the Request Summary - Latest table provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and time when the PeopleSoft batch job started.
End: Specifies the date and time when the PeopleSoft batch job ended.
Running Time (Min): Specifies the duration required for the PeopleSoft batch job to end, in minutes.
Host: Specifies the host where the PeopleSoft batch job is run.
Request Summary History - Last 24 Hours Chart
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click Status. Scroll down the Request History subtab to see the Request Summary History - Last 24 Hours table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Request Summary History - Last 24 Hours chart shows the runs of each status of a specific job in the last 24 hours.
Chart View: The chart view shows a series for each status hour by hour for the last 24 hours, with the count of jobs and the time based on the start time:
Successful With Warnings: Shows the number of jobs that finished successfully but with warnings.
Pending: Shows the number of jobs that are waiting for the previous item in the PeopleSoft job before being released by the PeopleSoft Process Scheduler.
Not Successful: Shows the number of jobs that encountered an error while processing transactions within the program and are marked as restartable.
Success: Shows the number of jobs that completed successfully.
Initiated Pending: Shows the number of jobs that have been placed in the pending queue.
Unposted: Shows the number of jobs jobs for which the Distribution Agent was not able to transfer the reports to the Report Manager.
Posted: Shows the number of jobs that finished and were posted.
Processing: Shows the number of jobs that are currently running.
Failed: Shows the number of jobs that failed.
Error: Shows the number of jobs that encountered an error while processing transactions within the program.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the Request Summary History - Last 24 Hours table view in expanded mode.
Table View: The table view shows the runs of each status hour by hour for the last 24 hours.
Each record in the Request Summary History - Last 24 Hours report provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and the time when the PeopleSoft batch job started.
End: Specifies the date and the time when the PeopleSoft batch job ended.
Running Time (Min): Specifies the duration required for the PeopleSoft batch job to end, in minutes.
Host: Specifies the host where the PeopleSoft batch job is run.
Request Summary History - Last 31 Days Chart
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click Status. Scroll down the Request History subtab to see the Request Summary History - Last 31 Days table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Request Summary History - Last 31 Days chart shows the runs of each status day by day for the last 31 days, with the count of jobs and the time based on the start time.
Chart View: The chart view shows a series for each status day by day for the last 31 days, with the count of jobs and the time based on the start time:
Successful With Warnings: Shows the number of jobs that finished successfully but with warnings.
Pending: Shows the number of jobs that are waiting for the previous item in the PeopleSoft job before being released by the PeopleSoft Process Scheduler.
Not Successful: Shows the number of jobs that encountered an error while processing transactions within the program and are marked as restartable.
Success: Shows the number of jobs that completed successfully.
Initiated Pending: Shows the number of jobs that have been placed in the pending queue.
Unposted: Shows the number of jobs for which the Distribution Agent was not able to transfer the reports to the Report Manager.
Posted: Shows the number of jobs that finished and were posted.
Processing: Shows the number of jobs that are currently running.
Failed: Shows the number of jobs that failed.
Error: Shows the number of jobs that encountered an error while processing transactions within the program.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the Request Summary History - Last 31 Days table view in expanded mode.
Table View: The table view shows the runs of each status day by day for the last 31 days.
Each record in the Request Summary History - Last 31 Days table provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and the time when the PeopleSoft batch job started.
End: Specifies the date and the time when the PeopleSoft batch job ended.
Running Time (Min): Specifies the duration required for the PeopleSoft batch job to end, in minutes.
Host: Specifies the host where the PeopleSoft batch job is run.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any PSFT batch job transaction record associated with an environment, then click Status and go to the Error History subtab. The Request Summary History table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Error History subtab shows the errors reported on a specific day for a specific job. Each record in the Request Summary History table provides the following information:
Job ID: Specifies the identification number of the PeopleSoft batch job, as available in PeopleSoft.
Status: Specifies the current state of the PeopleSoft batch job. Knowing the status of a job helps you determine where it is in the queue or identify a problem if the process has an error. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Distribution: Specifies the distribution status of the PeopleSoft batch job. For more information, see Analyzing Performance for PeopleSoft Process Schedulers and Jobs.
Name: Specifies the name of the PeopleSoft batch job, as available in PeopleSoft.
Type: Specifies the type of the PeopleSoft job.
User: Specifies the user ID of the person who submitted the PeopleSoft batch job request.
Start: Specifies the date and the time when the PeopleSoft batch job started.
End: Specifies the date and the time when the PeopleSoft batch job ended.
Host: Specifies the host where the PeopleSoft batch job is run.
Log File: Specifies the destination and file name of the log generated by PeopleSoft during execution of the jobs.
This section describes how to use the charts on the Transactions List view to analyze Service-Oriented Architecture (SOA) metrics:
the Analyzing SOA Environment Metrics section describes how to use the charts on the Run By tab to analyze SOA environment metrics.
the Analyzing SOA Partition Metrics section describes how to use the charts on the Status tab to analyze SOA environment metrics.
This section describes how to use the reports on the Run By tab to analyze SOA environment metrics. Click any SOA transaction record to see detailed metrics for SOA environments, as explained in the following sections:
The Composite Status subtab shows information about the status of SOA service targets and of the monitored SOA composites, as explained in the following sections:
Service Status Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment. The Run By tab is displayed by default, showing the Composite Status subtab, with the Service Status table at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Service Status table shows the UP/DOWN status of the following SOA service targets:
weblogic_j2eeserver - The WebLogic server used to run SOA Infrastructure.
weblogic_cluster - A WebLogic Server cluster consists of multiple WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability.
oracle_soainfra - SOA Infrastructure is a Java EE-compliant application running in Oracle WebLogic Server. The application manages composites and their lifecycle, service engines, and binding components.
oracle_soainfra_cluster - A SOA Infrastructure application cluster consists of multiple SOA Infrastructure application instances running simultaneously and working together to provide increased scalability and reliability.
Each record in the Service Status table provides the following information:
Target Name: Specifies the name of the SOA infrastructure target where composites run.
Target Type: Specifies the type of target.
Status: Specifies the status of the target. Available options include:
Target Down
Target Up
Composite Status Table
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment. The Run By tab is displayed by default. Scroll down the Composite Status subtab to see the Composite Status table. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Composite Status table provides a high-level view of the latest status for the SOA composites being monitored.
Each record in the Composite Status table provides the following information:
Partition Name: Specifies the name of the the group the composite target belongs to.
Composite Name: Specifies the name of the composite target.
Last Instantiated Name: Specifies the time when the composite target was last started.
Composite Revision: Specifies the version of the composite target.
Status: Specifies the status of the target. Available options include:
Target Down
Target Up
Total Instance Since Startup: Specifies the total number of times the composite target was run since the SOA server startup.
Asynchronous Response Time (s): Specifies the response time for the composite target's asynchronous operations.
Synchronous Response Time (s): Specifies the response time for the composite target's synchronous operations.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Tablespace Usage. The Tablespace Usage table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Tablespace Usage subtab allows you to monitor SOA storage space growth. This report shows both a chart and a table view for overall tablespace usage and tablespace usage specifically for the FUSION_TS_TOOLS tablespace, the main tablespace for storing SOA metadata and runtime data.
Chart View: The chart view shows a breakdown of the average storage usage by tablespace, in GB.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the Tablespace Usage table view in expanded mode.
Table View: The table view lists all your organization's tablespaces. It displays the name of each tablespace and the average storage used by the tablespace.
Each record in the Tablespace Usage table provides the following information:
Tablespace: Specifies the name of the database tablespace.
Used Storage Avg (GB): Specifies the average amount of space used, in GB.
This section describes how to use the reports on the Status tab to analyze SOA environment metrics. Click any SOA transaction record to see recent and historical status reports for a specific SOA partition, as explained in the following sections:
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Status. The Partition Status subtab is displayed by default, with the Partition Status table at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Partition Status table provides a high-level view of the latest status for each composite within a partition.
Each record in the Partition Status table provides the following information:
Target Name: Specifies the name of the SOA infrastructure target where composites run.
Target Type: Specifies the type of target.
Status: Specifies the status of the target. Available options include:
Target Down
Target Up
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Status and go to the Component Performance Summary Last 2 Hours subtab. The Component Performance Summary Last 2 Hours table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Component Performance Summary Last 2 Hours table provides a high-level summary of the status of each component in the last 2 hours, broken down by partition name, composite name and composite revision.
Each record in the Component Performance Summary Last 2 Hours table provides the following information:
Partition Name: Specifies the name of the group the composite target belongs to.
Composite Name: Specifies the name of the composite target.
Composite Revision: Specifies the version of the composite target.
Component Name: Specifies the name of the component.
Component Type: Specifies the type of the component (BPEL/Mediator).
Avg Response Time (ms): Specifies the average response time of the component, in milliseconds.
Total Faults: Specifies the total number of faults for the component.
Total Instances Last Collection: Specifies the total number of times the component has run since the last time information was collected.
Business Faults: Specifies the total number of business faults for the component, which are caused by a failure to meet a certain business rule.
System Faults: Specifies the total number of system faults for the component, which are caused by errors in the underlying infrastructure or middleware components on which applications run.
Recoverable Faults: Specifies the total number of recoverable faults for the component.
Total Recoverable Faults Since Startup: Specifies the total number of recoverable faults for the component since the SOA server startup.
Avg Response Time (s): Specifies the average response time for the component, in seconds.
Collection Timestamp: Specifies the date and time when the information was collected.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Status and go to the Component Performance Summary Last 24 Hours subtab. The Component Performance Summary Last 24 Hours table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Component Performance Summary Last 24 Hours table provides a high-level summary of the status of each component in the last 24 hours, broken down by partition name, composite name and composite revision.
Each record in the Component Performance Summary Last 24 Hours table provides the following information:
Partition Name: Specifies the name of the group the composite target belongs to.
Composite Name: Specifies the name of the composite target.
Composite Revision: Specifies the version of the composite target.
Component Name: Specifies the name of the component.
Component Type: Specifies the type of the component (BPEL/Mediator).
Avg Response Time (ms): Specifies the average response time of the component, in milliseconds.
Total Faults: Specifies the total number of faults for the component.
Business Faults: Specifies the total number of business faults for the component, which are caused by a failure to meet a certain business rule.
Total Instances Last Collection: Specifies the total number of times the component has run since the last time information was collected.
System Faults: Specifies the total number of system faults for the component, which are caused by errors in the underlying infrastructure or middleware components on which applications run.
Recoverable Faults: Specifies the total number of recoverable faults for the component.
Total Recoverable Faults Since Startup: Specifies the total number of recoverable faults for the component since the SOA server startup.
Avg Response Time (s): Specifies the average response time for the component, in seconds.
Successful Instances Since Startup: Specifies the number of times the composite target ran successfully since the SOA server startup.
Long Running Instances: Specifies the number of instances that have been running for longer than a predefined threshold.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Status and go to the Faulted Components subtab. The Faulted Components table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Faulted Components table allows you to review the current status of processes in SOA domains, and helps with the faster identification of the issue. This table provides details about all the faulted environments, including the error message.
Each record in the Faulted Components table provides the following information:
Partition Name: Specifies the name of the group the composite target belongs to.
Composite Name: Specifies the name of the composite target.
Component Type: Specifies the type of the component (BPEL/Mediator).
Composite Revision: Specifies the version of the composite target.
Component Name: Specifies the name of the component.
Environment: Specifies the name of the related database instance.
Fault Type: Specifies the type of fault that has occured.
Error Message: Specifies the error message associated with the fault.
Collection Timestamp: Specifies the date and time when the information was collected.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any SOA transaction record associated with an environment, then click Status and go to the Long Running Components subtab. The Long Running Components table is displayed at the top of the tab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Long Running Components table allows you to review the current status of processes in SOA domains. This table provides details about all the components running above the normal run time.
Each record in the Long Running Components table provides the following information:
Partition Name: Specifies the name of the group the composite target belongs to.
Composite Name: Specifies the name of the composite target.
Component Type: Specifies the type of the component (BPEL/Mediator).
Composite Revision: Specifies the version of the composite target.
Component Name: Specifies the name of the component.
Last Instantiated Time: Specifies the time when the composite target was last started.
Environment: Specifies the name of the related database instance.
Running Time: Specifies the length of time the component has been running for.
Collection Timestamp: Specifies the date and time when the information was collected.
This section describes how to use the charts on the Transactions List view to analyze the performance of user interaction transactions and the sustained stress periods:
the Current View section describes how to use the charts on the Current View tab to see the performance chart for individual collection points or for all the associated collection points.
the Sustained Stress section describes how to use the charts on the Sustained Stress tab to see an overview of the beacon performance.
This section describes how to use the charts on the Current View tab to analyze the response time for the user interaction over the specified reporting interval for one or more of your collection points. Click any user interaction record to see detailed information about the performance of your collection points, as explained in the following sections:
The performance charts on the Current View tab allow you to determine when the performance issue started, as well as the user zone affected by the issue. The performance threshold and the historical median are included on the chart for reference. The performance threshold is the longest acceptable response time set for the user interaction transaction. You can set the threshold in Oracle Enterprise Manager in consultation with your Oracle SDM. The historical median is the value lying at the midpoint of the range of response times measured.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any user interaction record associated with an environment. The Current View tab is displayed by default, showing the Collection Point subtab. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
The Collection Point subtab shows the performance chart for each individual collection point. Use the drop-down list at the top of the dashboard to select the collection point of your focus.
By default, information on the Collection Point subtab is displayed for the current day. For more information on how to change the time period for your reports, see the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
The chart name uses the following format:
{Location} {Transaction Long Name} {Beacon Name}
where
Location is @Oracle or @Customer.
Transaction Long Name is the long name of the transaction.
Beacon Name is the name of the beacon running the transaction.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the table view in expanded mode, then click the Export icon ( 
) in the upper right corner to export the data, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Depending on the selected time period, different information is available for each record in the performance profile flip view, as explained below:
the one-day report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Date/Time: Indicates the time when the metrics displayed were collected.
Time (sec): Specifies the length of time between the moment when the user interaction start request was received and the moment when the user interaction transaction was completed, in seconds.
30 Day Avg (sec): Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Metric Status: Indicates where the transaction resides in the resolution process.
Transaction Type: Indicates the category the transaction is organized into.
the one-week report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Date/Hour: Indicates the time when the metrics displayed were collected.
Avg (sec): Specifies the average runtime for transaction responses in the past hour for the given transaction or beacon.
30 Day Avg (sec): Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Historical Median: Specifies the median runtime value for all transaction responses in the past 90 days.
the one-month report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Time (Average): Specifies the daily average value of responses for the transaction, in seconds.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
30 Day Average: Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view ( ) is displayed by default. Click any user interaction record associated with an environment, then click Compare. For more information on how to access the Transactions dashboard, see Accessing the Transactions Dashboard.
In the case of transactions for multiple beacons, the Compare subtab shows the performance chart for all the collection points.
By default, information on the Compare subtab is displayed for the current day. For more information on how to change the time period for your reports, see the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
The chart name uses the following format:
{Location} {Transaction Long Name} {Beacon Name}
where
Location is @Oracle or @Customer.
Transaction Long Name is the long name of the transaction.
Beacon Name is the name of the beacon running the transaction.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the table view in expanded mode, then click the Export icon ( ) in the upper right corner to export the data, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Depending on the selected time period, different information is available for each record in the performance profile flip view, as explained below:
the one-day report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Date/Time: Indicates the time when the metrics displayed were collected.
Time (sec): Specifies the length of time between the moment when the user interaction start request was received and the moment when the user interaction transaction was completed, in seconds.
30 Day Avg (sec): Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Metric Status: Indicates where the transaction resides in the resolution process.
Transaction Type: Indicates the category the transaction is organized into.
the one-week report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Date/Hour: Indicates the time when the metrics displayed were collected.
Avg (sec): Specifies the average runtime for transaction responses in the past hour for the given transaction or beacon.
30 Day Avg (sec): Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Historical Median: Specifies the median runtime value for all transaction responses in the past 90 days.
the one-month report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the user interaction transaction.
Time (Average): Specifies the daily average value of responses for the transaction, in seconds.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
30 Day Average: Specifies the running mean of all response times for the user interaction transaction over the preceding 30 days.
Click the Sustained Stress (Last 24 Hours) icon ( ) in the Alert column and navigate to the Sustained Stress tab, showing an overview of the transaction performance, as follows:
the Response Time (sec) table shows an overview of the transaction performance for a specified beacon, with information about the duration of the stress period, as well as the minimum and maximum thresholds which show the usual response time range for the transaction. The following details are displayed on mouse-over:
Date/Time
Performance(sec)
Use the zoom-in option in the Response Time (Sec) table to gain a closer view of interesting issue periods, their duration, and proximity to previous issue periods.
the Proximate Events table shows information about the possible events contributing to the sustained stress periods. Depending on the event type, the following details are displayed on mouse-over:
functional events (outages and service interruptions):
Outage ID
MOS Ref#
change requests and service requests:
MOS Ref#
Subject
|
Note: To see information about change requests and service requests in the Sustained Stress tab, you must have the applicable Request for Change (RFC) and Service Request (SR) privileges for your organization in MOS. Please contact your SDM for more details. |
By default, information on the Sustained Stress tab is displayed for the last 24 hours, with the option to see details over the last 6 months. For more information on how to change the time period for your reports, see the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
This section describes how to use the charts on the Transactions dashboard to analyze Login Transaction Management (LTM) metrics. Click any LTM transaction to open the Current View tab, containing a detailed report of the transaction's performance, as follows:
the Collection Point subtab shows the performance chart for each individual collection point. Use the drop-down list at the top of the dashboard to select the collection point of your focus.
the Compare subtab shows the performance chart for all the collection points.
By default, information on the Current View tab is displayed for the current day. For information on how to change the time period for your reports, see the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
The chart name uses the following format:
{Location} {Transaction Long Name} {Beacon Name}
where
Location is @Oracle or @Customer.
Transaction Long Name is the long name of the transaction.
Beacon Name is the name of the beacon running the transaction.
The performance chart shows the response time for the user interaction over the specified reporting interval, allowing you to determine when the performance issue started, as well as the user zone affected by the issue. The performance threshold and the historical median are included on the chart for reference. The performance threshold is the longest acceptable response time set for the LTM transaction. You can set the threshold in Oracle Enterprise Manager in consultation with your Oracle SDM. The historical median is the value lying at the midpoint of the range of response times measured.
Click the Open Table View icon ( ) in the lower right corner of the chart to open the table view in expanded mode, then click the Export icon ( ) in the upper right corner to export the data, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Depending on the selected time period, different information is available for each record in the performance profile flip view, as explained below:
the one-day report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.
Date/Time: Indicates the time when the metrics displayed were collected.
Time (sec): Specifies the length of time between the moment when the user interaction start request was received and the moment when the LTM transaction was completed, in seconds.
30 Day Avg (sec): Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Metric Status: Indicates where the transaction resides in the resolution process.
Transaction Type: Indicates the category the transaction is organized into.
the one-week report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.
Date/Hour: Indicates the time when the metrics displayed were collected.
Avg (sec): Specifies the average runtime for transaction responses in the past hour for the given transaction or beacon.
30 Day Avg (sec): Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
Historical Median: Specifies the median runtime value for all transaction responses in the past 90 days.
the one-month report shows the following information:
Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.
Time (Average): Specifies the daily average value of responses for the transaction, in seconds.
Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.
30 Day Average: Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.
Use the filter in the upper right part of the Transactions List view at Customer and Service Level to display only the records of interest. Depending on your services, available options include:
All Transactions: Use this option to display all the transactions associated with your organization's services or environments which were specifically configured to be monitored by the Oracle Pulse BTM functionality.
EBiz Suite Batch Job: Use this option to display only the Oracle® E-Business Suite batch jobs associated with your organization's services or environments which were specifically configured to be monitored by the Oracle Pulse BTM functionality.
PeopleSoft Batch Job: Use this option to display only the PeopleSoft batch jobs associated with your organization's services or environments which were specifically configured to be monitored by the Oracle Pulse BTM functionality.
User Interaction: Use this option to display only the BTM synthetic user experience transactions associated with your organization's services or environments which were specifically configured to be monitored by the Oracle Pulse BTM functionality.
SOA Partition: Use this option to display only the transactions associated with your SOA partitions which were specifically configured to be monitored by the Oracle Pulse BTM functionality.
| Icon | Name | Description |
|---|---|---|
 |
EBiz Suite Batch Job | A sequence of steps required to complete an Oracle® E-Business Suite task, performed without user interaction. |
 |
E-Business Suite Concurrent Manager | Administrative concurrent programs that manage application requests to invoke concurrent programs, batch jobs, and reports. |
 |
PeopleSoft Batch Job | A sequence of steps required to complete a PeopleSoft task, performed without user interaction. |
 |
PeopleSoft Process Scheduler | Centralized tools that enable application developers, system administrators, and application users to manage PeopleSoft batch processes. |
 |
User Interaction | A sequence of steps that a user takes to complete a task. |
| LTM Transaction | A sequence of steps that logs into the application home page and immediately logs out, allowing application access issues that may arise in relation to infrastructure components, capacity, performance, and access to be reported and tracked. | |
 |
SOA Partition | A separate section of the SOA infrastructure where SOA composite applications are deployed. |
Use the search box at the top of the Transactions List view to search the records of interest by the transaction name.
Oracle Pulse lets you create groups of services for which to generate your reports. To do this:
Click the Service Group icon ( 
) in the upper right corner of the page.
The Service Group side pane opens.
Select the check boxes corresponding to the services you want to include in your service group.
Click Apply to save your changes and create your service group. The data on the Transactions Dashboard is refreshed to show data only for the services you have selected, and the Service Group icon ( ), along with the number of selected services, is displayed in the upper part of the dashboard.
For more information about the Service Group feature, see the Working with Service Groups section in Chapter 3, "Working with Oracle Pulse".
