Specifications

Chapter 9: Monitor Transactions in Java
Applications
If your Java applications or applets were developed using Java 2 Platform,
Standard Edition (J2SE) 1.2 and later or Oracle's JInitiator 1.2 and later,
Application Response captures more than just object IDs and Windows
classes; it captures parameters that are specific to Java such as invocation of
a Java application, text titles in a Java window, and the addition or removal of
a Java component to or from a container. To allow Application Response to
monitor these applications: you must publish AR agents that are enabled to
monitor Java. Then you can write rules that recognize transactions based on
Java-specific events.
Java Application Example
A customer service organization wants to track the speed with which customer
service representatives can open a customer account summary using the Java
application that is the interface to the customer database. To monitor the
response times of opening account summaries, Application Response needs to
be able to recognize when the status message changes from "Update in
progress..." to "Done." To do this, you define a transaction that begins when
the label on a Java component is "Update in progress..." and ends when the
label on the same Java component is no longer "Update in progress...".
With the AR agent and AR Java hook installed on the system, the customer
service representative starts the AR agent. Then the representative starts the
Java application. If configured correctly, the AR Java hook and the Java
application start and use the same Java runtime environment. The AR Java
hook starts the JNI API through which Java events are sent to the AR agent.
Java Applet Example
A major insurance company spent several years developing a home-grown
Java applet that allows salespeople in the field to perform quotes and collect
premiums. The company wants to track the time to login response time
because their threshold is shorter than the login threshold for other types of
users. With the AR agent installed and running on the system, a salesperson
opens a browser window and launches the Web page that will download the AR
Java hook. The browser asks for permission to download and run the AR Java
hook applet.
If the salesperson grants permission, the browser starts a Java virtual machine
process in which the AR Java hook applet runs. The AR Java hook applet starts
a JNI API through which Java events are sent to the AR agent. The
salesperson then starts the home-grown sales applet. Because the AR Java
Monitor Transactions in Java Applications 101