Upgrade Recommendations
This section summarizes SDL recommendations for customers upgrading to Contenta Web 5.0 who have made customizations to Contenta Web.
- Tomcat and Java – SDL recommends always moving to the latest supported versions of Tomcat and Java when upgrading Contenta Web. The latest versions have the latest security patches and enhancements.
- The notes below summarize how to approach upgrades when the specified types of customization are in place:
- Custom css
- As with previous versions of Contenta Web, custom css files need to be merged.
- In addition, there are new css files that may also require customization to complete the look and feel. See the list of new files later in this document and the CSS info in Section 5 of this document for more information.
- Custom images
- As with previous versions of Contenta Web, create/update images as necessary to modify the look and feel.
- Review the new and obsolete file list later in this document for images to see how it impacts custom images that are being used.
- Custom jsp/xsl
- As with previous versions of Contenta Web, custom jsp/xsl files need to be merged.
- In addition, review new and obsolete file list and plan how to move customizations forward - i.e. Is the customization still needed? Can it be done a different way that takes advantage of improvements in out-of-the-box Contenta Web and minimize future upgrade impact?
- Custom web tools
- Custom web tools will work without modification as the underlying Contenta Web and Contenta API have not changed.
- The Look and Feel of the custom web tool may need to be tweaked (because of new and updated css and images files).
- In addition, when multiple objects are selected in the list view in Contenta Web, additional idpaths are being sent to the tool. This may allow for enhancing custom web tools or creating new ones that can work on multiple objects.
- Custom css