Disabling Auditing for Task Rules

About this task

Task rules execution can result in a large number of audit entries in the Task Audit table. Inspection of the Task Audit table indicates that for each task and global rule execution, a table entry of "Trigger Rule Fired mm/dd/yyyy hh:mm am|pm Trigger Rule (GlobalTaskEventRule)" is created. In systems with a large number of tasks running, this can result in an unwanted increase in size of the Task Audit table.

To avoid the Task Audit table issue, you can disable auditing for specified task and global task rules in a configuration file.

Note: You can also disable audit logging for tasks in a process. For more information, see Disable/Enable Task Logging in Processes.

To disable auditing for specific task and global rules

Procedure

Open the following file in a text editor:
IBMwebMethods_directory/mws/server/instance/config/auditDisabledRules.properties
Type the rule names as a comma separated string in the appropriate rule type line (change, routing, and schedule). For example:
```
change=ChangeRule1,ChangeRule2 
routing=AssignmentRule1 
schedule=ScheduleRule1,ScheduleRule2,ScheduleRule3
```
Note: Routing rules are more generally known as Assignment rules. To view the available task and global rules in IBM My webMethods Server: Navigate > Applications > Administration > Business > Tasks > Task Engine Administration. Click the appropriate global rule icon, or a task rules icon in the Actions column.

If no task or global rules are specified in this file, audit entries are created for all task and global rules.
Save the modified properties file and restart IBM My webMethods Server.

Results

For more information about task logging levels, see Configuring the Task Engine Logging Level.