Manage an update of Genius Server?

This point also very well described in our product documentation.

Video #

Step-by-Step Video – This video is currently only available in German.

Requirements #

• running MyMFP or GeniusMFP installation on windows server, for linux installations please contact support@geniusbytes.com for additional info
• access to Genius Bytes software downloads e.g. Genius Server

Objective #

• update your MyMFP / GeniusMFP installation from any version to the latest version

Solution #

• Perform the Update following the step by step guide

Example #

1. Schedule a timeframe and inform the customer that the service will not be available in the timeframe.The update task to migrate the underlying datbase may take a lot of time depending on several factors, such as: cdds versions between old and new version, size of the database, performance of sql server. It may even be necessary to run the update overnight.
2. To update from versions pre 2.27.4, perform the update to 2.27.4 first, then perform update to 3.x. The guide will describe the update to 3.x
3. Download latest genius-server-3.xx.xx-update-win64.exe, e.g. genius-server-3.22.0-update-win64.exe
4. Create database backup and virtual machines backups
5. Stop all cluster nodes (if you are in a single node installation, stop the genius server service)
6. Close configuration tools of the current user and all other users logged in on the vm (e.g. by forcing a logout of other users).
7. Run genius-server-3.22.0-update-win64.exe as administrator on the first node in the cluster.
   in case of a MSSQL database connected by using the integratedSecurity option (e.g. if a domain user is used for accessing the db), start the update tool as this user.
   If you are not sure if the integratedSecurity option is used, check it in the configuration tool of the old installation (database URL).
8. Wait until the installer is finished. After a short while the update tool will open.
9. Click start migration
   
10. Wait until the tool has finished the database migration. As mentioned before this step will take some time. Do not close the configuration tool, even if you think it might not be working anymore.
11. Wait until the tool has finished the remaining update steps (update of the application files)
12. Wait until the tool will confirm the successful update with a “UPDATE SUCCESSFUL” text in the update tool.
13. For some version jumps an additional question will be displayed “Reset ETL?”. Please confirm the reset.
14. Close the update tool.
15. Start the configuration tool of the new version. A list of values will be displayed where we decided to change default values. You can use the new default values by clicking on the default button next to the setting. If you do not want to change the settings, press save and continue.
16. The name of the service might have changed from My CDDS Server to Genius Server. It is possible that you have to configure the service user again. If the Genius Server was always started with “local system” no change is required.
17. If required reconfigure the keyStore and trustStore in the new certificate section of the configuration tool.
18. Reset the logging configuration to the new default by deleting: /conf/cdds/log4j2.xml
19. JVM memory: In larger enterprise environments, Genius Server might require higher a larger memory pool. Check if the JVM has enough memory by:
    open the genius-cdds-service.exe in /bin. In the java tab increase „Initial memory pool” and „Maximum memory pool“ (default 2048MB for each). Do not change „Thread stack size“ (512).
20. Start the Genius Server server
21. Wait for at least a minute and check if you can login on the Genius Server /conf website. Perform a login and check for changed settings highlighted. The new default value can set by clicking the restore icon next to the setting. Save the changes. Changes in /conf do not require a service restart as they are stored in the database and are set for all servers in the cluster.
22. Check if you can login on the Genius Server admin website. (this indicates a successful update and running server).
23. If the update was successful, repeat the procedure for the other nodes in the cluster.

Should the update fail, save the /logs folder for later analysis. Send it to support@geniusbytes.com and roll back to your backups created earlier.