Upgrading External Data Feeder for NFO
You upgrade a single instance of External Data Feeder for NFO by installing the latest version over your existing installation. During the upgrade the installer package preserves all External Data Feeder for NFO configurations, except configuration files changed manually. These files, if changed, are backed up into conf-backup.<date>.tar.gz file (<date> is archive date), and should be restored manually, if necessary.
The following is a list of some configuration files.
File | Purpose |
$updater_home/conf/updater.properties | NetFlow Intergrator URI and other parameters |
$updater_home/conf/.updater_keystore | Default self-signed certificate for X509 authentication |
$updater_home/conf/.updater_truststore | Default self-signed NFO tomcat certificate |
$updater_home/java/jre/jre/lib/security/cacerts | Trusted certificates imported into Java Runtime cacerts keystore |
After upgrade, validate default configuration and restore from the backup if it is required. If you didn’t modify these files, ignore the caution.
When upgrading External Data Feeder for NFO on RHEL 7, the messages like these might be displayed:
Cleaning up / removing...2:nfi-updater-2.4.0.3.34-linux warning: file /opt/nfi-updater/lib/wasync-1.4.0.jar: remove failed: No such file or directorywarning: file /opt/nfi-updater/lib/netty-3.9.2.Final.jar: remove failed: No such file or directorywarning: file /opt/nfi-updater/lib/async-http-client-1.8.11.jar: remove failed: No such file or directory
This is a normal situation and these messages should be ignored.
