This section includes the following topics:
- About the Oracle Apps Top Forms portlet
- About the Oracle Top Applications portlet
- About the PeopleSoft Application Over Time portlet
- About the SAP Top Transactions portlet
- About the SAP Top Users portlet
- About the Siebel Application Business View portlet
- About the Siebel Location Business View portlet
About the Oracle Apps Top Forms portlet
The Oracle Apps Top Forms portlet displays the top Oracle Apps forms in a selected instance or in all instances in the selected Tier. This view easily identifies the Apps forms consuming the most resources.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 11-1 Oracle Apps Top Forms fields
| Field | Description |
|---|---|
| Forms | Displays the activity of the top Oracle Applications Forms in the selected application. |
| Response+Network Times (Summed) | Displays the total response and network time. |
| Work Times (Summed) | Displays the sum of the processing time spent in the Forms server and the Database server. |
| Network Times (Summed) | Displays the time spent on network activity from the server-side perspective. This includes the time spent reading the request from the network and the time spent sending the response back to the client through the network. |
| Response+Network Time (Avg) | Displays the average response and network time. |
| Work Time (Avg) | Displays the average processing time spent in the Forms server and the Database server. |
| Network Time (Avg) | Displays the average time spent on network activity from the server-side perspective. This includes the time spent reading the request from the network and the time spent sending the response back to the client through the network. |
| Network Bytes | Displays the total number of bytes transferred between the clients and the Forms server listener processes. |
| Executions | Displays the number of times a Forms operation was executed. |
| SLA Breach | Displays the percentage of Oracle Forms with SLA settings that did not meet the SLAs of their Oracle Applications (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle Forms with SLA settings that are close to the SLAs of their Oracle Applications (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle Forms with SLA settings that did meet the SLAs of their Oracle Applications. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
About the Oracle Top Applications portlet
The Oracle Top Applications portlet displays the top Oracle applications in a selected instance or in all instances in the selected Tier. This view easily identifies the applications consuming the most resources.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 11-2 Oracle Top Applications fields
| Field | Description |
|---|---|
| Applications | Displays the activity of the top Oracle applications in the selected application. |
| Response+Network Times (Summed) | Displays the total response and network time. |
| Work Times (Summed) | Displays the sum of the processing time spent in the Forms server and the Database server. |
| Network Times (Summed) | Displays the time spent on network activity from the server-side perspective. This includes the time spent reading the request from the network and the time spent sending the response back to the client through the network. |
| Response+Network Time (Avg) | Displays the average response and network time. |
| Work Time (Avg) | Displays the average processing time spent in the Forms server and the Database server. |
| Network Time (Avg) | Displays the average time spent on network activity from the server-side perspective. This includes the time spent reading the request from the network and the time spent sending the response back to the client through the network. |
| Network Bytes | Displays the sum of bytes transferred between the clients and the Forms server listener processes. |
| Executions | Displays the number of times a Forms operation was executed. |
| SLA Breach | Displays the percentage of Oracle Forms with SLA settings that did not meet the SLAs of their Oracle Applications (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Oracle Forms with SLA settings that are close to the SLAs of their Oracle Applications (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Oracle Forms with SLA settings that did meet the SLAs of their Oracle Applications. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
About the PeopleSoft Application Over Time portlet
The PeopleSoft Application Over Time portlet displays the overtime resource usage of the selected application
To view data in this portlet, verify that:
- The Web, J2EE, Tuxedo, and Oracle components are installed in the selected application
- The Precise SmartLink transaction tracking mechanism for PeopleSoft is enabled
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 11-3 PeopleSoft Application Over Time fields
| Field | Description |
|---|---|
| Date and Time | Displays the date and timestamp of the data available in the selected time frame. |
| Response Times (Summed) | Displays the total response time experienced by all clients from the selected PeopleSoft Application over time. The response time includes the net response time of the different Tiers. Response Times (Summed) = Client Times (Summed) + Web Server Times (Summed) + J2EE Times (Summed) + Tuxedo Times (Summed) + Database Times (Summed) |
| Client Times (Summed) | Displays the total time spent in the Web Client Browser side, until they begin being processed by the Web server. This field is only available in applications that include a Web Client Installation of Precise for Web. In this case, you should edit the portlet so that this field is not displayed. |
| Web Server Times (Summed) | Displays the total time spent in the Web Server, until they begin being processed by the next Tier (J2EE). This column is available in applications that include a Web Server Installation of Precise for Web. In this case, you should edit the portlet so that this field is not displayed. |
| J2EE Times (Summed) | Displays the total time in the J2EE Tier, until processing by the next Tier (Tuxedo) starts. |
| Tuxedo Times (Summed) | Displays the total time in the Tuxedo Tier, until processing by the next Tier (Database) starts. |
| Database Times (Summed) | Displays the total time spent in the Database Tier. |
| Response Time (Avg) | Displays the average response time experienced by all clients from the selected PeopleSoft Application over time. The response time includes the net response time of the different Tiers. Response Time (Avg) = Client Time (Avg) + Web Server Time (Avg) + J2EE Time (Avg) + Tuxedo Time (Avg) + Database Time (Avg) |
| Client Time (Avg) | Displays the average time spent in the Web Client Browser side, until they begin being processed by the Web server. This field is only available in applications that include a Web Client Installation of Precise for Web. In this case, you should edit the portlet so that this field is not displayed. |
| Web Server Time (Avg) | Displays the average time spent in the Web Server, until they begin being processed by the next Tier (J2EE). This column is available in applications that include a Web Server Installation of Precise for Web. In this case, you should edit the portlet so that this field is not displayed. |
| J2EE Time (Avg) | Displays the average time in the J2EE Tier, until processing by the next Tier (Tuxedo) starts. |
| Tuxedo Time (Avg) | Displays the average time in the Tuxedo Tier, until processing by the next Tier (Database) starts. |
| Database Time (Avg) | Displays the average time spent in the Database Tier. |
| Executions | Displays the total number of transactions requested by the PeopleSoft Application, over a specified time period. |
| SLA Breach | Displays the percentage of transactions with SLA settings that did not meet their SLAs (as defined in the breach threshold settings). |
| SLA Near-Breach | Displays the percentage of transactions with SLA settings that are close to their SLAs (as defined in the near-breach threshold settings). |
| SLA OK | Displays the percentage of transactions with SLA settings that did meet their SLAs. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
About the SAP Top Transactions portlet
The SAP Top Transactions portlet displays the top SAP transactions in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for SAP is installed in the selected application, and that it is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 11-4 SAP Top Transactions fields
| Field | Description |
|---|---|
| Transaction | Displays the top SAP transaction or transactions. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Client Times (Summed) | Displays the total client time of the activity. The client time is the time the activity spent on the way to or back from the SAP application server plus the time it spent in the client machine. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local SAP application server (including queue time). |
| Queue Times (Summed) | Displays the amount of time the activity waited in the queue for processing by the local SAP application server. |
| Application Times (Summed) | Displays the total time spent on the activity being processed by the SAP application server. |
| Database Times (Summed) | Displays the total database time of the activity. The database time is the time the activity spent in the SAP database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Client Time (Avg) | Displays the average processing time the activity spent on the way to or from the SAP application server plus the time it spent in the client machine. |
| Work Time (Avg) | Displays the average processing time spent in the local SAP application server (including queue time). |
| Queue Time (Avg) | Displays the average time the activity waited in the queue for processing by the local SAP application server. |
| Application Time (Avg) | Displays the average time spent on the activity being processed by the SAP application server. |
| Database Time (Avg) | Displays the average database time of the activity. The database time is the time the activity spent in the SAP database. |
| Executions | Displays the number of times an SAP transaction was executed. |
| SLA Breach | Displays the percentage of SAP transactions with SLA settings that did not meet SAP transactions' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SAP transactions with SLA settings that are close to their SAP transactions' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SAP transactions with SLA settings that did meet the SAP transactions' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
About the SAP Top Users portlet
The SAP Top Users portlet displays the top SAP users in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify Precise for SAP is installed in the selected application, and that it is integrated with PMDB and Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 11-5 SAP Top Users fields
| Field | Description |
|---|---|
| User | Displays the top SAP users in the selected application. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Client Times (Summed) | Displays the total client time of the activity. The client time is the time the activity spent on the way to or back from the SAP application server plus the time it spent in the client machine. |
| Work Times (Summed) | Displays the sum of the processing time spent in the local SAP application server (including queue time). |
| Queue Times (Summed) | Displays the amount of time the activity waited in the queue for processing by the local SAP application server. |
| Application Times (Summed) | Displays the total time spent on the activity being processed by the SAP application server. |
| Database Times (Summed) | Displays the total database time of the activity. The database time is the time the activity spent in the SAP database. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Client Time (Avg) | Displays the average processing time the activity spent on the way to or from the SAP application server plus the time it spent in the client machine. |
| Work Time (Avg) | Displays the average processing time spent in the local SAP application server (including queue time). |
| Queue Time (Avg) | Displays the average time the activity waited in the queue for processing by the local SAP application server. |
| Application Time (Avg) | Displays the average time spent on the activity being processed by the SAP application server. |
| Database Time (Avg) | Displays the average database time of the activity. The database time is the time the activity spent in the SAP database. |
| Executions | Displays the number of times an SAP transaction was executed. |
| SLA Breach | Displays the percentage of SAP transactions with SLA settings that did not meet SAP transactions' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of SAP transactions with SLA settings that are close to their SAP transactions' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of SAP transactions with SLA settings, that did meet the SAP transactions' SLA. |
See About the Tools portlets, Configuring the portlet, and Defining the portlet data preferences.
About the Siebel Application Business View portlet
For information regarding the Siebel Application Business View portlet, see About the Siebel Application Business View portlet.
About the Siebel Location Business View portlet
For information regarding the Siebel Location Business View portlet, see About the Siebel Location Business View portlet.
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal