Veritas Enterprise Vault™ Setting up Domino Server Archiving
- About this guide
- Setting up Domino mailbox archiving
- Preparation for Domino mailbox archiving
- Configuring Domino targets, tasks and policies in Enterprise Vault
- Adding Domino Server archiving targets
- Configuring mailbox policies for Domino mailbox archiving
- Using customized shortcuts for Domino mailbox archiving
- Configuring desktop policies for Domino mailbox archiving
- Adding a Provisioning Group when setting up Domino mailbox archiving
- Installing Enterprise Vault extensions for Notes and DWA clients
- About Enterprise Vault clients for Notes and DWA clients
- Granting Execution Control List permissions when setting up Notes and DWA clients
- Changes made by EVInstall.nsf when setting up Domino mailbox archiving
- How to edit automatic messages after installing Domino mailbox archiving
- Setting up a Vault Cache for offline users
- Setting up Domino Journaling archiving
- How to configure clients when setting up Domino Journal archiving
- Configuring filtering
- Configuring custom filtering
- Configuring registry settings for Domino custom filtering
- About custom filtering ruleset files
- About controlling default custom filtering behavior
- About the general format of ruleset files for custom filtering
- About rule actions for custom filtering
- About message attribute filters for custom filtering
- About the general format of Custom Properties.xml
- About content categories
- Defining how custom properties are presented in third party applications
About custom filtering ruleset files
Custom filter rules and actions are defined in XML ruleset files. Each ruleset file contains one or more rules with associated actions.
Each rule contains the following:
A set of one or more attribute filters for evaluating each item that the archiving task processes. The order of attribute filters in a rule is not significant, all the attribute filters are evaluated.
An action to be applied to an item that matches all the attribute filters in the rule. Examples of actions are applying a particular retention category or storing the item in a specified archive. More than one action can be applied to matching items.
Although the order of the attribute filters in a rule is not significant, the order of the rules in the ruleset file is significant. The rules are evaluated in the order in which they appear in the file. The action associated with the first matching rule is applied to the item, and no further rules are evaluated for that item. If none of the rules match the item, the default action is to archive the item.
By default items that do not match any rules are archived by the mailbox archiving task or the journal archiving task. If you want to archive only items that match a rule, you can create a catch-all rule as the last rule in the ruleset file. Assign the action "MARK_DO_NOT_ARCHIVE" to this last rule.
While developing and testing your filter, we strongly advise that you assign the action "MARK_DO_NOT_ARCHIVE" to your rules. Check that the rules are applied exactly as you expect before changing them to the actions that you want to use in your production environment.
All ruleset files must be available in the folder Custom Filter Rules
in the main Enterprise Vault folder (for example C:\Program Files (x86)\Enterprise Vault
) on the computer hosting the archiving tasks that are enabled for custom filtering.
After Enterprise Vault has been installed, this folder contains the following XML files:
Example Filter Rules.xml
- This provides examples of filter rules.ruleset schema.xdr
- This contains the XML schema for validating the XML ruleset files.Example Custom Properties.xml
- This provides example entries for the custom properties.xml file.customproperties.xsd
- This contains the XML schema for validating the custom properties XML file.
When you create ruleset files or modify existing ruleset files, you must restart the associated archiving tasks before the changes take effect. In a distributed environment, you must copy the updated file to each computer with tasks enabled for custom filtering, and then restart the associated tasks on each computer.
Note:
If you create rules to match names that contain special characters, you must save the XML ruleset files with Unicode encoding.
More Information