For Enterprise Vault to
access and index additional custom or standard MAPI properties on
Exchange Server messages, the properties must be defined in the
file Custom Properties.xml
, which you
create in the Enterprise Vault\Custom Filter
Rules
folder on the computer running the archiving tasks
enabled for custom filtering. The installed file, Enterprise Vault\Custom Filter Rules\Example Custom
Properties.xml
provides an example of this file.
The file has the following sections:
<CONTENTCATEGORIES></CONTENTCATEGORIES> This section defines available content categories. A content category is a group of settings that will be applied to an item when it is archived. This can include custom properties to index.
<CUSTOMPROPERTIES></CUSTOMPROPERTIES> This section defines the additional message properties that are to be available to Enterprise Vault.
<PRESENTATION></PRESENTATION> This section defines how the content categories and custom properties are displayed to users in external applications, such as the Enterprise Vault Web Access application browser search.
The following outline shows the general format of the file:
<?xml version="1.0"?> <CUSTOMPROPERTYMETADATA xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xsi:noNamespaceSchemaLocation="customproperties.xsd"> <!-- 1. DEFINITION OF CONTENT CATEGORIES AVAILABLE --> <CONTENTCATEGORIES> <CONTENTCATEGORY> ... </CONTENTCATEGORY> [<CONTENTCATEGORY> ... </CONTENTCATEGORY>] </CONTENTCATEGORIES> <!-- 2. DEFINITION OF CUSTOM PROPERTIES AVAILABLE --> <CUSTOMPROPERTIES> <NAMESPACE> ... </NAMESPACE> [<NAMESPACE> ... </NAMESPACE>] </CUSTOMPROPERTIES> <!-- 3. DEFINITION OF PRESENTATION PROPERTIES AVAILABLE --> <PRESENTATION> <APPLICATION> <FIELDGROUPS> <FIELDGROUP> ... </FIELDGROUP> [<FIELDGROUP> ... </FIELDGROUP>] </FIELDGROUPS> <AVAILABLECATEGORIES> <AVAILABLECATEGORY> ... </AVAILABLECATEGORY> [<AVAILABLECATEGORY> ... </AVAILABLECATEGORY>] </AVAILABLECATEGORIES> </APPLICATION> [<APPLICATION> ... </APPLICATION>] </PRESENTATION>
A summary description of all mandatory and optional elements and attributes in the file is provided in the following section:
See Table: XML elements and attributes in the Custom Properties.xml file.
Whenever you modify the file, you must restart the associated archiving tasks. In a distributed environment, you must copy the updated file to each computer with tasks enabled for custom properties, and then restart the associated tasks on each computer.
If the browser search is being used to search for custom properties, then the Enterprise Vault Application Pool in IIS Manager must also be restarted.
More Information