Distribución de RDD según meses
CONCLUSIONES Y RECOMENDACIONES
The Enterprise Vault browser search application uses the custom filter and properties API to access custom properties defined in theCustom Properties.xml
file.
This section shows how the example presentation section entries would be displayed in the US English version of this application.
Figure 7-2shows the Enterprise Vault browser search with the example custom properties and content categories displayed.
Figure 7-2 Example presentation properties displayed in the browser search page
The Content Category dropdown box shows the content categories available to be used in searches. These were defined using the <AVAILABLECATEGORIES> element. You can change the content categories listed in the dropdown box, but you cannot change or hide the label, Content Category.
Selecting a content category in the box and clicking Search will return all items that were archived with the selected content category.
The Case Properties and Client Properties sections display each group of custom properties (FIELDGROUP) associated with the selected content category. Entering a value for a custom property and clicking Search will search the custom property index entry of archived items.
To see the additional property details in the search results, Details must be set to Full.
If the user selects a different content category, the custom properties available will change.
As RETRIEVE="Y" was set in the definition of the Litigation content category, and Details was set to Full on the Search page, custom properties in search result items will be displayed at the end of the list of normal message attributes.
Figure 7-3 Custom properties displayed in search results
Note the following on displaying custom properties in browser search:
■ You must include the LOCALE attribute.
■ If custom properties are to be used in the Enterprise Vault browser search, Internet Explorer security settings must allow cookies for the Enterprise Vault server site.
■ When changes are made to the custom property configuration, you need to restart the Enterprise Vault Application Pool in IIS Manager.
■ If the contents of theCustom Properties.xmlfile is changed, searches may return different results. For example, if an item is indexed using one content category and the properties included in the content category are changed, the custom properties returned by subsequent searches will be different. To ensure you can still search on the original properties, leave the original content category and create a new one.
Summary of custom property elements and attributes
Table 7-3summarizes all elements and attributes inCustom Properties.xml.The value in the Mandatory column assumes that the IGNORENODEFAULT registry setting is not used.
Table 7-3 XML elements and attributes in the Custom Properties.xml file
Description Mandatory
Attribute Element
Defines the content category section of the file.
Yes CONTENTCATEGORIES
Value is the name of the content category to be used as default. Required if custom properties in all items are to be indexed.
No DEFAULT=
Defines a group of settings that are to be assigned to an archived item. Yes
CONTENTCATEGORY
Value is a unique name to identify category to ruleset and presentation interface.
Yes NAME=
Value is a retention category to be assigned to the archived item. retention category must exist in Enterprise Vault.
No RETENTIONCATEGORY=
Value is the ID of the archive to store the item in. Value can be found in the properties of the archive in the Enterprise Vault Administration Console.
No ARCHIVEID=
Defines a set of additional properties in the content category.
Yes INDEXEDPROPERTIES
Value is "Y" or "N". Indicates whether or not properties in this set should appear in the search results. Default is "N".
No RETRIEVE=
Defines an additional property to index for items that are assigned this content category.
Yes PROPERTY
Value is the Enterprise Vault TAG of the property.
Yes TAG=
Defines the custom property section of the file.
Yes CUSTOMPROPERTIES
Defines a NAMESPACE that contains a group of custom properties. Yes
Table 7-3 XML elements and attributes in the Custom Properties.xml file (continued) Description Mandatory Attribute Element
Value is the type of property: "LOTUS".
Yes TYPE=
Defines a custom property. Yes
PROPERTY
Value is the identity of the property as displayed in message properties in the Lotus Notes client.
Value must be unique in NAMESPACE.
Yes NAME=
Value is the Domino property data type: "TEXT", "NUMBER" or "TIME". Yes
LOTUSTYPE=
TAG identifies the property within Enterprise Vault. It can contain only 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. Yes
TAG=
Defines the presentation property section of the file.
Yes PRESENTATION
Defines a group of fields for use by a named application.
Yes APPLICATION
Value is the name of the application that will use the fields in this definition.
Yes NAME=
The value depends on what the calling application requires to define the language. The Enterprise Vault browser search uses standard Microsoft Locale ID number that the application will run under. (Currently only "1033", US English, is supported for displaying custom properties in the browser search.) Yes
Table 7-3 XML elements and attributes in the Custom Properties.xml file (continued) Description Mandatory Attribute Element
Define the field groups available to the application.
Yes FIELDGROUPS
A logical grouping of fields for the presentation interface.
Yes FIELDGROUP
Value will be presented to the application for this field group. The label must be unique within the application.
No LABEL=
Defines a field that will reference a custom property.
Yes FIELD
Value will be displayed on the application user interface to represent this custom property. Yes
LABEL=
Value is the name of a content category listed in
AVAILABLECATEGORIES for the application.
Yes CATEGORY=
Value is the TAG of a custom property. The tag must be unique in the FIELDGROUP.
Yes TAG=
Define which content categories are available to the application. Yes
AVAILABLECATEGORIES
Defines a content category. Yes
AVAILABLECATEGORY
Value defines how the content category is to appear in the user interface.
Yes LABEL=
Value is the NAME of the required content category as specified in the Content Category section of the file. Yes
A
Advanced desktop policy settings Domino archiving 33 Advanced mailbox policy settings
Domino mailbox archiving 27
C
Content categories introduction 74 Custom filtering
assigning archive 87
assigning retention category 86 configuring 77
default rules 82
Domino registry settings 79 filtering messages 87 filtering on DLs 89–90
filtering on message direction 95 filtering on message subject 97 format of ruleset files 83 introduction 73
named ruleset files 83 registry settings 78 rule actions 85 ruleset file example 98 ruleset file schema 82 ruleset file security 82 ruleset files 81 Custom properties introduction 74 supported properties 103 Custom properties.xml introduction 75 schema 82 Customized filters 104
D
Desktop policiesDomino mailbox archiving 31
Domino archiving adding a domain 22
adding a Domino mail server 22 Domino Journaling
adding a domain 66 adding a location 69 adding a server 66
adding permissions to the journal archive 68 assigning a vault store 66
creating a task 69 creating a vault store 67 creating an archive 67
using DominoJournalingTemplates 69 Domino Journaling Archiving 65
set up 68
Domino journaling location 79 Domino journaling locations
ruleset file name 83 Domino mailbox archiving
desktop policies 31 Domino Mailbox task 35 Domino Provisioning task 34 installing client templates 39 mailbox policies 23
setting up 15
Domino retention folders 30 Domino retention plan 30
XML file 30 DominoHubServers 23
E
enabling Domino mailbox manually 58 enabling mailbox wizard 57 EVDominoRetentionPlans.exe 30 EVMessages.nsf 55
F
Filtering Custom filtering 73I
INCLUDES and ALLOWOTHERS operators 91 Internal addresses Defining 96 InternalSMTPDomains 97
M
mailbox enabling manually 58 Mailbox policiesDomino mailbox archiving 23 Message classes 27
N
.NET Framework requirement 74
R
Retention folders, Domino 30 Retention plan, Domino 30 Ruleset file schema 85 Ruleset files introduction 74
S
Site Settings reviewing 35V
Vault Store name valid characters 67W
Welcome message editing 55 location of 55 wizardsEnable Domino mailboxes for archiving 58
X
XML file