Analyzing Services' Stability and Performance

Use the BTM table to identify performance and stability issues for the business-critical user experience and batch transactions for any of your services where BTM has been enabled.

Note

Where BTM has not been enabled, this table is hidden.

This table provides an overview of the performance and stability of all the user experience transactions and batch jobs for each service as observed from the application mid-tier, Oracle data center (both local and remote), and customer data center levels, where configured:

  • Application Local: Identifies a beacon (for example, an agent which executes the transaction) found on a host within the customer's environment.

  • Data Center (Local): Identifies a beacon found on a host in the same data center.

  • Data Center (Remote): Identifies a beacon found on a host within the Oracle (remote) data center.

  • Customer Center: Identifies a beacon found in the customer's data center.

  • Batch: Shows an aggregated summary of the overall stability and performance status for the monitored batch targets.

The stability and performance status for each of these categories is described by means of indicators, as explained 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.

Click either row to open the Transactions table filtered by the selected service:

  • Service Transactions: Indicates the transaction and service name.

  • Run By: For user experience transactions, this column indicates the beacon (execution agent) running the synthetic transaction. For batch job transactions, this column indicates the service environment on which the job is running.

  • Status: Indicates the status of the latest execution of the user experience or batch job transaction.

  • Last Response: Indicates the response time of the last execution of the user experience synthetic transaction or live batch job.

  • Performance: Indicates the transaction performance details for the latest execution of the user experience or batch job transaction.

Use the list in the upper left corner to filter the records in the Transactions table:

  • All: Shows all the transactions – synthetic user experience, and batch jobs - associated with your organization's services which were specifically configured to be monitored by the Oracle Pulse BTM functionality.

  • EBiz Suite Batch Job: Shows only the Oracle® E-Business Suite batch jobs associated with your organization's services which were specifically configured to be monitored by the Oracle Pulse BTM functionality.

  • PeopleSoft Batch Job: Shows only the PeopleSoft batch jobs associated with your organization's services which were specifically configured to be monitored by the Oracle Pulse BTM functionality.

  • User Interaction: Shows only the BTM synthetic user experience transactions associated with your organization's services which were specifically configured to be monitored by the Oracle Pulse BTM functionality.

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.