Specifications

Enable the AR Agent to Monitor Java Applications
2. Use the AR Agent Publisher to generate an AR agent installation program:
a. Double-click ARAgentPublisher.exe to start it.
b. On the Welcome screen, select Generate an AR Agent Installation
Program and click Next.
c. At the warning message, click OK.
d. On the Software License Agreement screen, read the agreement and
click Yes.
e. On the Edit Controller Information screen, complete the fields and click
Next. (Click Help for assistance.)
f. On the Options for Agent Install screen, complete the fields and click
Next. (Click Help for assistance.)
g. On the Agent Extensions screen, select Install Application Event API
and Monitor Java Applications. This is necessary for extending your
Java runtime environment (JRE) installation with the AR Java hook.
h. In the Application Class Path field, enter one location in which the AR
Java hook should be installed and click Add. (The maximum path
length is 128 characters.) The recommended location is the
$JAVA_HOME\jre\lib\ext subdirectory. For example, if you want to
monitor Live Health and you normally install Live Health in
c:\LiveHealth, the application class path would be
c:\LiveHealth\client\jre\lib\ext. You can specify additional paths by
entering them one at a time or you can separate them using a semi-
colon (;).
i. Complete the remainder of the AR Agent Publisher screens, as
described in its online help, and generate the AR agent installation
program.
3. Install the AR agent by running the AR agent installation program on each
client system where users will use the target application.
4. Optionally, on each client system, use Windows Explorer to confirm the
following:
a. The file that contains the JavaHook classes, ARJavaHook.jar, should be
in the directory that you specified to the AR Agent Publisher, typically
the jre\lib\ext subdirectory of the JRE installation.
b. The ARAppEvent.dll file should be in the %system root%\SYSTEM32
directory, typically C:\WINNT\SYSTEM32.
5. Because the AR Java Hook classes need to be initialized before the Java
application you want to monitor starts, you need to modify one or more of
the following for each client installation:
 the application icon properties
 the .bat file for the application
Monitor Transactions in Java Applications 103