Platform Deployment Guide › Binary Text Extractor › BTE Requirements on FSA Servers

BTE Requirements on FSA Servers

You may need to install the BinaryTextorConfig.xml configuration file manually on a File Scanning Agent (FSA) server.

The BTE is installed automatically on servers hosting the FSA. This enables you to apply CA DataMinder policy to scanned files that have non-standard formats.

When the FSA scans a file, it extracts the text content and passes the content to a remote policy engine for analysis. Consequently, the FSA requires a local copy of the BinaryTextorConfig.xml configuration file in order to scan and extract text from files with non-standard formats. .

Normally, CA DataMinder replicates this configuration file automatically to CA DataMinder policy engines and endpoint computers after you install the file on the CMS. However, CA DataMinder can only replicate BinaryTextorConfig.xml to an FSA host server if the CA DataMinder infrastructure is installed on the server. If the CA DataMinder infrastructure is not installed, you must manually copy BinaryTextorConfig.xml to the FSA server and edit the registry to specify the location of this file.

Do I need to install the BTE configuration file on an FSA server?

You must install BinaryTextorConfig.xml manually if the FSA uses the Remote Policy Engine Connector. (The Connector is a special policy engine hub that an FSA can use to distribute scanned items to remote policy engines for processing. The Connector does not use the CA DataMinder infrastructure.)

You do not need to install BinaryTextorConfig.xml manually if the FSA passes scanned items directly to a local CA DataMinder policy engine. (A CA DataMinder infrastructure is installed on these FSA servers when you install the policy engine.)

Full details about the FSA are in the Stored Data Integration Guide.

To manually install the BTE configuration file on an FSA host server

Repeat the following instructions on each FSA server where the FSA needs the BTE to extract text content from files.

1. Export your customized BinaryTextorConfig.xml from the CMS.

   The procedure is the same as exporting the default configuration file.

2. Copy BinaryTextorConfig.xml to the FSA host server.

   You can choose any target folder.

3. Create the following registry key on the FSA host server:

   On 32-bit servers:

   HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA DataMinder
     \CurrentVersion\UserProcess\BinaryTextExtractor
   

   On 64-bit servers:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA DataMinder
     \CurrentVersion\UserProcess\BinaryTextExtractor
   

4. Within this registry key, add the following registry value:

   ConfigFile

   Type: REG_SZ

   Data: Specify the full path to BinaryTextorConfig.xml on the local FSA server. For example:

   C:\BTE\BinaryTextorConfig.xml
   

Important! If you update BinaryTextorConfig.xml in the future, repeat the above instructions on each affected FSA server.

More information:

Export the Default Configuration File