File system (filecopy) data sources
|This feature is not available in the Squiz DXP.|
A file system (filecopy) data source is used for indexing documents from a file system. The file system can be accessed locally or remotely.
File system data sources are created by following the data source creation steps and selecting filecopy from the list of data source types.
A file system data source is defined by the following properties:
Funnelback supports the indexing of various different types of directory. These include:
These are file shares that are served using the SMB or CIFS protocols, as is standard in most Windows environments. They can be addressed as UNC paths. How the data source is specified will depend on where the data is located. For example, a file system data source might have:
For a local disk:
For a Windows file share:
Note that on Linux operating systems, the default firewall rules may need to be altered to allow for SMB / CIFS name resolution.
RedHat Linux provides instructions for mounting NFS file shares and also comes with SMB/CIFS support
File shares mounted on a Windows machine can be indexed in a similar way, and will provide SMB/CIFS support. Please note that drive letter mappings are done or a per-user basis, so paths must be specified as UNC paths (e.g.
\\fileserver\directory) for remote file shares.
File system results are served by the user interface layer. It will contact the file system to retrieve the requested file and download it to the search user browser.
Apache Tika is used to convert binary document formats to text. Additional filtering can be applied using Funnelback plugins.
|If you’ve updated the filter chain or how a filter works, you may need to disable the filecopy.cache to ensure the changes are applied to any previously processed documents.|
|This functionality is only available to Funnelback system administrators.|
The steps below set the log level for a filecopy data source.
Edit the file and update the line below to the desired level.
<Logger name="com.funnelback" level="info"/> <!-- eg. increase to debug level: --> <Logger name="com.funnelback" level="debug"/>
Save the file and start and update observing debug messages now appear in the