Veritas Enterprise Vault™ Setting up Domino Server Archiving
- About this guide
- Setting up Domino mailbox archiving
- About Domino mailbox archiving
- Preparation for Domino mailbox archiving
- Configuring Domino targets, tasks and policies in Enterprise Vault
- Checking the list of Domino forms
- Adding Domino Server archiving targets
- Configuring mailbox policies for Domino mailbox archiving
- General tab (Domino mailbox archiving)
- Archiving Rules tab (Domino mailbox archiving)
- Archiving Actions tab (Domino mailbox archiving)
- Shortcut Content tab (Domino mailbox archiving)
- Forms tab (Domino mailbox archiving)
- Shortcut Deletion tab (Domino mailbox archiving)
- Advanced tab (Domino mailbox archiving)
- Targets tab (Domino mailbox archiving)
- Using customized shortcuts for Domino mailbox archiving
- Domino mailbox archiving retention folders
- Configuring desktop policies for Domino mailbox archiving
- Creating a Domino Provisioning task
- Creating a Domino Mailbox task
- Reviewing the default settings for the Enterprise Vault site
- 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
- Installing Enterprise Vault client extensions for Notes and DWA clients
- Setting up an account to use EVInstall.nsf to set up an Enterprise Vault Domino Gateway
- Setting up an account to use EVInstall.nsf to set up a mail server
- Granting Execution Control List permissions when setting up Notes and DWA clients
- Installing the Notes and DWA client extensions
- Changes made by EVInstall.nsf when setting up Domino mailbox archiving
- Updating mail files with the new design after installing the Notes and DWA extensions
- How users access Enterprise Vault Search features after installing the Notes and DWA extensions
- Identifying internal Notes mail recipients
- How to edit automatic messages after installing Domino mailbox archiving
- Enabling mailboxes for archiving after installing Domino mailbox archiving
- Setting up a Vault Cache for offline users
- Setting up Domino Journaling archiving
- Preparation for Domino Journaling archiving
- Adding a Domino domain
- Adding a Domino server
- Assigning a vault store for Domino Journaling
- Creating a Domino Journal archive
- Adding permissions to the Domino journal archive
- Creating a Domino Journal policy
- Creating a Domino Journaling task
- Adding a Domino Journaling location
- Identifying internal Notes mail recipients
- How to configure clients when setting up Domino Journal archiving
- Configuring filtering
- About 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
- Message author and recipients filters for custom filtering
- About distribution lists in attribute values with custom filtering
- About creating complex filters using the INCLUDES and ALLOWOTHERS operators
- Message direction filters for custom filtering
- Message subject filters for custom filtering
- Domino named property filters for custom filtering
- Example ruleset file for custom filtering
- Configuring custom properties and content categories
- About the general format of Custom Properties.xml
- Defining additional Domino message properties in custom properties
- About content categories
- Defining how custom properties are presented in third party applications
- Summary of custom property elements and attributes
About content categories
In the <CONTENTCATEGORIES> section of Custom Properties.xml, you define the content categories that you want to apply to filtered messages.
A content category defines a group of settings that are to be applied to an item when it is archived.
The settings can include the following:
The retention category to assign to the item
The destination archive
A list of the additional message properties that Enterprise Vault is to index
There can be more than one content category defined in the <CONTENTCATEGORIES> element.
In ruleset files, the actions associated with a rule can include assigning a particular content category to messages that satisfy the rule. The content category definition in Custom Properties.xml provides the default settings for the content category. Some of these can be overridden for particular rules.
The following example shows entries for a content category called Litigation:
<!-- 1. DEFINITION OF CONTENT CATEGORIES AVAILABLE -->
<CONTENTCATEGORIES DEFAULT="Litigation">
<CONTENTCATEGORY NAME="Litigation" RETENTIONCATEGORY="Litigation"
ARCHIVEID="15165263832890493848568161647.server1.local">
<INDEXEDPROPERTIES RETRIEVE="Y">
<PROPERTY TAG="CaseAuthor"/>
<PROPERTY TAG="CaseStatus"/>
</INDEXEDPROPERTIES>
</CONTENTCATEGORY>
</CONTENTCATEGORIES><CONTENTCATEGORIES></CONTENTCATEGORIES> defines the content category section in the file.
The DEFAULT attribute specifies the content category to be used as the default. This default applies to all types of archiving enabled for custom filtering.
This attribute is optional, if custom filtering is used, but mandatory if there are no ruleset files (unless the registry setting IGNORENODEFAULT is configured).
If filters are configured in ruleset files and a default content category is specified, any item that does not match any rules will be archived according to the settings in the default content category. If no default content category is specified, then a content category will only be applied to an item if specified by a matching rule in a filter ruleset file.
If no applicable ruleset files exist, then you must specify a default content category using the DEFAULT attribute in the <CONTENTCATEGORIES> element in
Custom Properties.xml. The settings in the content category are then applied to all messages archived (unless the registry setting IGNORENODEFAULT is configured).The actions of archiving tasks are determined by combinations of ruleset files, custom properties, content categories and the registry setting IGNORENODEFAULT.
The <CONTENTCATEGORY> element defines a particular content category. There must be at least one content category defined.
The content category NAME is used to identify this content category in the presentation section of the file, rules in custom filter ruleset files and external subsystems, such as the Enterprise Vault Indexing service. The name must have at least five characters, which can include alphanumeric characters only (A-Z a-z 0-9); space and underscore characters are not permitted.
If the content category is included in the presentation section of the file, it will be possible to search on the content category name in order to find all items archived using this particular content category.
RETENTIONCATEGORY is optional and enables you to assign a retention category to each item archived using this content category. The retention category must already exist in Enterprise Vault.
ARCHIVEID is optional and enables you to specify a destination archive for the item. The archive must exist and be enabled. To find the ID of an archive, display the archive properties in the administration console and click the "Advanced" tab.
The <INDEXEDPROPERTIES> element is mandatory and groups the additional properties that Enterprise Vault is to index.
The RETRIEVE attribute (optional) determines whether or not the defined properties should be returned with archive search results. By default, the properties are not displayed with search results (RETRIEVE="N").
A <PROPERTY> element is required for each additional property to be indexed.
The TAG value must match the associated Enterprise Vault TAG value specified in the custom properties section.
See Defining additional Domino message properties in custom properties.