IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Excluding classes from instrumentation

Complete the following steps:

  1. Edit the configuration file DC_home/runtime/app_server_version.node_name.server_name/custom/toolkit_custom.properties to add the following new property:
    am.camtoolkit.gpe.customxml.exclude=excludes.xml

  2. Create the file excludes.xml in the same custom directory with the following content:
    <gpe>
      <bci>
        <classExcludes>
          <exclude>org.apache.struts.action.ActionServlet</exclude>
          <exclude>com.company.package.*</exclude>
        </classExcludes>
      </bci>
    </gpe>

  3. Add as many classes as needed.

  4. Restart the application server.

  5. To verify that the class has been excluded, look in toolkit.xml. It appears as follows:
    <classExcludes>
          <include>*</include>
          <include>org.eclipse.osgi.framework.adaptor.core.*</include>
          <exclude>com.company.class</exclude>
          <exclude>com.company.package.*</exclude>
          <exclude>com.sun.net.ssl.internal.ssl.JSA_RSAKeyFactory</exclude>
          <exclude>COM.rsa.jsafe*</exclude>
          <exclude>org.eclipse.osgi.*</exclude>
        </classExcludes>

    The toolkit.xml file contains runtime settings and it is refreshed every time the application server is restarted


Parent topic:

Create custom requests