This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- Code Insight
- :
- Code Insight Knowledge Base
- :
- FNCI 6.x - Processing Electronic Updates through a different SFTP server (changing the default)
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
FNCI 6.x - Processing Electronic Updates through a different SFTP server (changing the default)
FNCI 6.x - Processing Electronic Updates through a different SFTP server (changing the default)
Summary
There may be a need to change the SFTP server connection details from the default (updates3.palamida.com) to a new location. This article shows the configuration file and properties that can be changed to achieve that.Synopsis
To specify a different SFTP location where the electronic updates file are copied and would like to use this new server for all future electronic update connections, you can configure this file in the application and restart the server to take effect:Configuration file location:
$FNCI_installation\tomcat\webapps\palamida\WEB-INF\classes
File to modify:
core.common.properties
Property configuration:
# Electronic Updates Settings
palamida.ftp.server.url = updates3.palamida.com
palamida.ftp.server.port = 22
palamida.ftp.server.username = updates-user
palamida.ftp.server.password= <password>
manifest.file.name = /updates/3.1/update_manifest.txt
update.file.name = /updates/3.1/update.zip
# Use Cron frequency syntax (default is every Sunday at noon)
# http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger
auto.update.enabled = true
auto.update.jobFrequency = 0 0 12 ? * SUN
No ratings