How to exclude classes from being monitored using the excludes.xml file.

There may be times when you will need to exclude certain classes for instrumentation from your Request.  For example, you may need to be certain that your Request doesn't get re-formatted when sent to another server, say an authentication server for processing.   Here's how you can go about doing this.

1) Your first step is to do preweaving and postweaving, and then look at the preweave and postweave directories, and output logs.  This way, you can see the exact classes being used.

2) Next you will need to edit the configuration file {DC_home}/runtime/{app_server_version.node_name.server_name}/custom/toolkit_custom.properties and add this line to the file:

am.camtoolkit.gpe.customxml.exclude=excludes.xml

3) Create or modify the file excludes.xml in the same custom directory ({DC_home}/runtime/{app_server_version.node_name.server_name}/custom) with the following content.  (Note that this is just an example, replace the exclude lines shown below with your classes you want to exclude from step 1 above).

<gpe>   

<bci>   

<classExcludes>

  <exclude>psdi.*</exclude>

  <exclude>org.slf4j.*</exclude>

  <exclude>net.oauth.*</exclude>

  <exclude>com.ibm.ws.bootstrap.*</exclude>

      <exclude>com.ibm.ws.classloader.*</exclude>

      <exclude>com.ibm.ws.naming.*</exclude>

      <exclude>com.ibm.ws.persistence.*</exclude>

      <exclude>com.ibm.ws.rsadapter.*</exclude>

      <exclude>com.ibm.ws.sib.*</exclude>

      <exclude>com.ibm.ws.tcp.*</exclude>

   <exclude>com.ibm.ws.wim.*</exclude>

 </classExcludes>   

 </bci>   

 </gpe>

4) .Restart your configured JVM/server.   Then check the excluded classes results from the logs and verify they're being excluded.