Start Monitoring Java

AppDynamics Java Application Performance Monitoring provides end-to-end performance insights in the most complex and distributed environments. Within a few steps, you can get real-time visibility into how your applications perform inside many of the industry-leading Java application servers, including Weblogic, WebSphere, JBoss, Tomcat, Glassfish and more. With our Getting Started Wizard and Agent Installer, it takes only a few minutes to see the auto-discovered business transactions and application topology. If you need additional help, see our documentation.
Video Thumbnail
To monitor your application, you need:
  1. An AppDynamics account. If you don't have one, getting a SaaS Controller is easy. Just sign up for an account and start a trial. It's free - no credit card required.
  2. Access to the machine where the application runs. Verify you have a user account with privileges to install the agent software and restart the application.
  3. The machine where your application runs can access the Controller.
Once you sign up, you'll receive a welcome email with instructions on how to log on to your Controller. From there, the Getting Started Wizard under Home screen will guide you through the remaining steps.

You can see a list of Java Supported Environments here.
  1. Choose a JVM (Sun/JRockit or IBM) from the dropdown menu.
  2. In configure, connection information of current controller is automatically populated so you don't need to change anything. If you want to use a different controller to monitor your application, edit the controller Url and port. 
  3. Select whether or not to enable SSL.
In AppDynamics, each environment is modeled in Application -> Tier -> Node hierarchies:
  • Application: A business application is the top-level container in the AppDynamics model. A business application contains a set of related services and business transactions. You can have a single application or divide it into several applications to reflect work teams in your organization.
  • Tier: Business applications contain tiers, the unit in the AppDynamics model that collects one or more nodes. You may choose to group identical nodes into a single tier based on the mental model of your environment. Remember, there is no interaction among nodes within a single tier and each node cannot belong to more than one tier.
  • Node: A node is the smallest unit of the modeled environment. In general, a node corresponds to an individual application server, JVM, or CLR on which you have installed an AppDynamics agent. 
Set up application and tier based on your environment. You can choose to use an existing application/tier or create a new one. 
Download the Agent installer and modify the start script to start with AppDynamics.

For exact instructions on how to start your application server, choose from the drop down menu and follow the documentation.
Once application is restarted, it will take about 2-3 minutes for the agent to connect. 

Generate load to the application.  

When both lines are green, click continue to proceed. You've successfully instrumented your Java Application.
https://vimeo.com/161248747

Introduction

AppDynamics Java Application Performance Monitoring provides end-to-end performance insights in the most complex and distributed environments. Within a few steps, you can get real-time visibility into how your applications perform inside many of the industry-leading Java application servers, including Weblogic, WebSphere, JBoss, Tomcat, Glassfish and more. With our Getting Started Wizard and Agent Installer, it takes only a few minutes to see the auto-discovered business transactions and application topology. If you need additional help, see our documentation.

Before starting

To monitor your application, you need:
  1. An AppDynamics account. If you don't have one, getting a SaaS Controller is easy. Just sign up for an account and start a trial. It's free - no credit card required.
  2. Access to the machine where the application runs. Verify you have a user account with privileges to install the agent software and restart the application.
  3. The machine where your application runs can access the Controller.
Once you sign up, you'll receive a welcome email with instructions on how to log on to your Controller. From there, the Getting Started Wizard under Home screen will guide you through the remaining steps.

You can see a list of Java Supported Environments here.

Select JVM and configure

  1. Choose a JVM (Sun/JRockit or IBM) from the dropdown menu.
  2. In configure, connection information of current controller is automatically populated so you don't need to change anything. If you want to use a different controller to monitor your application, edit the controller Url and port. 
  3. Select whether or not to enable SSL.

Set Application and Tier

In AppDynamics, each environment is modeled in Application -> Tier -> Node hierarchies:
  • Application: A business application is the top-level container in the AppDynamics model. A business application contains a set of related services and business transactions. You can have a single application or divide it into several applications to reflect work teams in your organization.
  • Tier: Business applications contain tiers, the unit in the AppDynamics model that collects one or more nodes. You may choose to group identical nodes into a single tier based on the mental model of your environment. Remember, there is no interaction among nodes within a single tier and each node cannot belong to more than one tier.
  • Node: A node is the smallest unit of the modeled environment. In general, a node corresponds to an individual application server, JVM, or CLR on which you have installed an AppDynamics agent. 
Set up application and tier based on your environment. You can choose to use an existing application/tier or create a new one. 

Download and install

Download the Agent installer and modify the start script to start with AppDynamics.

For exact instructions on how to start your application server, choose from the drop down menu and follow the documentation.

Wait for connection and load

Once application is restarted, it will take about 2-3 minutes for the agent to connect. 

Generate load to the application.  

When both lines are green, click continue to proceed. You've successfully instrumented your Java Application.