Prior to running the framework upgrade tool you must close all opened files in the DualShield installation folder. If you are using remote desktop to access the DualShield machine, make sure there is no other people (session) connected to the same server. If possible, backup up the system before upgrading. For instance, take a snapshot if the machine is a VM.
The upgrade tool actually does the following things
Check if it needs to upgrade;
Stop DualShield service;
Backup the existing tomcat folder to tomcat6_$day_of_upgrade;
Copy server.xml and context.xml (under tomcat/conf) to new folder “critical”;
Copy the new tomcat (version 8.0.24) to tomcat folder (overwrite the existing files);
Copy lib\security\cacerts to critical folder;
Rename the jre folder to jre_$day_of_upgrade;
Copy new JRE 7 to jre folder;
Copy the unlimited JCE Policy files;
Copy back the server.xml and context.xml, then modify them accordingly.
Modify cacerts in new JRE 7;
Modify DualShield service in Registry;
Restart DualShield service.
If you don’t see any RED message before “Upgrade Finished. Please check Performance in the started Task Manager and wait the service fully started, then check if everything is OK.”, then upgrade itself should be successful. If you can’t access the upgraded DualShield service, check the tomcat logs for details.
If you do see some RED message during the upgrade, it may indicate the upgrade somehow failed. Please take a picture of upgrade window, then send it to our support email account for help.
The solution to the upgrade failure varies, it depends on which stage it failed at. For instance, if you see the upgrade failed at renaming jre folder (it may be caused by a opened Windows Prompt while the current folder is jre something), then the rollback procedure is simple, just remove the tomcat folder and rename tomcat6_$day_of_upgrade back to tomcat.
Appendix: the powershell script for upgrade