Network share indexing
We will present here a simple example of indexing a network share.
Configuration
Indexing class
com.axemble.axvdocsearch.extensions.base.implementation.BaseFileIndexExtension
Custom Tags « system »
CustomTag | Description | Type |
---|---|---|
ID | text | |
REFERENCE | text | |
FILE | Content of the indexed file | file |
FOLDER | This is a tree custom tag that corresponds to the path of the folder containing the indexed file | text (tree) |
SIZE | The size of the indexed file | number |
EXTENSION | The extension of the indexed file (.txt, .doc, .docx, …). | text |
Required input parameters
Parameter Name | Description |
---|---|
FOLDER_PATH | Path to the root folder of the items to be indexed. The system will browse the subfolders and files. |
An example of a XML configuration
Let’s say a network share: \\server\users_data\
Here is a possible XML configuration:
<index name="IndexUsersData"
label="LG_IndexUsersData"
controller="com.axemble.axvdocsearch.core.controllers.implementation.LuceneController"
extension="com.axemble.axvdocsearch.extensions.base.implementation.BaseFileIndexExtension"
indexStorePath="vdocsearch\IndexUsersData"
updateOnIndexedDocuments="true"
locales="fr" >
<parameters>
<parameter key="FOLDER_PATH" value="\\server\users_data\" />
</parameters>
<customtag name="FILE" type="file" />
<customtag name="FOLDER" type="text" />
<customtag name="SIZE" type="number" />
<customtag name="EXTENSION" type="text" />
</index>
Note on the network share:
- The network share must be visible from the Process server.
- The user who runs Process must have read rights on the network share.
Source : https://wiki.myvdoc.net/xwiki/bin/view/Dev+Floor/FileIndexExtension