Page History
...
Table 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 | ||||
|---|---|---|---|---|
|
...
Table 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.
...
Table 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.
...
Table 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 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 popup 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
...
- 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.