Skip to end of metadata
Go to start of metadata

On this page:

Oracle GlassFish is an OSGi-based application container. Accordingly, you need to set configure class bootloader settings as well as load the Java Agent in the runtime JVM, as described here.  

Instrument Oracle GlassFish

  1. Add the location of the Java Agent JAR file as a -javaagent JVM option in the GlassFish domain. You can add the agent using the asadmin tool as follows:

    For Windows:

    glassfish4\bin\asadmin.bat create-jvm-options '-javaagent:<Drive_letter>:<agent_home>\javaagent.jar' 

    For Linux:

    glassfish4\bin\asadmin create-jvm-options "-javaagent\:/home/appduser/javaagent/javaagent.jar"

    Ensure you escape the colon character on Linux. 

  2. Configure the boot delegation entry for the AppDynamics package, as follows: 

    • In GlassFish 3.x through 3.1.2, open the config.properties file located at <glassfish_home>/glassfish/osgi/felix/conf and add the following package prefix to the config.properties file: 

    • In GlassFish 3.1.2 and later, in the boot delegation list in the <glassfish_home>/glassfish/config/osgi.properties file, add com.singularity.* 
      For example:

  3. Restart the application server.

To verify the configuration, look at the domain.xml file located at <glassfish_home>\domains\<domain_name>\config. The domain.xml file should have an entry for the -javaagent option. 

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.