cm1-53-sr-20191105-patch

cm1-53-sr1-20200310-patch

Patch ID - 5315_20200310

This is a cumulative/rollup patch for CM1 5.3 SR1.  This patch contains security updates and defect corrections.

An updated list of Known Issues can be found at the bottom of this page. 

For details on bug fixes and improvements in previous patch updates, please see the release notes for prior patches. Links to prior patch release notes are provided below:

ISSUES ADDRESSED IN THIS PATCH:


[CMS-6566] - Security: DTS ROOT/WEB-INF/web.xml does not define an error page

A security issue was corrected where the default Tomcat ROOT web application did not specify an error page by default.  This has been corrected in this patch. 

[CMS-6503] - Security: AJP / "GhostCat"  - Update Tomcat to version 7.0.100

The DTS Tomcat has been updated to Tomcat 7.0.10 and the patch has been updated to remove AJP connectors.  System configuration may have been customized prior to patching so we do recommend that customers review the following files after patching to confirm that any <Connector protocol="AJP/1.3" ... /> elements are removed from the configuration. 

  • <InstallDir>/Deployment/Server/conf/server.xml
  • <InstallDir>/Staging/Deployment/Server/conf/server.xml
  • <InstallDir>/AppServer/server/rx/deploy/jboss-web.deployer/server.xml

More information can be found on this community post.

[CMS-6145] - 5.3 Patch seems to overwrite the Default Workflow and drop and recreate the Adhoc Type breaking workflows

A long time issue was resolved where applying the latest patch could overwrite the Default Workflow, removing any custom steps that may have been added to the Default Workflow.  This issue is resolved in this patch. 

[CMS-6529] - Uninstalling the patch is not restoring the DTS server.xml file

An issue was corrected where uninstalling the patch did not correctly restore the DTS server.xml file. Uninstalling the patch will now restore the server.xml to the state it was in prior to patching.

[CMS-6560] - Patch install fails when updating the database with MySQL 5.7 backend

An issue was corrected where the Patch would fail to install when upgrading a MySQL schema that had been upgraded to MySQL 5.7.  NOTE: we recommend updating the MySQL Connector when updating MySQL versions.  The current version of MySQL Connector is Connector/J 5.1.48

[CMS-6554] - Add support for full text indexing of Page and Asset content (in addition to metadata) when publishing to Apache SOLR

An improvement was made to the SOLR integration to add support for the full text indexing of Page and Asset content in addition to page metadata.  the SOLR configuration page has been updated to include the steps need to enable SOLR indexing of assets. 


INSTALLATION NOTES & COMMON ISSUES

MEMORY REQUIREMENTS

Patch updates include additional caches that can increase the minimum memory requirements from 2GB to 4GB.  Verify that the memory setting in PercussionServer.lax file is set to at least a value of -xmX 4096m when patching to avoid unexpected outages due to out of memory errors.

DATABASE UPDATES

Beginning with Patch 5315_20181221 the update engine now supports database schema updates as part of the update process. As a result the patch relies on the installer database configuration file to successfully run. In environments where the database setup has changed, or a server / RDBMS migration has occurred, it is possible that the installation database configuration file may be out of date which would cause the patch to fail. To avoid this problem, prior to installing the Patch verify that the contents of the <InstallDir>/rxconfig/Installer/rxrepository.properties file are correct. Updating this file is covered in the Appendix A section of the Migrating Percussion Environments help page.

COMMON ISSUES / WORKAROUNDS

Updates can occasionally fail to apply for a variety of reasons. To help streamline troubleshooting, we have created a new Common Issues / Workarounds page to collect the steps to correct these issues if you run into them when patching. As always if you run into a problem applying a patch, please contact the Technical Support team at support@percussion.com, and they will be happy to assist.

Known Issue List

  • CMS-5294 - The Ignore Unmodified Assets publishing feature does not work correctly on systems with 2000 or more Assets. We recommend that this option be unchecked in your publishing configuration to avoid publishing failures.

  • CMS-3614 - After applying the patch end users may need to clear their browser cache in the CM1 user interface in order to see the new changes to the Rich text Editor and plugins.
  • CMS-3257 - Customers using the MySQL database server as the backing database for the DTS, will lose the MySQL Connector jar if it was previously placed into the <InstallDir>/Deployment/Server/perc-lib directory. To correct this problem the MySQL Connector for Java may be installed or symlinked into the <InstallDir>/Deployment/Server/lib directory. Percussion does not include this connector as part of our installation due to license incompatibility issues.
  • CMS-3490 - Customers patching the DTS on Windows Servers will need to reinstall the DTS Windows service by using the "<InstallDir>\Deployment\Server\bin\service.bat remove" and "<InstallDir>\Deployment\Server\bin\service.bat install" commands. Once the service has been successfully re-installed, the Percussion DTS Windows Service will start 

Uninstalling the Patch

This patch includes an uninstall option to support rollback in the event the patch introduces a problem or issue. The patch can be downloaded from the Support portal. For instructions on installing or uninstalling the patch, please review the Readme file provided in the patch folder. Note: To install a patch after uninstalling an existing patch, uninstall the existing patch, start the service back up normal, shut the service down and then install a patch.