Application Response Measurement

Request metrics information might be either saved to the log file for later retrieval and analysis, be sent to Application Response Measurement (ARM) agents, or both. Request metrics provides response time for each of the major WebSphere Application Server components through ARM APIs.

ARM is an Open Group standard. Request metrics helps you to plug in an ARM agent to collect response time measurements.

WAS does not ship an ARM agent. However, it supports the use of agents adhering to ARM 4.0 and ARM 2.0 standards.

We can choose our own ARM implementation providers to obtain the ARM implementation libraries. Follow the instruction from the ARM provider, and ensure that the ARM API Java archive (JAR) files found in the ARM provider are on the class path so that the WAS can load the needed classes. In the case of Tivoli Monitoring Transaction Performance, V5.3, copy the armjni.jar and core_util.jar files from the Tivoli Monitoring Transaction Performance <tmtp_install_root>/lib installation root directory to the app_server_root/lib directory, which is the WAS installation root directory. If the underlying ARM implementation is ARM 4.0, specify the ARM transaction factory class name. Otherwise, this specification is not required.

See the Performance: Resources for learning information about the ARM specifications.

Subtopics

• ARM application properties and transaction context data
  Request metrics provides build-in instrumentation to monitor transaction flows. The data that is collected by request metrics can be sent to a supported Application Response Measurement (ARM) agent.

Getting performance data from request metrics

Performance: Resources for learning