Analyzing the Performance of Business Transaction Monitoring Transactions
Analyze the performance of business transaction monitoring transactions.
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:
Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs
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.
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.
Analyzing Performance for PeopleSoft Process Schedulers and Jobs 🔗
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.
Analyzing Performance for User Interaction Transactions 🔗
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 Flag option helps you easily identify low performing transactions, while Sustained Stress option 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.
Analyzing Performance for Login Transaction Management Transactions 🔗
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.
Analyzing Performance for SOA Composites 🔗
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.