Having a backup file is one of the most important steps. It is a good idea to have a working backup in case something goes wrong. Therefore, database and Frontline Home back-ups are required before the update.
To have a backup for Frontline Home Directory, make a copy of the directory or put the directory in an archive to use less space.
Updates consist of replacing the frontline.jar file and checking if the application starts normally again.
It is recommended to always have a backup before making changes within the application.
To download the latest stable frontline.jar, refer to downloads.
Stop the service using Windows Service View and select Stop on Frontline Command Center Service.
Alternatively, the service can be stopped by using the following command:
net stop frontline
Cleaning up the Frontline Home directory will prevent unexpected behavior due to old files which will not be overwritten:
Administrators should delete the following directories in FRONTLINE_HOME/config
:
In the configuration directory, the following items should be deleted:
If the logging configuration for the installation has been modified, then logging.xml
and logging_service.xml
files should not be deleted.
Navigate to the old frontline.jar file and replace it with the one that has been just downloaded.
Restart the service using the GUI or the command:
net start frontline
To see if the update was successful, check the logs
file for the availability of the server by using a browser.
Clearing the browser cache after some time helps preventing login and certificate issues after the update.
For users using a custom-developed Frontline Connector (e.g. with a Database) these steps can be different.
To update the standard Frontline Connector:
net stop frontlineconnector
xservice.jar
file to something like xservice-old.jar
xservice.jarnet start frontlineconnector