Excluding Attributes From Logged Messages

You can exclude specific message attributes from being logged by defining a rule in the CONFIG_DATA\bpm\bpm_app_name\configuration\ec-probe-rules.xml file.

Prerequisites

Make a backup copy of the existing ec-probe-rules.xml file.

Procedure

  1. Open the ec-probe-rules.xml file in a text editor and, in the <messageProcessDefinitions> section, find the LocalLoggingProcess definition: 
            <messageProcessDefinitions>

            <messageProcessDefinition name="LocalLoggingProcess">
            </messageProcessDefinition>
  2. In this definition, add a new excludedAttributesList section, as follows: 
            <messageProcessDefinitions>

            <messageProcessDefinition name="LocalLoggingProcess">
                <excludedAttributesList>
                    <attribute>TEST</attribute>
                </excludedAttributesList>
            </messageProcessDefinition>
  3. Modify the new excludedAttributesList section, as follows:
    1. In the <attribute> tag, replace TEST with the Attribute Name of the attribute that you want to prevent from being logged.
    2. Add an additional <attribute> tag for each attribute that you want to prevent from being logged.
    For example, the following definition excludes the stackTrace attribute from being logged. 
            <messageProcessDefinitions>

            <messageProcessDefinition name="LocalLoggingProcess">
                <excludedAttributesList>
                    <attribute>stackTrace</attribute>
                </excludedAttributesList>
            </messageProcessDefinition>
  4. Save the modified ec-probe-rules.xml file when you are ready.
  5. Validate your changes to the ec-probe-rules.xml file using the TIBCO_HOME\bpm\version\bin\rulesinfo utility. For example: 
    rulesinfo validate -configdir C:\ProgramData\bpm1\tibco\data\bpm\amx.bpm.app\configuration

    See Using the rulesinfo Utility to Validate the Event Probe Rules and Event Rules Files for more information about the rulesinfo utility.

  6. Check the BPM log file to verify that your changes are working and having the desired effect on the logged information.