Top
Systemwalker Service Quality Coordinator User's Guide
Systemwalker

1.1.3 Transaction breakdown analysis

When transaction breakdown analysis measurements are made, only some data is sampled, because collecting information for all transactions that are running would increase the overheads for the system.

Sampling frequency can be changed using the "measurement interval" of the Interstage operating parameter.

Usually, Fujitsu recommends operating with the measurement interval of 1000. This means data is collected for one transaction out of every 1000 transactions. Change the frequency only when there are very few transactions and very little transaction breakdown analysis data can be collected. The measurement interval, 1000, assumes a load of about 10 transactions per second. When changing the value, change the value so that information is collected about once every 100 seconds.

If the measurement interval is too short, the overheads on the system will increase. Once the load increases beyond a certain point (that is, once an internal buffer fills up), data collection is temporarily suspended in order to prevent the load from increasing any further. As a result, there will be gaps in the transaction breakdown analysis data. If this happens, there will be gaps in the sequence of transaction IDs, which are normally numbered in ascending order. This can be checked by displaying collection data on the details tree. If gaps are found in the sequence of transaction IDs, this means that the measurement interval is too short, so review the settings.

Refer to "Interstage(TxnAnalysis)JavaEE/Interstage(TxnAnalysis) tree" in the User's Guide (Console Edition) for more information about transaction IDs.


Note

Please define not to overlap the Server Instance name of the Java EE environment and the work unit name of the J2EE environment.


1.1.3.1 Under the Java EE Environment

If "transaction breakdown analysis" is performed for IJServer cluster, make the following settings from the Interstage Java EE Admin Console or by executing asadmin command.


By executing set sub-command of asadmin command

Example of setup when the cluster name of the IJServer is "IJServer001", setting name is "IJServer001-config", and sampling frequency is "1000" is as follows.

  1. Enable transaction breakdown analysis

    asadmin set IJServer001-config.monitoring-service.module-monitoring-levels.property.ssqc-service=true
  2. Specify the sampling frequency (measurement interval)

    asadmin set IJServer001-config.monitoring-service.module-monitoring-levels.property.ssqc-interval=1000

The above-mentioned setting is done in each monitoring IJServer cluster.

Refer to Reference Manual (Command Edition) of the Interstage Application Server/Interstage Web Server for detailed information about asadmin command.


By using Interstage Java EE Admin Console

Make following settings from "Monitoring Service" page of the IJServer cluster to monitor.

  1. Enable transaction breakdown analysis

    Add following items as additional properties.

    • Name : ssqc-service

    • Value : true

  2. Specify the sampling frequency (measurement interval)

    Add following items as additional properties.

    • Name : ssqc-interval

    • Value : 1000 (when sampling frequency is "1000")

The above-mentioned setting is done in each monitoring IJServer cluster.

Refer to Operation Guide for Java EE of the Interstage Application Server/Interstage Web Server for detailed information about Interstage Java EE Admin Console.


1.1.3.1.1 Display

Transaction breakdown analysis information in a Java EE environment can be displayed using the following method.

Details

A separate node for each Server Instance is generated under the "Interstage(TxnAnalysis)JavaEE" node on the detailed tree. Selecting a Server Instance displays all of the transactions that have been executed by that Server Instance. By setting up transaction ID nodes, information can be displayed for each individual transaction. Refer to "Interstage(TxnAnalysis)JavaEE/Interstage(TxnAnalysis) tree" in the User's Guide (Console Edition) for more information.

Reports
  • Generic report


1.1.3.2 Under the J2EE Environment

If "transaction breakdown analysis" is performed for IJServer Work Units, make the following settings from the Interstage Management Console.

  1. Enable transaction breakdown analysis

  2. Specify the sampling frequency (measurement interval)

Refer to J2EE User's Guide in the Interstage Application Server/Interstage Web Server for more information about Interstage Management Console.


1.1.3.2.1 Display

Transaction breakdown analysis information in a J2EE environment can be displayed by following methods.

Summary

Information will be displayed by selecting following nodes in the Summary tree:

  • "Interstage(EJB)" node (Interstage(EJB)Monitor)

  • "Interstage(TD)" node (Interstage(TD)Monitor)

  • "Interstage(CORBA)" node (Interstage(CORBA)Monitor)

Details

A separate node for each Work Unit is generated under the "Interstage(TxnAnalysis)" node on the detailed tree. Selecting a Work Unit displays all of the transactions that have been executed by that Work Unit. By setting up transaction ID nodes, information can be displayed for each individual transaction. Refer to "Interstage(TxnAnalysis)JavaEE/Interstage(TxnAnalysis) tree" in the User's Guide (Console Edition) for more information.

Reports
  • Generic report