Cloudpaging Server upgrade procedure

Overview

This article outlines the procedure to upgrade Cloudpaging Server and the pre-requisite components installed to the latest supported versions.

See Upgrading Cloudpaging Server and the Cloudpaging Server Guide for information. 

Prerequisites

1. Review all related documentation (Upgrading Cloudpaging Server and the Cloudpaging Server Admin Guide)

2. Review the Cloudpaging release article and release notes in Latest Releases

3. Schedule a maintenance window according to Upgrading Cloudpaging Server

4. Raise a ticket with AppsAnywhere Support

   1. Requesting the installation files

   2. Check if a new license is required

   3. Provide the maintenance window so AppsAnywhere Support can be available

Upgrade Procedure

1. Place the installation files on the desktop of each Cloudpaging Server and extract the zip file

2. Backup folder C:\Program Files (x86)\Numecent\Application Jukebox Server\core\webapps\jukeboxserver

3. Ensure there is a backup of the Cloudpaging database (StreamDB)

4. Perform functionality tests.

   1. Login to AppsAnywhere

   2. Launch more than one Cloudpaging application (E.g. Audacity)

   3. Check the Cloudpaging Player log file shows a successful connection to each online Paging server (search for "Connection Test for Remote Source")

      

5. Login to the Cloudpaging Server admin portal and confirm that all online services are running showing a green tick.

   

6. Connect to the server group 1 (1 x Admin/License server and 1 x Paging server).

7. Stop the Cloudpaging Server Service via services.msc on server group 1.

   

8. Perform functionality tests against server group 2 via load balancer

9. Check the current version of Cloudpaging Server in Add or Remove programs

   

10. Run the relevant database migration scripts from the latest Cloudpaging Server zip file downloaded. The scripts are saved in cloudpaging-server\<version>\Server-Windows\Database\upgrades and should be run against the StreamDB database using the dbjbuser SQL login.
    A successful run will show that at least one row was affected e.g.:

    • If upgrading from 9.4.621 to 9.5.1, run the web_9.4_to_9.5.sql.

    • If upgrading from 9.2.1, 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.

11. Open ''Add or Remove Programs'' and uninstall the old Java (AdoptOpenJDK JRE with Hotspot / Eclipse) component.

    

12. Uninstall the old Apache Tomcat version. When uninstalling Apache Tomcat 8.5, a prompt will ask if all files should be removed from the Tomcat directory, click Yes.

    

13. If upgrading from Cloudpaging <=9.7 to >=9.8, delete the Cloudpaging server.xml file, otherwise proceed to step 14

    1. Delete C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xml on each server in group 1

14. Run Application Jukebox Server.exe from the extracted cloudpaging-server\<version>\server-windows folder and click Yes to start the upgrade.

11. Click Yes to install AdoptOpenJDK

    

12. Click Yes to install Apache Tomcat

    

13. Click Next

    

14. Click Upgrade

    

15. Click Finish

    

16. 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.

    

17. Login to the Cloudpaging Server admin portal and confirm that all services are running, showing a green tick.

    

18. If upgrading from Cloudpaging <=9.7 to >=9.8, edit the Cloudpaging server.xml file, otherwise proceed to step 26

    1. Open C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xmland update the certificate attribute on one server in group 1.

    2. Edit the keystoreFile="C:\Program Files (x86)\Numecent\Application Jukebox Server\secured.keystore attribute replacing the secured.keystore filename with the Cloudpaging certificate filename e.g. cloudpaging.pfx.

    3. Immediately after that entry add the password attribute with the correct password e.g. keystorePass="ThePassword" keystoreType="PKCS12".

    4. The server.xml file, should have the following entries for the declared connectors:

       CODE

       <Connector connectionTimeout="20000" maxParameterCount="1000" keystoreFile="C:\Program Files (x86)\Numecent\Application Jukebox Server\cloudpaging.pfx" keystorePass="ThePassword" keystoreType="PKCS12" minSpareThreads="25" URIEncoding="UTF-8" port="443" SSLEnabled="true" scheme="https" secure="true" sslProtocol="TLS"/>

       CODE

       <Connector connectionTimeout="20000" maxParameterCount="1000" disableUploadTimeout="true" enableLookups="false" minSpareThreads="25" URIEncoding="UTF-8" port="80" />

19. Save the server.xml file.

20. Restart the Cloudpaging service on the server from step 18.

21. Ensure the certificate is applied and the Cloudpaging service health check returns a success response on the server from step 18.

22. Copy C:\Program Files (x86)\Numecent\Application Jukebox Server\core\conf\server.xml to the other Cloudpaging servers.

23. Restart the Cloudpaging service on each of the other Cloudpaging servers.

24. Ensure the certificate is applied to each Cloudpaging Admin server via https://<server_dns>/jukeboxserver.

25. Use the health check to confirm that a success response is returned from each server.

26. Stop the Cloudpaging Server Service via services.msc on server group 2.

27. Perform functionality tests against server group 1 via the load balanced DNS.

28. Complete the upgrade steps on server group 2.

29. Stop the Cloudpaging Server Service via services.msc on server group 1.

30. Perform functionality tests against server group 2 via the load balanced DNS.

31. Start the Cloudpaging Server Service via services.msc on all server group 1.

32. Complete the upgrade steps on all remaining server groups.

33. Apply any new Cloudpaging Server license keys that have been provided e.g. when upgrading to 9.5 or above from an older version

34. Perform functionality tests against all remaining server groups via the load balanced DNS.

35. Start the Cloudpaging Server Service via services.msc on all server groups.

36. Perform functionality tests via the load balanced DNS.