Configuration of JavaTransactionsTest

This test will allow you to monitor configured patterns of transactions to the target Java application, and report their response times, so that slow transactions and transaction exceptions are isolated and the reasons for the same analyzed.

Note:

If the value of any of the parameters of the JavaTransactionsTest test is changed at a later point in time, then the test will not report any metrics for the measurement cycle that immediately follows the change. For instance, say that the JavaTransactionsTest test has been configured to run every 10 minutes, and the last time the test executed was as at 10.30 AM. This means that the test will execute next at 10.40 AM. Now, if you make changes to the test parameters at say, 10.35 AM, no metrics will be reported by the test when it executes at 10.40 AM. However, subsequently, when the test executes again at 10.50 AM, it will report all metrics.

The default parameters associated with this test are:

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

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• The port number at which the specified HOST listens should be specified in the PORT list box. If Java Transaction Monitoring is enabled for the target Java application, then the JTM PORT has to be specified in this text box.

• In the JTM PORT text box, specify the port number configured as the JTM_Port in the jtmConn.props file described in the procedure outlined here.

• Provide a comma-separated list of the URL patterns of web requests/transactions to be monitored in the URL PATTERNS text box. The format of your specification should be as follows: <DisplayName_of_Pattern>:<Transaction_Pattern>. For instance, your specification can be: login:*log*,ALL:*,pay:*pay*

• Provide a comma-separated list of the URL patterns of transactions/web requests to be excluded from the monitoring scope of this test in the FILTERED URL PATTERNS text box. For example, *blog*,*paycheque*

• The Slow transactions measure of this test will report the number of transactions (of the configured patterns) for which the response time is higher than the value (in seconds) specified in the SLOW URL THRESHOLD text box.

• The detailed diagnosis of the Slow transactions response time measure allows you to drill down to a URL tree, where the methods invoked by a chosen transaction are listed in the descending order of their execution time. By configuring an execution duration (in seconds) in the METHOD EXEC CUTOFF text box, you can have the URL Tree list only those methods that have been executing for a duration greater the specified value. For instance, if you specify 5 here, the URL tree for a transaction will list only those methods that have been executing for over 5 seconds, thus shedding light on the slow method calls alone.

• In the MAX SLOW URLS PER TEST PERIOD text box, specify the number of top-n transactions (of a configured pattern) that should be listed in the detailed diagnosis of the Slow transactions response time measure, every time the test runs. By default, this is set to 10, indicating that the detailed diagnosis of the Slow transactions response time measure will by default list the top-10 transactions, arranged in the descending order of their response times.

• In the MAX ERROR URLS PER TEST PERIOD text box, specify the number of top-n transactions (of a configured pattern) that should be listed in the detailed diagnosis of the Error transactions response time measure, every time the test runs. By default, this is set to 10, indicating that the detailed diagnosis of the Error transactions response time measure will by default list the top-10 transactions, in terms of the number of errors they encountered.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• 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.