Configuration of LtmAppURLAccessTest

For each URL through which applications are accessed by the end users, this test reports the time taken by the applications that are load balanced by the target traffic manager to respond to requests, reports the average load time of the application etc. Using this test, administrators can easily identify URL segment groups that are adversely impacting user experience with the web application. This way, you can identify the transactions to the web application that are slow.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the IP address of the traffic manager has to be specified.

• In the PORT text box, enter the port number at which the traffic manager being monitored listens. By default, this is NULL.

• This test groups URLs based on the URL segments configured for monitoring and reports aggregated response time metrics for every group.

  Using the URL GROUPING COUNT parameter, you can specify a comma-separated list of URL segment numbers based on which the pages are to be grouped.

  URL segments are the parts of a URL (after the base URL) or path delimited by slashes. So if you had the URL: http://www.eazykart.com/web/shopping/login.jsp, then, http://www.eazykart.com will be the base URL or domain, /web will be the first URL segment, /shopping will be the second URL segment, and /login.jsp will be the third URL segment.

  By default, this parameter is set to 3. This default setting, when applied to the sample URL provided above, the test will report metrics for the descriptor /login.jsp. If you set this value to 2, then the test will report metrics for the descriptor /shopping.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.