FileConnect Enterprise v3 (FCEv3) Setup Guide

This guide explains how to install, configure, and activate FileConnect Enterprise v3 (FCEv3) in a production environment. It covers prerequisites, virtual machine setup, connector configuration, licensing, verification, and optional enhancements.  

1. User Accounts

Default accounts referenced during setup:

Retrieve the elastic password from appsettings:

bash /opt/recordpoint-connector-IndexBuilder/Deployment/get-appsettings-elastic-pass.sh

Reference: user account table and retrieval script.  

2. Prerequisites and Preparation

Install a supported hypervisor (VMware or VirtualBox) on the host system before proceeding. Ensure your environment meets the documented host requirements. 

3. Azure Application Registration

1. Sign in to the Azure Portal with an Admin account.
2. Open Azure Entra ID → App registrations → New registration.
3. Set Name to FileConnect Enterprise and Supported account types to “Accounts in this organizational directory only”.

4. 

5. Click Register and record the Application (client) ID.

1. Go to Certificates & secrets → New client secret. Describe it (e.g., “fce secret”) and choose a 12–24 month expiry.
2. Copy the Value of the secret and store it securely (not the Secret ID).

4. Configure the RecordPoint Connector

1. Sign in to your RecordPoint region (e.g., https://usw.records365.com).
2. Open the gear icon → Connectors → + Add Connector → FileConnect Enterprise (v3).

1. Enter the Azure Application (client) ID.
2. Set Aggregation Level to Lowest Level Folder.
3. Optionally rename, then Save and Enable the connector.

Reference: connector creation and aggregation level.  

5. Download Configuration Files

Reference: download list and purpose. 

6. Create the Virtual Machine

1. Import the OVA into VMware or VirtualBox and name the VM.
2. Recommended resources: Disk ≥256 GB, CPU: 4 cores, Memory: 32 GB (≤50% of host), Networking: NAT for initial startup.
3. Start the VM and allow one-time setup to complete before making changes.

Reference: VM creation guidance and resource recommendations.  

7. License Diskover

1. Log into the VM as diskover.
2. Generate hardware ID:

sudo -i
cd /opt/diskover
python3 -m pip install -r requirements.txt
python3 diskover_lic.py -g
exit

3. Share the ID with RecordPoint to receive diskover.lic and diskover-web.lic.
4. Install licenses and restart Diskover:

sudo mv ./diskover.lic /opt/diskover/
sudo mv ./diskover-web.lic /var/www/diskover-web/src/diskover/
sudo systemctl restart diskoverd

Reference: Diskover licensing steps and paths.  

8. Install FCEv3

1. Copy the RPM ZIP to the VM and install:

unzip -o rpm-packages-*.zip &&
sudo dnf install ./recordpoint-connector-*.rpm &&
rm ./recordpoint-connector-*.rpm

2. Retrieve and store the Elasticsearch password (bootstrap file):

sudo awk 'END {print $NF}' /root/elastic_user

3. (Alternative after OVA configuration) retrieve from appsettings:

bash /opt/recordpoint-connector-IndexBuilder/Deployment/get-appsettings-elastic-pass.sh

4. Run the OVA configuration script:

cd /opt/recordpoint-connector-IndexBuilder/Deployment
sudo chmod a+x ./configure-ova-rpms.sh
sudo ./configure-ova-rpms.sh

Verify services are running:

./fcectl.sh --status

Reference: installation commands and service verification.  

9. Configure FCEv3 Connector (in UI)

1. Open http://localhost:8080/#/setting.
2. Enable as needed:
   • Azure Logging → Enable Azure Monitor
   • Document Cracking → Extract and Store File Content or Extract Content Metadata Only (Author)
   • Crack Image Types and Enable OCR (if required)
3. Import the Connector Configuration JSON downloaded earlier.
4. Paste the Azure App Registration Client Secret, optionally Test Settings, then Save.

Reference: UI settings and JSON import. 

10. Validate Diskover Access

1. Open http://localhost:8000 and log in as admin.
2. “No completed indices found” is expected until tasks are created and run.

Reference: Diskover login and first-time state. 

11. Updating an Existing FCEv3 Installation

1. Download the latest RPM ZIP from the connector configuration page.
2. Install as in Step 8, then re-run the configuration script:

sudo bash /opt/recordpoint-connector-IndexBuilder/Deployment/configure-ova-rpms.sh

Consider reviewing Elasticsearch memory guidance in the FAQ.