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
Summary of custom property elements and attributes
Table: XML elements and attributes in the Custom Properties.xml file summarizes all elements and attributes in Custom Properties.xml.
The value in the Mandatory column assumes that the IGNORENODEFAULT registry setting is not used.
Table: XML elements and attributes in the Custom Properties.xml file
Element | Attribute | Mandatory | Description |
|---|---|---|---|
CONTENTCATEGORIES | Yes | Defines the content category section of the file. | |
DEFAULT= | No | Value is the name of the content category to be used as default. Required if custom properties in all items are to be indexed. | |
CONTENTCATEGORY | Yes | Defines a group of settings that are to be assigned to an archived item. | |
NAME= | Yes | Value is a unique name to identify category to ruleset and presentation interface. | |
RETENTIONCATEGORY= | No | Value is a retention category to be assigned to the archived item. The retention category must exist in Enterprise Vault. | |
ARCHIVEID= | No | Value is the ID of the archive to store the item in. The value can be found in the properties of the archive in the Enterprise Vault Administration Console. | |
INDEXEDPROPERTIES | Yes | Defines a set of additional properties in the content category. | |
RETRIEVE= | No | Value is "Y" or "N". Indicates whether or not properties in this set should appear in the search results. The default is "N". | |
PROPERTY | Yes | Defines an additional property to index for items that are assigned this content category. | |
TAG= | Yes | Value is the Enterprise Vault TAG of the property. | |
CUSTOMPROPERTIES | Yes | Defines the custom property section of the file. | |
NAMESPACE | Yes | Defines a NAMESPACE that contains a group of custom properties. | |
TYPE= | Yes | Value is the type of property: "LOTUS". | |
PROPERTY | Yes | Defines a custom property. | |
NAME= | Yes |
Value is the identity of the property as displayed in message properties in the Notes client. Value must be unique in NAMESPACE. | |
LOTUSTYPE= | Yes | Value is the Domino property data type: "TEXT", "NUMBER" or "TIME". | |
TAG= | Yes | TAG identifies the property within Enterprise Vault. It must contain four or more alphanumeric characters (A-Z a-z 0-9); spaces and underscore characters are not permitted. The value must be unique within the XML file. TAG value is the property name that will be stored in the index. | |
PRESENTATION | Yes | Defines the presentation property section of the file. | |
APPLICATION | Yes | Defines a group of fields for use by a named application. | |
NAME= | Yes | Value is the name of the application that will use the fields in this definition. | |
LOCALE= | Yes | The value depends on what the calling application requires to define the language. For example, an application may use the standard Microsoft Locale ID number that the application runs under. | |
FIELDGROUPS | Yes | Define the field groups available to the application. | |
FIELDGROUP | Yes | A logical grouping of fields for the presentation interface. | |
LABEL= | No | Value will be presented to the application for this field group. The label must be unique within the application. | |
FIELD | Yes | Defines a field that will reference a custom property. | |
LABEL= | Yes | Value will be displayed on the application user interface to represent this custom property. | |
CATEGORY= | Yes | Value is the name of a content category listed in AVAILABLECATEGORIES for the application. | |
TAG= | Yes | Value is the TAG of a custom property. The tag must be unique in the FIELDGROUP. | |
AVAILABLECATEGORIES | Yes | Define which content categories are available to the application. | |
AVAILABLECATEGORY | Yes | Defines a content category. | |
LABEL= | Yes | Value defines how the content category is to appear in the user interface. | |
CONTENTCATEGORY= | Yes | Value is the NAME of the required content category as specified in the Content Category section of the file. |