AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

Skip to end of metadata
Go to start of metadata

To load the Java Agent in Mule ESB, pass the Java Agent JAR location as a JVM argument to Mule.

Mule ESB 3.X or later uses the Tanuki configuration environment. To specify JVM arguments in your Mule ESB environment, you need to configure them as additional parameters to the Tanuki Java Service Wrapper configuration file, wrapper.conf, as described below.  

To configure the Tanuki Service Wrapper

  1. Open the Java Service Wrapper configuration file: 
    <MULE_HOME>/conf/wrapper.conf  
  2. Find the location indicated for Java Additional Parameters:

    # Java Additional Parameters
    wrapper.java.additional.1=
  3. Add the path to the Java Agent JAR file as a JVM argument using a wrapper.java.additional.n parameter, as follows.

    wrapper.java.additional.n="-javaagent:/path_to_appagent/javaagent.jar"
    wrapper.java.additional.n.stripquotes=TRUE

    Where "n" is the next available integer among the wrapper.java.additional parameters already in the wrapper.conf file, if any. The numbers serve to identify each Java Additional Parameter in the file. Do not skip numbers when adding the property. Replace path_to_appagent to the path to the javaagent.jar file in your system. The stripquotes parameter is necessary only if there are spaces in the path or filename, but is safe to include if not. 

    For example, on a Linux system and with seven Java parameters already in the file, add the following properties: 

    wrapper.java.additional.8="-javaagent:/opt/AppDynamics/Agent/app_agent/javaagent.jar"
    wrapper.java.additional.8.stripquotes=TRUE


    Note: There may be additional wrapper.java.additional properties defined in other Mule files. These are generated by the system. As indicated by comments preceding these properties, you should not make changes directly to the properties. Mule automatically auto-increments the index number for these properties based on the highest integer number used in wrapper.conf, so you do not need to modify or otherwise account for the index numbers of auto-generated configuration properties.

Learn More

  • No labels

2 Comments

  1. Unknown User (michael.mcdowell@appdynamics.com)

    This example will not work as presented:

    1. There cannot be two AppDynamics -javaagent definitions in one application startup.
    2. The example also shows unmatched double quotes on both javaagent lines
    3. The line: wrapper.java.addional.stripquotes=TRU (should be TRUE)

    In our case on RHEL, the combination which worked was 

    wrapper.java.additional.X="-javaagent:/opt/AppDynamics/Agent/app_agent/javaagent.jar"

    wrapper.java.additional.X.stripquotes=TRUE

    ... where X = 8.

    One final point, there might be another place where wrapper.java.additional values are defined, but these will be auto-generated by the application. Don't make changes to these, Mule is smart enough to auto-increment their indeces based on the highest integer used in the wrapper.conf. You will know that you are in the wrong place when there's a comment immediately before those arguments instructing you to not make changes directly to them.

    1. Thanks, Michael. I've updated the page based on your feedback.