ManageEngine® Applications Manager Web Transaction Agent |
||
J2EE Web Transaction Monitor requires an agent to be plugged in the application server (like JBoss, Tomcat) to be monitored. Follow the steps given below to deploy the agent:
Copy the WebTransactionAgent.jar present under <ApplicationsManagerHome>/working/resources to a local directory in the Application server (like JBoss, Tomcat).
Edit the startup script of the application server (like JBoss, Tomcat)
and add the below command line option to the java runtime environment
-javaagent:<Path to the WebTransactionAgent.jar>
Restart the Application server (like JBoss, Tomcat).
For e.g., To enable J2EE Web Transaction Monitor in JBoss application Server, do the following :
Copy the J2EE web transactions agent(WebTransactionAgent.jar) under <ApplicationsManagerHome>/working/resources to a local directory of the server where JBoss is installed.
Edit the run.sh/bat under JBoss home/bin. Append the following command
to JAVA_OPTS
JAVA_OPTS =-javaagent:<Path to the WebTransactionAgent.jar>
Restart JBoss.
By default, only the standard J2EE classes are instrumented for performance metrics. This includes Servlet, JSP, EJB and JDBC classes. In order to collect metrics for the user's Java classes the <wta.props> file needs to be configured.
J2EE Web Transaction Agent Configuration
To configure the wta.props file in your Application Server, add -Dam.wtaconf.dir
=<directory in which the wta.props file is present> in
JAVA_OPTS . A sample wta.props file is present under <AppManager10/working/conf> |
Note: This file should be used juditiously because unwanted packages selected for instrumentation will create additional performance overhead on the system. |
Note: |
See Also
Creating New Monitor - J2EE Web Transactions Monitor
J2EE Web Transactions Monitoring |
J2EE Web Transaction Metrics |