Mule ESB Startup Settings

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.

Configuring 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.
    Note: If you are using the following processors, End User Monitoring (EUM) might not work as expected. This happens because Mule interferes with the Splunk AppDynamics headers.
    <custom-processor class="com.mulesoft.gateway.extension.ProxyRequestHeadersProcessor" />
<custom-processor class="com.mulesoft.gateway.extension.ProxyResponseHeadersProcessor" />