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 validating Custom Properties.xml
When Enterprise Vault is installed, customproperties.xsd
is placed in the Custom Filter Rules
folder. This is the XML schema for validating Custom Properties.xml
.
The schema file must be referenced in the CUSTOMPROPERTYMETADATA entry at the start of the Custom Properties.xml
file, as follows:
<?xml version="1.0"?> <CUSTOMPROPERTYMETADATA xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xsi:noNamespaceSchemaLocation="customproperties.xsd">
If the file contains non-ANSI characters, ensure the correct encoding is set on the first line and save the file using the appropriate encoding.
The XML is validated when the associated task starts processing messages. If anything is invalid, the task stops and you must correct any errors before restarting the task.
To avoid disrupting tasks because of syntactic errors, it is a good idea to validate your XML file before it is accessed by the tasks. You could use a third party tool, such as the graphical XML Editor in Liquid XML Studio:
http://www.liquid-technologies.com/XmlStudio/Free-Xml-Editor.aspx
When using the tool, specify the namespace as:
x-schema:customproperties.xsd
Note:
All the XML tags and predefined values shown in upper case in this document are case-sensitive and must be entered as upper case in the file. Values entered should also be treated as case-sensitive.