Network Deployment (Distributed operating systems), v8.0 > Monitor > Monitor application flow > Get performance data from request metrics
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 WAS 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 your own ARM implementation providers to obtain the ARM implementation libraries. Follow the instruction from the ARM provider, and ensure that the ARM API 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 WAS_HOME/lib directory, which is the WAS installation root directory. If the underlying ARM implementation is ARM 4.0, you need to specify the ARM transaction factory class name. Otherwise, this specification is not required.
See the Performance: Resources for learning information about the ARM specifications.
ARM application properties and transaction context data
Get performance data from request metrics
Performance: Resources for learning