Page History
...
Precise for Web continuously collects high-quality metrics from the end-user’s user's browsers and from the Web servers of your Web server-based applications and correlates these metrics to build a clear picture of application performance from the end-user perspective - response time.
The Precise for Web user interface is made up of three tabs. Each tab has a different focus, provides a different view into your Web application’s application's performance, or identifies patterns in resource consumption.
The table below describes which tasks can be performed in each tab.
Table 2- 1 Tabs in Precise for Web
| Tab | Description |
|---|---|
| Dashboard | Lets you quickly identify which Web instance has a performance problem, providing the first glimpse into where the problem lies. |
| Activity | Lets you examine the application’s performance over time and helps locate performance bottlenecks in its behavior. |
| Statistics | Lets you identify performance bottlenecks in the way Web instance resources are used. |
| Anchor | ||||
|---|---|---|---|---|
|
...
The following figure shows the structure of a typical tab.
Figure 2- 1 How a typical tab is structured
...
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
| Icon | Name | Description |
|---|---|---|
 | Back | During a work session, keeps track of where you have navigated to. The Back and History buttons enable 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. |
 | AdminPoint | Launches Precise AdminPoint. |
 | Home | Navigates to the highest level entity, usually the instance or Tier (all instances). The time frame settings remain the same. |
 | 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. |
 | Settings | Opens the General Settings, Transactions & Users Settings, and Time Frame Settings dialog boxes. |
 | Help | Opens the online help in context. |
About the Main area
In most tabs, the left or top area is the Main area. This area displays an overview of all instances monitored by your Precise product. This information can be displayed in either graph, table, or tree format. The time frame for which the information is displayed is shown in the workspace toolbar. The times displayed are the local times on the FocalPoint server where the page is generated.
...
| Anchor | ||||
|---|---|---|---|---|
|
The term “in"in-context” context" means that you can display additional information on a selected item by drilling down to another workspace or view. The filter settings you define (for example, the time frame you chose) and the entity you select are carried over to the other view or workspace, 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. Therefore, the information displayed when drilling down in context is always related to your original selection’s settings.
For example, when viewing information on an instance in the Dashboard workspace, you can click a link in the Details area (right pane) to view additional information on the related workspace, in the context of your original selection. Or when viewing a list of alerts for your product in Alerts, you can open your product in context and continue investigating the factors that led the system to issue that alert. This means that the information displayed when drilling down in context is always related to your original selection’s selection's settings.
| Anchor | ||||
|---|---|---|---|---|
|
...
Each settings tab displays an instances and clusters table that enables you to select a specific instance, cluster, multiple instances, or multiple clusters. By default, the instances and clusters table displays a list of all monitored Precise for Web instances and clusters that reside on the displayed Tier’s Tier's node on the Tree View (where available). The user can control the way data is displayed in the table.
Click the triangle on the name column heading to sort instance and cluster data in ascending or descending order. Click on the filter icon displayed on selected table headings to filter data in that table column.
Table 2- 3 Typical column headers on the tabs
| Heading | Description |
|---|---|
| Name | Name of the instance and server or cluster. |
| Type | Instance or cluster. |
| Application (Tier) | A list of the applications and Tiers that contain the instance or cluster. |
| Details | A short description of the instance or cluster current settings, according to the selected tab. |
| Server | Name of the server on which the instance or cluster is installed. |
Setting parameters at the cluster level affects all instances in that cluster. It is impossible to set parameters for an instance within a cluster individually.
...
- Click to select one or more clusters for editing (for selecting more than one, press and hold down the CTRL key while clicking the clusters you want to select).
- Click Edit. Select the most suitable method to collect the application users’ users' data. The two options are: Import settings or configure the user’s user's collection method manually. The configuration format varies according to the selected method.
- Click OK.
...
- In the Edit Instance or Cluster dialog box, click Import...
- Use the application and/or Tier fields.
- Click OK and the instance’s instance or cluster’s cluster user collection method configuration will be is copied to the Edit Instance or Cluster dialog box.
Manually configure the user collection method configuration
Manually configure the user’s user's collection method by selecting a method in the ‘Select method:’ field.
| Info |
|---|
The available methods in the ‘Select method’ field vary according to the selected instance(s) or cluster(s). |
Table 2- 4 Available methods for manual configuration
| Method | Pre-Requisite Instance Configuration | Description |
|---|---|---|
| Automatic | None | Try methods one after the other (until the application user is found) in the following order:
|
| User-Defined Server | None | Allows extracting the user from the request header, cookie, or URL parameter. |
| Remote User Variable | None | Returns the REMOTE_USER Web server variable value. |
| SiteMinder | SiteMinder should be installed and configured to provide user information using the request header, cookie, or URL parameter (SM_USER). | Collect the user from the SM_USER key (request header, cookie, or URL parameter). |
| User-Defined Client | Dynamic instrumentation agent installed. | Allows extracting the user from the cookie, URL parameter, or DOM Element. |
| Login Forms | Client-side collection (dynamic instrumentation) is installed. | Collect the user from HTML login forms. |
| PeopleSoft | PeopleSoft application and Client-side collection (dynamic instrumentation) is installed. | Collect the user from PeopleSoft HTML pages. |
| Oracle Applications | Oracle Applications and Client-side collection (dynamic instrumentation) is installed. | Collect the user from the Oracle Applications login form. |
| SAP Portal | SAP J2EE application and client side collection (dynamic instrumentation) is installed. | Collect the user from the SAP Portal login form. |
| IIS API | IIS Web server | Uses the information that IIS API provides. |
| J2EE API | J2EE Web servers (WebSphere, WebLogic, Tomcat, Oracle Applications server, SAP J2EE, SunOne) | Uses the information that J2EE API provides. |
About Login Forms configuration
When selecting the Login Forms option, the login forms table appears, which allows you to add/edit the list of URLs or forms, where the user name should be collected from. Clicking the Add or Edit button opens the dialog with the following fields (show table).
Table 2- 5 Add / Edit fields
| Radio Button | Field | Description |
|---|---|---|
| Login | Field Name | The name of the username text box in the Web page. Consult the Web page administrator/developer, if applicable, to get this name. Alternatively you can find it by right clicking the mouse near the field and selecting |
View source |
from the |
pop-up menu. The structure of the HTML page should be like the following: <form name="loginForm"… action= …> … User Name: <input type="text" name="myUsernameField"> … </form> The value you need to put in the "Field Name" field in this example is myUsernameField. Note that the input type is |
text |
. Another way to get the field name: copy to the browser's address bar the following command, that should fill all the text boxes in the page with their name and the name of the form. javascript:var frms = document.forms ;for (var formInd=0 ; formInd <frms.length ; formInd++) {var form = frms[formInd];var elems = form.elements;for (var ind=0; ind< elems.length; ind++ ){var field = elems(ind);if (field.type == "text")field.value="Field=" +field.name + " form=" + form.name;}};void(0); | |||
| URI | To save the time of looking for the field in all pages, specify the URI of the login page, e.g.
| ||
| Form Name | If the URI is dynamically changing, or you can reach the login page using many URIs, you can mention instead (or in addition) the form name in which the user name field exists. You can find the form name in the same way mentioned above; in this example the value for the form name would be loginForm. | ||
| Logout | URI | Specify the URI of the logout page that after visiting makes sure that the user is no longer signed in , e.g. /signOut.jsp. All pages in a session since visiting the login page are marked as visited by the found user. Pages visited after this URI are no longer related to the user. |
About manually configuring URL parameters
...
- Select one or more instances or clusters in the table for which you want to configure the URL parameters.
- Define how to display the parameters in the parameter part of the URL.
- Define rules for specific parameters.
See Editing URL mapping rules for an instance or cluster in the system on page 19.
| Anchor | ||||
|---|---|---|---|---|
|
You can define how to handle parameters in the parameter part of a URL by using the URL Parameters dialog box. This dialog box also lets you specify exceptions to the defined rule.
...
Selecting a predefined time frame from the toolbar displays transaction performance data for the selected time period up to the current time. See Selecting a predefined time frame from the Precise for Web toolbar on page 21.
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 a time frame using the calendar icon on page 21.
The predefined time frame options are:
...
The time frame selected affects all information displayed in Precise for Web. 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 Web 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 Start and End dates and times.
- To define a time frame up to the current time, select the ‘Last’ option 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.
...
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.”"
The email will include a link to the Precise product in the current context (time frame and selected entries).
...
- Relative Time Frame. Saving a relative time frame 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.
...
To export a table view
- Click the Column Chooser icon.
- Select Export to the Precise Custom Portal Portlet.
- Insert a name in the name field that clearly describes the table view.
- Click OK.
...
- Right-click the graph.
- Select Export to the Precise Custom Portal Portlet.
- Insert a name in the name field that clearly describes the graph view.
- Click OK.
Precise. Performance intelligence from click to storage. Learn more > >
...