3.2.3 Setting up the Web transactions to be monitored

(1) Before you start

• Verify that you have the service group administrator permissions.

• Verify that the monitored service has been registered.

  For details about how to register monitored services, see 3.2.1 Registering monitored services.

• Verify that monitoring of the monitored service for which Web transactions are to be set up has been stopped.

  For details about how to stop monitoring, see 4.2.2 Stopping monitoring.

To Page Top

(2) Procedure

The following shows the procedure:

Shown below are the Settings window, Register Web transaction window, Add Web access condition window, Edit cookie window, and Edit query window that are used in this task.

• Settings window

  

• Register Web transaction window (displayed in a new window when the New button is clicked (step 4))

  

• Add Web access condition window (displayed in a new window when the Add condition button is clicked (step 6))

  

• Edit cookie window (displayed in a new window when the Edit cookie button is clicked (step 11) or the Cookie text box is clicked (step 13))

  

• Edit query window (displayed in a new window when the Query text box is clicked (step 13))

  

To set up the Web transactions to be monitored:

1. Click the Settings button.

2. In the Setting menu area, select Web transaction setting.

   The Web transaction setting area is displayed.

3. From the Services area, select the monitored service.

   When you select a monitored service, the service group name and monitored service name are displayed in the Web transaction setting area. Any Web transaction name that has already been set for the monitored service and the Web access conditions for that Web transaction are displayed under Web transaction and Web access condition in the Web transaction setting area. Immediately after the monitored service has been registered, nothing is displayed under Web transaction and Web access condition.

4. Click the New button.

   The Register Web transaction window is displayed.

5. Enter a name for a Web transaction.

   Enter a name in the Web transaction name text box.

   If an input rule is violated, an error message is displayed. Although no error message is displayed when platform-dependent characters or control characters are used, these characters might cause erroneous display of log files.

   Note that the same transaction name cannot be registered more than once for the same monitored service.

6. Click the Add condition button.

   The Add Web access condition window is displayed. The Source IP text box displays the IP address of the current computer (that is accessing ITSLM via a browser).

   The procedure for adding Web access conditions depends on the addition method:

   • To import Web access conditions from a URI that was detected automatically by accessing the monitored service

     Go to step 7.

   • To import Web access conditions from the URI of a monitored service that you entered directly

     Go to step 10.

   • To directly enter Web access conditions

     Go to step 13.

   Specify for the Web access conditions the case-sensitive path, query, and cookie used for actual Web access. ITSLM monitors the Web accesses that match the specified character string.

   Some browsers might convert the case during actual Web access. If the case does not match between the specified Web access conditions and the actual Web access, the Web transaction cannot be monitored.

7. Click the Start detection button.

   Status changes from Stopped to Detecting and URI detection is enabled. The Start detection button changes to the Stop detection button.

   The following figure shows Status changed to Detecting.

   Figure 3‒27: Status changed to Detecting (Add Web access condition window)

8. Open a new page in the browser logged in to ITSLM - Manager or start another browser, and then access the monitored service's Web page.

   In this case, make sure that you do not change or close the browser logged in to ITSLM - Manager and that you open a new page or start another browser.

   The URI detected by the access is added to Available URI. Each time a different Web page is accessed, a new URI is added. A URI that has already been detected is not added.

9. After the URI has been detected, click the Stop detection button.

   Status changes from Detecting to Stopped and detection is complete.

   The following figure shows Status that has changed to Stopped.

   Figure 3‒28: Status changed to Stopped (Add Web access condition window)

10. To edit a URI displayed under Available URI, select a desired URI and then edit it. You can also add a new URI by adding a blank line.

    You can edit any of the URIs displayed under Available URI by clicking the URI. You can also add a blank line under Available URI and then directly enter a desired URI. To directly enter a URI, click the Add line button and then enter the URI on the added line.

11. To check or edit the cookie of a URI displayed under Available URI, select the URI, and then click the Edit cookie button.

    The Edit cookie window is displayed. In the Edit cookie window, you can check, add, change, or delete the cookie to be imported to the Web access conditions. Edit the cookie, if necessary, and then click the OK button.

12. Select a URI from Available URI and then click the Import Available URI button.

    In Define Web access condition, you can enter the path, query, and cookie values of the URI selected from Available URI all at once.

13. To directly enter or edit Web access conditions, enter or edit the path condition, query condition, and cookie condition in Define Web access condition.

    If you click the Apply Web Access Condition button after you have entered or edited the conditions, there is further refinement of the URIs displayed under Available URI and only the URIs that perfectly match the conditions are displayed.

    Directly enter the path condition in the text box. Enter query and cookie conditions in the Edit query window and Edit cookie window, respectively, that are opened when you click the corresponding text box.

    You can specify multiple query and cookie conditions, but the maximum number of conditions that you can specify is 20 including both query and cookie conditions. When you specify multiple conditions, they are separated by a space and displayed in a random order.

    Use the path, query, and cookie conditions to refine URIs so that you can obtain only the URIs of those processes that you want to monitor.

14. While the conditions are showing in Define Web access condition, click the Add condition button in the Add Web access condition window.

    The values entered in Define Web access condition in the Add Web access condition window are displayed in Web access condition in the Register Web transaction window.

15. Repeat the procedure for adding Web access conditions until all the conditions necessary for the Web transactions to be monitored are displayed in Web access condition.

    The same Web access condition cannot be registered more than once. A maximum of five Web access conditions can be specified for one Web transaction.

16. When you have finished adding Web access conditions, click the Close button.

    The Add Web access condition window closes and the Register Web transaction window is displayed again.

17. If necessary, change the order of the Web access conditions by dragging Web access conditions in Web access condition up and down in the Register Web transaction window.

    ITSLM checks the Web accesses against the Web access conditions displayed in Web access condition in this order to determine whether they are for the specified Web transactions.

18. If you want to check whether Web accesses are from the same user, specify session conditions.

    You can specify session conditions by selecting query and cookie conditions displayed in Available query condition and Available cookie condition, respectively. Select a candidate to be used as a session condition and then click the > button.

    Available query condition and Available cookie condition display the keys of query and cookie conditions that match multiple Web access conditions displayed in Web access condition.

    The following shows an example in which the keys of query and cookie conditions that match multiple Web access conditions are displayed.

    This example assumes that the following Web access conditions are displayed in Web access condition:

    No.	Path	Query condition	Cookie condition
    1	/top.html	a=1 b=.*	session=.* c=0
    2	/middle.html	b=.*	session=.* d=0

    b (the key of b=.*) is displayed in Available query condition and session (the key of session=.*) is displayed in Available cookie condition. The following figure shows an example in which Available query condition and Available cookie condition are displayed.

    Figure 3‒29: Example in which Available query condition and Available cookie condition are displayed

    To delete query conditions and cookie conditions from Query condition and Cookie condition, respectively, select a desired query condition or cookie condition in Query condition or Cookie condition, respectively, and then click the < button to move the query condition or cookie condition back to Available query condition or Available cookie condition, respectively. The maximum number of conditions you can specify in Query condition and Cookie condition is 10 including both query and cookie conditions.

19. Click the Registration button.

    If any entries have been added in Web access condition, the Registration button is enabled.

Clicking the Registration button closes the Register Web transaction window, and the Web transaction setting area is displayed again. The settings in the Register Web transaction window are added as a Web transaction to the Web transaction setting area.

To Page Top

(3) Next task

• 3.2.5 Setting up the monitoring items for system performance as configuration information (working with Performance Management) (working with Performance Management)

• 3.2.7 Setting up the monitoring items for service performance (when not working with Performance Management)

To Page Top

(4) Related topics

• 3.1.1 ITSLM's monitoring methods and types of monitored targets

• 3.2.4 Deleting Web transactions to be monitored

• 5.2 User settings in ITSLM

• 10.6.1 Configuration of the Settings window

• 10.1.2(3) Services area

• 10.6.3 Setting menu area

• 10.6.5 Web transaction setting area

• 10.6.6 Register Web transaction window

• 10.6.7 Add Web access condition window

• 10.6.8 Edit Web access condition window

• 10.6.9 Edit cookie window

• 10.6.10 Edit query window

• 10.6.11 Edit Web transaction window

To Page Top