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 the default filter rules file for custom filtering
The Domino archiving tasks use the rules defined in Default Filter Rules.xml
as the defaults for all provisioning groups and journaling locations. However, Default Filter Rules.xml
is not mandatory and you might choose to create only named ruleset files, which the Domino journaling tasks then apply to specific provisioning groups or journaling locations.
See About named ruleset files for individual Domino provisioning groups and journaling locations.
If you choose not to use Default Filter Rules.xml
, you must configure the IGNORENODEFAULT registry value.
See Ignoring the absence of default filter rules.
In this way, custom filtering is only applied to target locations explicitly defined by named ruleset files.
If you implement the custom properties feature, and want the same actions applied to all items that the archiving tasks process (that is, specific items are not selected for processing by matching attributes), you can omit ruleset files altogether and define a default content category in the file, custom properties.xml
.
Information on content categories and the custom properties.xml
file is provided in the following section: