Hitachi

JP1 Version 11 JP1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference


2.4.3 Definition examples (Measurement of Web transactions)

This section explains the definition when you measure Web transactions on the sites with the dynamic session management. PFM - Web Console is taken for example as the sites with the dynamic session management.

To measure the sites with the dynamic session management as a Web transaction, you must specify the variable character strings each time you measure those sites.

When you use PFM - Web Console to measure Web transactions, you must consider the fact that these sites manage the sessions using the dynamically changing session IDs given to its users whenever they log in. The location of the session IDs (that is, in URLs, message bodies, or so) varies depending on the sites.

Thus, to measure Web transaction properly, the session IDs in the URL or message body must be replaced with the newly given session IDs whenever PFM - Agent for Service Response measure Web transactions.

Suppose that you record the following series of procedures in PFM - Web Console as a Web transaction:

  1. Logging on to PFM - Web Console

  2. Operations by using the PFM - Web Console (Displaying reports)

  3. Logging off from PFM - Web Console

The following describes the overview of the procedures to measure this Web transaction correctly.

  1. Record Web transactions

    Use the Web Recorder to record step information of a Web transaction.

  2. Define measurement conditions

    Add necessary settings to measure the recorded Web transaction.

  3. Test measurement conditions

    Check whether the added definition is correct. At the same time, acquire the information to specify the setting for the dynamic session management.

  4. Set conditions for dynamic session management

    Set the conditions to replace the variable string with the substitute string.

  5. Web transaction operation check

    Check whether the Web transaction is measured correctly.

The following subsections describe the details of the procedures:

The information listed below is used in the following procedures. The values are displayed in italics.

Table 2‒7: Necessary items to measure Web transaction

Item

Value

Web transaction file name

sample01.xml

Web transaction name

sample01

Prefix of step ID

SAMPLE_STEP

Task ID

103#

#

Each Task ID in the same Web transaction file must be unique.

Organization of this subsection

(1) Recording Web transactions

The following shows the procedures to record the Web transactions.

  1. From Windows Start menu, choose All Programs, Performance Management, Agent Option for Service Response, and then Web Recorder.

    The Web Recorder (main) window appears.

    [Figure]

    For details about the Web Recorder (main) window, see 7.2.1 Web Recorder (main) window.

  2. From the Transaction menu, choose New.

    The Web Recorder Create New Web Transaction window appears.

  3. Specify necessary items to create new Web transaction.

    Specify sample01.xml in Web transaction file name and specify sample01 in New Web transaction name.

    Check Give a step ID automatically check box, and then, enter a prefix in Prefix. The step IDs are necessary for outputting the acquired HTML and HTTP header in a file collected from pages that are to be accessed by the Web transaction.

    [Figure]

    For details about the Create New Web Transaction window, see 7.2.2 Create New Web Transaction window.

  4. Click the OK button.

    A new Web transaction is created, the specified values are display in Web transaction file name and Web transaction name of the Web Recorder (main) window.

    [Figure]

  5. In the Web Recorder (main) window, from the Transaction menu, choose Set Transaction.

    The Set Web Transaction Conditions window appears.

  6. Set the configuration to output the acquired HTML and HTTP header in a file in Web Transaction Info page.

    • Select the Output the acquired HTML and HTTP header in a file check box.

      After selecting this check box, you can acquire the necessary information to replace the variable string (that is, the session ID when recording) with the substitute string (that is, the newly given session ID when logging in again). You can also check whether PFM - Agent for Service Response monitor transactions correctly.

    • Select UTF-8 in Character set.

      [Figure]

      For details about Set Web Transaction Conditions window, see 7.2.6 Set Web Transaction Conditions window.

  7. Click the OK button.

    The Set Web Transaction Conditions window is closed.

  8. In the Web Recorder (main) window, in Address, enter the URL of the login window of PFM - Web Console and then click the Go button.

    The Login window of PFM - Web Console appears in the IE window.

    [Figure]

  9. Enter a User name and Password in the Login window and click the Login button.

    Log on to PFM - Web Console. The main window appears in the IE window.

  10. In the navigation frame of the main window, select the Reports tab.

    [Figure]

  11. In the menu bar frame of the main window, click the Logout menu to log off from PFM - Web Console.

    The Login window of PFM - Web Console appears in the IE window.

  12. From the Transaction menu, choose Save.

    The Web transaction file is saved.

(2) Defining measurement conditions

The following shows the procedures to define measurement conditions for Web transactions by using PFM - Web Console.

  1. From the monitoring console browser, log on to PFM - Web Console.

    The main window of PFM - Web Console appears.

  2. In the navigation frame of the main window, choose the Services tab.

    The Services window appears.

    [Figure]

  3. In the navigation frame of the Services window, expand the contents of the monitoring agent host folder, and select the Agent Collector service.

    The Properties page appears.

    [Figure]

  4. Expand the hierarchy under the Probe folder, and select the ADD OR DELETE A TASK.

    [Figure]

  5. Set properties appear at the bottom of the information frame.

    Set 103 to the New Task ID, WEBTRANS to the New Task Protocol.

    [Figure]

  6. Click the OK button at the bottom of the information frame.

    The created folder WEBTRANS_103 appears under Task List.

    [Figure]

  7. Select the WEBTRANS_103 tree

  8. Set properties appear at the bottom of the information frame.

    Set 80 to the Interval, sample01.xml to the Filename, and sample01 to the Transaction.

    [Figure]

  9. Click the OK button.

    The specified settings are applied in the measurement condition registration file.

    Reference note:

    You can specify these conditions by editing the measurement condition registration file directly. In this case, add the following contents in the measurement condition registration file:

    <TASK>
      <GEN_PARAM>
        <TASKID>103</TASKID>
        <INTERVAL>80</INTERVAL>
        <TIMEOUT>30</TIMEOUT>
      </GEN_PARAM>
      <SERV_PARAM>
        <WEBTRANS>
          <TRANSACTION_FILE>sample01.xml</TRANSACTION_FILE>
          <TRANSACTION_NAME>sample01</TRANSACTION_NAME>
        </WEBTRANS>
      </SERV_PARAM>
    </TASK>

(3) Testing measurement conditions

The following shows the procedures to test the measurement conditions. Following these procedures, you also acquire the necessary information to specify the setting for the dynamic session management.

  1. Select the WEBTRANS_103 tree under Task List, check the value of Status is Valid.

    [Figure]

  2. Select Probe folder under Services tree, select Yes in Reload and click the OK button.

    [Figure]

  3. Select the WEBTRANS_103 tree under Task List, check the value of Status is Applied.

    [Figure]

  4. Check whether the HTML file with SAMPLE_STEP as prefix in its file name (such as SAMPLE_STEP00001.html) is saved in the following folder by using the Explorer or so:

    installation-folder\agtv\probe\probedata\webtrans
  5. Open SAMPLE_STEP00002.html, check the substitute string in <frame> tag.

    Look at the underlined string on the example below:

    <frameset border="0" frameborder="no" framespacing="0" rows="32,*" onUnload="baseLogout()">
     
        <frame name="PrTitle" noresize scrolling="no" frameborder="no"
    src="/PFMWebConsole/dispMainTitle.do?prSessionId=A_00E71812A672E7E3AA00385404F53228_1197249957218&launchMode=" />
     
        <frameset cols="350,*" border="8" frameborder="yes" framespacing="4" bordercolor="silver">
Hint:

In this example, since the first page where the session ID is found is

SAMPLE_STEP00002.html, check firstly SAMPLE_STEP00002.html.

(4) Setting conditions for dynamic session management

The following shows the procedures to replace the variable string with the substitute string:

  1. From Windows Start menu, choose All Programs, Performance Management, Agent Option for Service Response, and then Web Recorder.

    The Web Recorder (main) window appears.

  2. From the Transaction menu, choose Open.

    The Select Web Transaction window appears.

    [Figure]

  3. From List of Web transaction files, select sample01.xml and from List of Web transactions, select sample01, then click the OK button.

    The specified measurement conditions are read, the Select Web Transaction window is closed.

  4. In the Web Recorder (main) window, from URL list select the URL, and from the Edit menu choose Property.

    The Properties window appears.

    [Figure]

  5. Check whether the URL in the Page Info page or Message body in the Request Info page contains the variable string.

    If the same string (that is, variable string) as which you checked the substitute string in (3) Testing measurement conditions exists in either the URL or the Message body, follow the procedures below. If the string does not exist in both pages, skip the remaining procedures.

    [Figure]

    For details about the Properties window, see 7.2.7 Properties window.

  6. Click the Variable String page.

    The Variable String page appears.

  7. Click the Add button.

    The Conditions of Variable String window appears.

  8. Select the location of the variable string checked at the procedure 5 in the Setting of variable string of the Variable String page.

    [Figure]

    Select either the URL or Message body button.

    For details about the Conditions of Variable String window, see 7.2.8 Conditions of Variable String window.

  9. Enter the variable string you checked at the procedure 5 in the Variable string at the time of the record.

    The variable string when recording is displayed in the Information at the time of the record.

  10. Click the Substitute String page.

    The Substitute String page appears.

    [Figure]

  11. Click the From HTML or HTTP header button, click the Add button.

    The Conditions of Substitute String window appears.

    [Figure]

  12. Specify the substitute string in the Conditions of Substitute String window.

    Specify the values show following table list:

    Item to be specified

    Value

    Step ID

    Select SAMPLE_STEP00002.

    Source of substitute string

    Click the From HTML button.

    Element name

    Enter frame#1 in the text box.

    Where to include substitute string

    Click the Attribute button, and enter src#1 in the Attribute name text box.

    String to exclude from substitute string

    Select the String to exclude from substitute string check box, and enter prSessionId= in the String just before text box, enter & in the String just after text box. #2

    #1

    The variable string you checked in (3) Testing measurement conditions exists in the src attribute of the <frame> tag.

    #2

    These strings surround the variable string when you checked the string in (3) Testing measurement conditions.

    For details about the Conditions of Substitute String window, see 7.2.10 Conditions of Substitute String window.

  13. Click the OK button in the Conditions of Substitute String window.

    The Conditions of Substitute String window is closed.

  14. Click the OK button in the Conditions of Variable String window.

    The Conditions of Variable String window is closed.

  15. Click the OK button in the Properties window.

    The Properties window is closed.

  16. Repeat the procedure 4 to 15 for each step containing the variable string in a Web transaction file.

    The settings of the variable strings and the substitute strings can be imported by clicking the Import button in the Conditions of Variable String window and the Conditions of Substitute String window.

    Example:

    1. Select the next URL (step ID: SAMPLE_STEP00004) after the URL selected in step 4. Then, from the Edit menu choose Property.

    2. Click the Add button on the Variable String page. The Conditions of Variable String window appears.

    3. In the Conditions of Variable String window, click the Import button.

    The Conditions of Substitute String window appears.

    [Figure]

    4. In the Select Source of Variable String Settings window, select Variable string at the time of the record, and then click the OK button.

    The selected variable string appears in the Variable string at the time of the record field in the Conditions of Substitute String window.

    For details, see the following sections:

    When you import the setting of variable strings:

    When you import the setting of substitute strings:

  17. In the Web Recorder (main) window, from the Transaction menu, choose Save.

    The settings are saved in the Web transaction file.

For details about the definitions for supporting dynamic session management, see 4.4.6 Defining settings for the dynamic session management.

(5) Web transaction operation check

The following shows the procedures to check the Web transaction measuring:

  1. From the Start menu of Windows, choose Settings, Control Panel, Administrative Tool, and then Services, right-click the PFM - Agent for Service Response service in the Services dialog box, and from the pulldown menu choose Start (or Restart).

  2. Open each HTML file under the installation-folder\agtv\probe\probedata\webtrans folder by using a text editor, check whether the messages that show the session disconnects or the invalid operations are not output on each HTML file.

    The following shows the example of displaying messages:

    <tr class="v50pr-err-contents">
      <td>Message</td>
      <td class="v50pr-space-normal">
    The window displayed for already logout session is operated.
     <br/>
    Close the window, re-open the window.
      <td>
    </tr>