AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    27 rates

    You can instrument the webMethods Integration Server or My webMethods Server by adding the Java Agent to the startup script of the server.

    The Java agent settings can go in the runtime.bat/runtime.sh file or the server.bat/server.sh file under the bin subdirectory of the server home.

    Instrumenting webMethods with the Tanuki Wrapper

    For webMethods servers that use the Tanuki Java service wrapper for start-up, you need to configure the agent in the wrapper.conf file.

    Note that the order of arguments in the file is important. Specifically, when instrumenting an OSGI-based platform, the agent configuration must precede the bootclasspath argument. 

    For example, the following listing shows the Java options used in a sample wrapper.conf file:

    # Java Additional Parameters
    ...
    wrapper.java.additional.4=-XX:MaxPermSize=256M 
    wrapper.java.additional.5=-javaagent:/opt/appd/appagent/javaagent.jar
    wrapper.java.additional.6=-Xbootclasspath/a:"%OSGI_INSTALL_AREA%/lib/runtime/platform-jaasproxy.jar"