-
Notifications
You must be signed in to change notification settings - Fork 9
PercussionCM1Upgrade
- Must be on the latest 5.3 patch, Version 5315_2020527. Downloadable here
- Java 1.8 must be installed in order to run the installation JAR files. Amazon Corretto JRE 1.8 downloadable here
- Download the perc-distribution-tree.jar and delivery-tier-distribution.jar from the Releases page
- Shut down all Percussion services. There will be a Production DTS, an optional Staging DTS, and a CM1 service that need to be shut down.
- Verify that there are no Java processes running:
-
Windows: Check Task manager for any Java processes and click End Task
-
Linux: Run
pgrep javaorps aux | grep javaand kill the services if they are running from the Percussion folder
- Open the command line or terminal. On windows, make sure to run this as Administrator.
- Verify that your system java version is Java 1.8. To do this, run
java -version. If it is not version 1.8, you can download the Amazon Corretto distribution of JRE 1.8 here. Note: Make sure to complete this step before moving forward or the build will fail. - Navigate using
cdto the folder where you downloaded the perc-distribution-tree.jar and delivery-tier-distribution.jar files
To upgrade the CMS, run:
-
Windows:
java -jar perc-distribution-tree.jar C:\Path\To\CM1InstallationFolder -
Linux:
java -jar perc-distribution-tree.jar /path/to/CM1InstallationFolder
Once that completes, to upgrade the DTS, run:
-
Windows:
java -jar delivery-tier-distribution.jar C:\Path\To\DTSInstallationFolder -
Linux:
java -jar delivery-tier-distribution.jar /path/to/CM1InstallationFolder
-
Make sure the Percussion/JRE/ folder contains an installation of JRE 1.8. If not, you can either sym-link this path to your system JRE folder, or copy in a full JRE 1.8 installation into the Percussion folder, then rename it to "JRE". If the directory structure is correct, you should have the java executable under Percussion/JRE/bin/java.
-
Install the Percussion CMS service and PercussionProductionDTS service so these can run in the background.
-
Windows:
- Navigate to the Percussion\jetty\service folder in the command line
- Run
install-jetty-service.bat installto install the CMS service - Hit enter if any prompts come up to choose the default options
- Navigate to the Percussion\Deployment\Server folder
- Run
DTSProductionService.bat installto install the DTS service - OPTIONAL: If you are using the Staging DTS, install the Staging service by navigating to the Percussion\Staging\Deployment\Server folder and running
DTSStagingService.bat install
-
Linux:
- Navigate to the Percussion/jetty/service folder in the terminal
- Run
install-jetty-service.sh install - Hit enter if any prompts come up to choose the default options
- Navigate to the Percussion/Deployment/Server folder
- Run
DTSProductionService.sh installto install the DTS service - OPTIONAL: If you are using the Staging DTS, install the Staging service by navigating to the Percussion/Staging/Deployment/Server folder and running
DTSStagingService.sh install
On Windows, there should be a PercussionProductionDTS and a PercussionCMS windows service. You can start and stop the CMS using these services now.
On Linux, there will be a PercussionCMS and PercussionProductionDTS service under /etc/init.d that should have been created by the shell scripts on step 6 of the installation. You can start them with systemctl start PercussionCMS / systemctl start PercussionProductionDTS and stop them with systemctl stop PercussionCMS / systemctl stop PercussionProductionDTS
See Enabling HTTPS in PercussionCMS 8.x
Your settings should have stayed the same for the LDAP configuration, but if LDAP users are not able to log in after the upgrade, you can try importing the server certificate from the LDAP server to the CMS. You can add the certificate to the Percussion/rxconfig/trusted_certificates folder in both Windows and Linux. Then, simply restart the PercussionCMS service.