A configuration file is used to define what directories
the IFilter should index, and what information from each xml file
should be extracted to Index Server.
The configuration file is in XML format and supports
the Xpath syntax for specifying nodes and attributes. Click
here to see a sample file.
Directory Specific Configuration
-
separate configurations for each physical directory to be searched
-
automatically include all sub folders
-
specify
a default configuration for all directories that are not
explicitly identified
-
directory format supports normal file system paths
or UNC aliases
XPath syntax
-
configuration file supports Xpath syntax
for identifying property, content and linkedFile nodes
-
support recursive descent for specifying content nodes
Property Nodes
Property nodes are used to identify each item
in an XML file that should be emitted
to Index Server as a catalog property
Each
property node
definition supports the following attributes:
| Attribute |
|
| name |
friendly property name that will be listed in the Index
Server catalog
|
| type |
data type for the property. Supported types are string,
Boolean, float, double, dateTime, long, longArray, stringArray |
| Xpath |
a valid Xpath that will identify the node in the XML file
that contains the value to be emitted to Index Server |
Samples
<
property name=”DocId” type=”string” xpath=”/*/@DocID”/>
< property name= ”Created” type=”dateTime” xpath=”/*/Created”/>
Content Nodes
Content nodes are used to
identify each item in an XML file that should be emitted
to Index Server as contents (for full
text searches). Each content node requires a valid XPath attribute.
If the XPath
returns more than one node, the contents value emitted
to Index Server will be the text of all
returned nodes.
Samples
< content xpath=”//*”/>
< content
xpath=”/*/Title”/>
< content xpath=”/*/Abstract”/>
linkedFile Nodes
A linkedFile node is used to indicate
an item in an XML file that contains a reference
to an external file as its value.
When
the IFilter encounters one of these nodes, it will allow
the registered filter for
the specific file type to process the file and will emit
the results as contents of the source XML file. The external
file does not need
to be in the same path or sub-path as the XML file.
Each linkedFile
node definition supports the following attributes:
| Attribute |
|
| Xpath |
a valid Xpath that will identify the node in the XML file that contains
the path of the linked file |
| relativePath |
a Boolean setting that indicates whether the path to the linked
file is relative to the path of the source XML file |
Samples
< linkedFile xpath=”/*/ReferenceFile” relativePath=”false”>
< linkedFile
xpath=”/*/Links[@Id=’123’]/FileName” relativePath=”true”>
request more info