GlassFish Startup Settings

The Java Agent bootstraps using the javaagent command line option.

To add the javaagent command in a GlassFish 3.0 environment

1. If you are using GlassFish v3.0, first configure the OSGi containers. For details see OSGi Infrastructure Configuration.

2. Log into the GlassFish domain where you want to install the Java Agent.

3. In the left navigation tree Common Tasks section, click Application Server. The Application Server Settings dialog opens.

4. In the JVM Settings tab, click JVM Options.

5. Click Add JVM Option and  add an entry for the javaagent argument. The javaagent argument contains the full path, including the drive, of the Java Agent installation directory.

-javaagent:<drive>:\<agent_home>\javaagent.jar

If you are a Self-Service Trial user, add the Java Agent javaagent argument to your JVM start script where <my-app-jvm1> is the name you use for the application running on that JVM.

-javaagent:<drive>:\<agent_home>\javaagent.jar=uniqueID=<my-app-jvm1>

6. Restart the application server. The application server must be restarted for the changes to take effect.

To add the javaagent command in a GlassFish 3.1 environment

1. If you are using GlassFish v3.1, first configure the OSGi containers. For details see OSGi Infrastructure Configuration.

2. Log into the GlassFish domain where you want to install the Java Agent.

Note: Remember to turn on remote administration by entering the following command from the <Controller_home>/appserver/glassfish/bin directory:

asadmin enable-secure-admin

3. In the Configurations section in the left navigation tree, click server-config and then click JVM Settings.

4. On the JVM Settings tab, click JVM Options.

5. Click Add JVM Option and add an entry for the javaagent argument as follows:

For Windows:

-javaagent:<Drive Letter>:<agent install location>\javaagent.jar

For Linux:

-javaagent:<agent install location>/javaagent.jar

If you are a Self-Service Trial user, add the Java Agent javaagent argument to your JVM start script where <my-app-jvm1> is the name you use for the application running on that JVM.

-javaagent:<drive>:\<agent_home>\javaagent.jar=uniqueID=<my-app-jvm1>

6. Restart the application server. The application server must be restarted for the changes to take effect.

To verify the Agent configuration

To verify this configuration, look at the domain.xml file located at <glassfish_install_dir>\domains\<domain_name>. The domain.xml file should have an entry as shown in the following screenshot.

About Glassfish AMX Support

AppDynamics supports Glassfish AMX MBeans.

Set the boot-amx node property to enable AMX MBeans. See boot-amx.

You will see the AMX domain in the MBean Browser in the JMX tab of the node dashboard.