This article outlines the procedure to upgrade Cloudpaging Server and the pre-requisite components installed to the latest supported versions.
The upgrade process may require downtime resulting in service disruption. A backup of all systems should be taken prior to making any changes.
With the release of 9.6.0 Server, Java version has changed to 11 and Tomcat has changed to 9. You must have upgraded your server to 9.6.0 prior to upgrading to 9.7.0.
Review the Cloudpaging release article and release notes in Latest Releases
Schedule a maintenance window according to Upgrading Cloudpaging Server
Raise a ticket with AppsAnywhere Support
Requesting the installation files
Check if a new license is required
Provide the maintenance window so AppsAnywhere Support can be available
In line with the Support Workflow, AppsAnywhere Support needs to be aware of any change to the infrastructure. Otherwise, the support agreement may be invalidated.
Place the installation files on the desktop of each Cloudpaging Server and extract the zip file
Ensure a snapshot has been taken of all the servers that are being upgraded
Ensure there is a backup of the Cloudpaging database (StreamDB)
Perform functionality tests.
Login to AppsAnywhere
Launch more than one Cloudpaging application (E.g. Audacity)
Check the Cloudpaging Player log file shows a successful connection to each online Paging server (search for "Connection Test for Remote Source")
Login to the Cloudpaging Server admin portal and confirm that all online services are running showing a green tick
Connect to the first server group (1 x Admin/License server and 1 x Paging server).
Stop the Cloudpaging Server Service via services.msc on server group 1.
Perform functionality tests (step 5) against server group 2 via load balancer
Check your current version of Cloudpaging Server in Add or Remove programs
Run the relevant database migration scripts from within latest Cloudpaging Server zip file downloaded from step 1. cloudpaging-server\<version>\Server-Windows\Database\upgrades using SQL Server Management Studio with the dbjbuser account. A successful run will show that at least one row was affected.
- If upgrading from 9.4.621 to 9.5.1, you will need to run the web_9.4_to_9.5.sql.
- If upgrading from 9.2.1, you will need to run the web_9.2_to_9.3.sql script, web_9.3_to_9.4.sql then web_9.4_to_9.5.sql.
If there were any errors, please take a screenshot and contact AppsAnywhere support and attach the error to the ticket.
11. Open ''Add or Remove Programs'' and uninstall the Java (AdoptOpenJDK JRE with Hotspot / Eclipse) component.
12. Uninstall Apache Tomcat 8.5 Tomcat8 (remove only). When uninstalling Apache Tomcat 8.5, a prompt will ask if all files should be removed from the Tomcat directory, click Yes.
13. Run Application Jukebox Server.exe from the extracted cloudpaging-server\<version>\server-windows folder and click Yes to start the upgrade.
Do not install Microsoft SQL Server 2016 Express RTM if prompted to do so
14. Click Yes to install AdoptOpenJDK
15. Click Yes to install Apache Tomcat
16. Click Next
17. Click Upgrade
18. Click Finish
19. Once the upgrade is complete, launch the Cloudpaging Server shortcut on the desktop to verify in the footer of the login page of the Cloudpaging Server Admin Portal, Enterprise Edition matches the version installed and Database Version is on the same build.
20. Login to the Cloudpaging Server admin portal and confirm that all services are running, showing a green tick. Since you're unable to login to the admin portal on the paging server, refresh services window and restart the Cloudpaging server service.
21. Stop the Cloudpaging Server Service via services.msc on server group 2.
22. Perform functionality tests (step 5) against server group 1 via the load balanced DNS.
23. Complete the upgrade steps 11-20 on server group 2.
24. Stop the Cloudpaging Server Service via services.msc on server group 1.
25. Perform functionality tests (step 5) against server group 2 via the load balanced DNS.
26. If you do not have any more servers to upgrade, go to step 31.
27. If applicable, stop the Cloudpaging Server Service via services.msc on all remaining servers.
28. Complete the upgrade steps 11-20 on all remaining servers.
29. Stop the Cloudpaging Server Service via services.msc on server groups 1 and 2.
30. Perform functionality tests (step 5) against all remaining servers via the load balanced DNS.
31. Start the Cloudpaging Server Service via services.msc on all server groups.
32. Perform functionality tests (step 5) via the load balanced DNS.
Providing the functionality tests are successful, the upgrade of Cloudpaging Server is complete!