Upgrading or Removing EDFN
This guide provides instructions for maintaining your standalone External Data Feeder for NFO (EDFN) instances, including upgrading to the latest version and complete removal from your system.
If you are using NFO version 2.7 or higher, EDFN is already bundled with the main NFO installation. You only need to follow these steps if you are running a standalone EDFN instance on a separate server.
Upgrading EDFN
You upgrade a standalone instance by installing the latest version over your existing installation. The installer preserves most configurations, but manually changed files are backed up into a conf-backup.<date>.tar.gz archive.
Key Configuration Files
If you have modified these files, you should manually verify and restore settings from the backup after the upgrade:
| File | Purpose |
|---|---|
$EDFN_HOME/conf/updater.properties | NFO URI and core parameters |
$EDFN_HOME/conf/.updater_keystore | Default self-signed certificate for X509 authentication |
$EDFN_HOME/conf/.updater_truststore | Default self-signed NFO tomcat certificate |
On RHEL 7, you may see "remove failed" warnings for specific .jar files during the cleanup phase. This is normal and these messages should be ignored.