Page History
...
The following table describes which tasks can be performed in each tab.
Table 2- 1 Precise for SAP tabs
| Tab | Description |
|---|---|
| Dashboard | The Precise for SAP Dashboard is an easy-to-use tool for visualizing the overall health and status of all monitored SAP systems. The Precise for SAP Dashboard tab provides support for detailed views of individual application servers, organizations, locales and other entities as well as top-level summary views of multiple SAP systems. |
| Activity | The Activity tab displays detailed information on the historical activity of your SAP system. Performance information displayed in this tab can be used to identify and analyze the cause of a performance problem and is a prime source of input for future tuning decisions. For example, this tab can help you identify the user and transaction that consumed the most resources during the last day and discover where the time was spent. For example, the time may be spent in waiting for a work process, or in processing the request in the database. The Activity tab enables you to answer the following types of questions: "How well did my SAP system perform yesterday?" or "Why did the transactions in the SAP System run so slowly from 8 AM to 10 AM yesterday?" |
| Availability | The Availability tab displays detailed information on the availability of your SAP system. Availability of a SAP system is comprised of application server availability and connectivity (which is the network availability to the locales). Performance information displayed in this tab can be used to identify and analyze the cause of a drop in SAP availability. For example, this tab can help you identify the SAP application servers that were down during the past 24 hours. and discover what component caused this downtime. The Availability tab enables you to answer the following type of question: "How available was my SAP system yesterday?" |
| Jobs | The Jobs tab displays detailed information on current and historical jobs running on your SAP system. Performance information displayed in this tab can be used to identify and analyze the cause of a job performance problem. For example, this tab can help you identify the user and job of the batch that consumed the most resources during the past 24 hours. The Job tab enables you to answer questions such as: "How long did my batch jobs take yesterday?" |
| Statistics | The Statistics tab displays detailed information on the hosts comprising your SAP system. Information displayed in this tab can be used to identify and analyze the cause of a performance problem and is a prime source of input for future tuning decisions. For example, this tab can help you identify the host that had the highest average CPU consumption during the past 24 hours. |
| Anchor | ||||
|---|---|---|---|---|
|
...
The following figure describes the common key elements in the Activity tab and what happens when you drill down to a specific entity.
Figure 2- 1 Typical Precise for SAP tab structure
...
The Precise bar enables you to keep track of where you have been and provides various controls. The following table describes the function of each of the toolbar buttons.
Table 2-2 Precise bar functions
| Button | Name | Description |
|---|---|---|
 | Back | During a work session, keeps track of where you have navigated to. The Back button enables you to navigate between previously visited views. The Back control displays your previous view. |
 | Forward | Enables you to navigate to the next view. This button is only enabled if you clicked Back or if you chose a history option. |
 | Stop | Stops a request for information from the server. |
 | Refresh | Updates the data currently displayed. |
 | Favorites | Enables you to add or remove favorites in your Favorites list. |
 | Send | Opens a new email message in your email program with the link to the current application in context. |
 | Home | Navigates to the highest level entity (stays in the same Tier, tab, or view). The time frame settings remain the same. |
 | Help | Opens the online help in context. |
 | Settings | Lets you configure various program settings. |
 | AdminPoint | Launches Precise AdminPoint. |
About the Main area
The Main area displays general information on the selected instance or entity, in context (the entity that is described in the Tab Heading). The structure of this area depends on the selected entity and tab. For example, some views show two overtime graphs, displayed side-by-side, describing two data series.
...
In some tabs, you can filter the contents of the view by clicking the Filter button. See “Filtering data” on page 19 Filtering data.
About the Association area
...
The following icons are used to indicate which format information is displayed.
Table 2- 3 Changing the format in which information is displayed
| Icon | Description |
|---|---|
 | Display the information in numerical format. |
 | Display the information in a bar graph. |
 | Display the information as a stacked bar graph. |
 | Display the information in percentage format. |
The Association area lets you drill down to another entity by clicking a row. The information displayed in both the Main area and the Association area will change to reflect your selection. See “Filtering data” on page 19 and “Associating Filtering data and Associating entities with data that meets specific criteria” on page 19criteria.
| Anchor | ||||
|---|---|---|---|---|
|
The term “in"in-context” context" means that you can display additional information on a selected item by drilling down to another tab or view. The filter settings you defined (for example, the selected time you chose) and the entity you selected are carried over to the other view or tab, to allow you to continue analyzing your subject from a different perspective. This concept takes on slightly different meanings depending upon where you are attempting to drill down in context from.
...
Precise for SAP provides performance and utilization information on your SAP system. You can view this data according to your company’s organization structure and locale’s by configuring the relevant Mapping and Locale settings.For For more information, see the Installing SAP Tier Collectors section in the Precise Installation Guide SAP tier collector installation.
Configuring Display settings
...
Selecting a predefined time frame from the toolbar displays transaction performance data for the selected time period up to the current time. See “Selecting Selecting a predefined time frame from the Precise for SAP toolbar” on page 18toolbar.
Selecting the time frame using the calendar icon, you can choose to define a time range independent of the current time, or to define a time range up to the current time. See “Selecting Selecting a time frame using the calendar icon” on page 18. icon.
The predefined time frame options are:
...
The time frame selected affects all information displayed in Precise for SAP. Only data that falls within the selected time frame is shown in these areas.
| Anchor | ||||
|---|---|---|---|---|
|
To select a predefined time frame, from the Precise for SAP toolbar, select one of the predefined time frames.
| Anchor | ||||
|---|---|---|---|---|
|
To select a time frame
- Click the calendar icon. In the dialog box that is displayed perform one of the following:
- To define a time frame independent from the current time, select the ‘Time Range’ option and select the Time Range, and then select the Start and End dates and times.
- To define a time frame up to the current time, select the ‘Last’ option Last, and enter the desired time frame.
- To use one of the three previously used time frames, select the ‘Recently used’ option and from the drop- down menu select the desired time frame.
- To use a previously saved time frame, select Use a previously saved time frame and from the drop-down menu select the desired time frame.
- To save your settings for future access, select Save these definitions for future use as: and enter a name in the corresponding field.
- Click OK.
...
The Client selector contains a list of all SAP clients that were configured in the selected system. You can choose to filter out and view information on a specific client’s client's activities by selecting it from the Client Selector list or choose All Clients to view information on the activities of all SAP clients configured in the selected system.
...
You can define flexible selection criteria in the Filter Dialog Boxdialog box. To open the dialog box, you need to click the Filter Off icon next to the Time Frame selector. Filter On or Filter Off indicates the current state of the filtering mechanism.
- Filter Off
...
- all information is shown
...
- Filter On
...
- only a subset of information is shown
...
When you apply your selections in the Filter dialog box, the information displayed in both the Main area and the Association area is modified to reflect your selections. Also, the filtering continues to apply when you drill down to associated entities.
...
You can send an email message to one or more recipients from the Precise toolbar. The default subject for the message will be “Link is, "Link to a Precise application”application."
The email will include a link to the Precise product in the current context (time frame and selected entries).
...
- Relative Time Frame. Saving relative timeframe instead of static date. For example, saving the last 7 seven days will always display the last 7 seven days, depending on the day entered.
- One click to specific location. Once you open Precise by launching a saved Favorite item, you will not have to enter a login credential nor click the login button.
- IE Favorites support. Adding a new Favorite item in Precise will also add it to the IE Favorites menu.
- Auto Complete. The Favorites dialog includes a new combo box which supports AutoComplete.
- Auto Naming. The Favorites dialog generates item names based on the current location.
...
The following table describes the information displayed by the response time counters.
Table 2- 4 Response time counters
| Counter | Description |
|---|---|
| Client time | If working in a LAN, client time should be a very small portion of total SAP response time. |
| Queue time | Should be a very small portion (less than 1%) of the total SAP response time. When this value is high, other long-running transactions or batch programs prohibit proper throughput, or not enough work processes are available. |
| Application time | Includes load time and should be no more than 60% of total SAP response time. When this value is high, the CPU is slowed down, there are SAP memory shortages or the program takes an excessive amount of time for load, queue or ABAP/4 application processing. |
| DB time | Should be approximately 40% of total SAP response time. |
About application time counters
Application time counters help you determine which application time component constitutes a performance bottleneck. The following table describes the information displayed by the application time counters.
Table 2- 5 Application time counters
| Counter | Description |
|---|---|
| Load time | Should be no more than 10% of the application’s total response time. If this value exceeds 10%, this indicates that the SAP System is spending too much time loading the application. Check the Memory Resources counter to determine if there are any SAP memory shortages. If it appears that the CPU or memory resources are sufficient for the application’s processing, check for the following actions:
|
|
| |
| Enqueue time | Should constitute a small percentage of the application time. When enqueue time is high, check or perform the following actions:
|
| Roll-wait time | The number of seconds that may be required to wait during roll-in of context information for dialog steps. The number of seconds required to transfer GUI control-related information to the front-end solution is also included. During processing, a program may result in a roll-out while waiting for other processing to take place. The process of roll-out and roll-in (in this case) is usually a change of memory pointers, and roll-wait time is minimal. In SAP 4.6 and higher, several communication steps, called round trips, can occur between the application servers and the front-end system. During the round trip, the application server transfers GUI control-related information to the front-end system. The work process is rolled-out and this time is recorded under roll-wait time. Network and front-end time are included as part of roll-wait time, but only as it applies to the control-related information transferred between the application server and the front-end system during the execution of the dialog step. Network time associated with the first request and the last request is therefore not included in roll-wait time. Roll-wait time should be very low. When high, perform the following steps:
|
| Process time | Should constitute 50-60% of the application’s total SAP response time. When this percentage is higher than it should be, system or SAP memory resources are an issue or the application is spending too much time in application logic. Take the following steps:
|
| Anchor | ||||
|---|---|---|---|---|
|
DB time counters identify whether database response time is attributed to sequential reads, direct reads or changes by comparing their times.
...
The following table describes the information displayed by the DB counters.
Table 2- 6 DB time counters
| Counter | Description |
|---|---|
| Sequential Reads | The response time for logical database requests associated with sequential reads (for example, "select * from ..." ABAP/4 statements). |
| Direct Reads | The response time for logical database requests associated with direct reads (for example, "select single ..." ABAP/4 statements). |
| Changes | The response time for logical database requests associated with database inserts, updates and deletes. |
About requests counters
Requests counters show the volume of database read requests and change requests. The following table describes the information displayed by the Requests counters.
Table 2- 7 Requests counters
| Counter | Description |
|---|---|
| Sequential Reads | The number of logical database requests associated with sequential reads (for example, "select * from ..." ABAP/4 statements). |
| Direct Reads | The number of logical database requests associated with direct reads (for example, "select single ..." ABAP/4 statements). |
| Changes | The number of logical database requests associated with database inserts, updates and deletes. |
See “About About DB time counters” on page 24 and “About counters and About average server buffer ratio” on page 25ratio.
About time per request counters
Time per request counters identify when database requests do not fall within their performance boundaries. The following table describes the information displayed by the Times per request counters.
Table 2- 8 Time per request counters
| Counter | Description |
|---|---|
| Sequential Reads | The response time, per request, for logical database requests associated with sequential reads (for example, "select * from ..." ABAP/4 statements). |
| Direct Reads | The response time, per request, for logical database requests associated with direct reads (for example, "select single ..." ABAP/4 statements). |
| Changes | The response time, per request, for logical database requests associated with database inserts, updates and deletes. |
When analyzing these counters, keep in mind the following issues:
- Sequential reads should be less than 40 milliseconds per request.
- Direct read requests should be less than 10 milliseconds per request.
- Change requests are expected to be greater than 25 milliseconds per request.
- When per request times are not within their expected performance boundaries:
- Use the DB Time section to determine the importance of the types of read or change requests in question, with respect to the overall response time.
- Use the Requests section to understand the request volume involved in read and change requests.
- When sequential reads or direct reads are performing poorly, see the Application Server Buffer Ratio section to investigate whether buffering techniques are optimized for read requests.
- When changes or reads are performing poorly and your Application Server Buffer ratio appears normal, but the number of returned rows appears unacceptable, the database is likely the source of the problem and should be examined for additional indexes or other causes.
...
| Anchor | ||||
|---|---|---|---|---|
|
The average server buffer ratio illustrates the degree of optimization related to application server buffering techniques, which optimize performance for database requests by avoiding the need to transfer read requests to the database server.
The following table describes the information displayed by the average server buffer ratio.
Table 2- 9 Average server buffer ratio
| Counter | Description |
|---|---|
| Sequential Reads | The percentage of time sequential read requests were handled by the application server, instead of the database server. Sequential read requests refer to logical database requests associated with sequential reads (for example, "select * from ..." ABAP/4 statements). |
| Direct Reads | The percentage of time direct read requests were handled by the application server, instead of the database server. Direct read requests refer to logical database requests associated with direct reads (for example, "select single ..." ABAP/4 statements). |
Keep in mind the following issues when analyzing these counters:
...
The following table shows which counters are included in the Memory resources.
Table 2- 10 Memory resources
| Counter | Description |
|---|---|
| Private Mode | Private mode conditions should not occur. When private mode conditions occur, the SAP application server's shared memory is insufficient to meet the demands of the application, and the following occurs:
|
| Extended Memory | To determine memory shortage impact on an application's response time, do the following:
|
| Anchor | ||||
|---|---|---|---|---|
|
Precise is a Web-based application. You can access the Precise user interface using the Internet Explorer browser, version 6.0, or later. The syntax of the Precise URL address is http://<server>:<port>,where <server> refers to the Precise FocalPoint server and <port> refers to the port number used by the GUI Web server. By default, the port number is 20790. For example: http://beanotownbeantown:20790.
This URL provides secure access to the StartPoint using authorized roles. From here, you can launch all Precise products. It gives you a quick overview of the status of your environments and access to the AdminPoint, where you can perform various management tasks (see the the Precise Administration Guide for details).
| Info |
|---|
You must have local administrator privileges on the server where the StartPoint is running. |
...
- Type the address of the StartPoint user interface into the Address bar of your browser and click Enter. The Precise login page opens. The login page provides secure access to Precise and to your specific product.
- Specify your authorized role name and password. By default, both role name and password are admin. For more information about role names, see the Precise Administration Guide.
- Click Login. The StartPoint page opens. This is the Precise home page.
- On the Product Selection bar, from the drop-down list, select the product you want to launch.
Precise. Performance intelligence from click to storage. Learn more > >
...
...