Technical notes for NER enabled on-premise collectors
This article provides an overview of the key features and considerations related to on-premise collectors with NER (Named Entity Recognition) functionality enabled.
Installation
During installation of the collector, a small Java service is installed to run NER tasks. This service listens to a port determined by the type of collector.
| Collector Type | Port |
| Windows File Share | 50052 |
| iManage Work | 50053 |
Requests to these ports are designed exclusively for communication from the Collector, meaning they will only accept requests originating from the same machine on which the Collector is installed, and not from any external sources.
Temporary File Processing
When processing objects for NER extraction, temporary files are created in this default location- %PROGRAMDATA%\ActiveNav\Collector\FeatureExtraction.
This location can be changed by modifying the ConvertedTextTempDirectory entry in %PROGRAMFILES%\ActiveNav\Collector\appsettings.json.
Note - If the default temp directory is changed, the ActiveNav Cloud Collector service will need to be given read/write/delete access to the new location.
After changes to the default settings, the service should be restarted for the update to be applied.