CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of ContentsThis guide is intended to assist you during your upgrade. Familiarize yourself with the changes and actual tasks when upgrading from CoreMedia Content Cloud v10 to v11. Use this introduction to learn about the major enhancements and to understand the big picture.
Use the following chapters to review all the information about the changes that concern you – your individual upgrade – in detail.
There's no need to read this guide from A to Z as the chapters can be read individually. Simply use the search function to navigate quickly to the topics in this guide that are especially interesting for you.
New Features - The Highlights
We have been working on our Studio’s interface, releasing various improvements that have the goal to significantly support the users in their daily work and to make it more enjoyable.
Among them:
The Workflow App, which opens fullscreen in a new browser tab, and in the new Studio design.
With the Workflow App, tasks such as localization and publication have both more room and a cleaner work area. This new user interface also gives us enough space for adding new features in the near future which will translate into greatly improved UX and productivity.
New, exciting visual changes, illustrations, and animations, for example a login screen that comes in different variations based on your individual location and preferences.
The new Preferred Site Selector, which enables an improved and intuitive locale and name sorting.
Redesigned Toasts and Notifications, that minimize distractions and help focusing on important messages.
The Content Issue Search, to tidy up your content repository, for example by increasing issue visibility through custom dashboard widgets in Studio. A healthy content repository ensures flawless processing of editorial workflows. But most importantly, it improves the browsing and shopping experience of your customers.
CKEditor 5 as the future foundation for Rich Text editing, to enable new features such as Search and Replace and Source Editing and improve the UX and DX with a modern technical foundation. The CKEditor 5 is currently available as a developer preview.
Technical Changes - Overview
Besides these new features, CoreMedia has done a lot of work behind the scenes. Updated libraries, an improved developer experience, removal of outdated functionalities, and more. While these improvements will ease your life in the long run, they require immediate upgrade tasks.
The following list shows the most important changes in terms of the upgrade effort, while Chapter 6, Detailed Overview of Changes lists all changes in detail. See the http://bit.ly/cmcc-11-supported-environments document for the list of the supported databases, operating systems, and browsers of this release.
Studio client is implemented in TypeScript instead of ActionScript/MXML
TypeScript is a very popular programming language with an active community. There are many experienced developers that will be able to support you with developing your Studio extensions in the future. You first have to convert your existing extensions into TypeScript. CoreMedia provides the necessary tools for this upgrade.
Introduction of new Commerce Hub/Adapter API v2
A more capable and cleaned up API for Commerce adapters is introduced and required. If you have a custom Commerce adapter or have customized one of our default adapters, you have to migrate your existing code to the v2 API. Users of our out-of-the-box adapters need to make sure to use a v2 adapter and update the adapter configuration.
Upgrade to Spring Boot 2.5
In order to benefit from the improvements and new features of Spring Boot 2.5 you have to do some changes in your custom code, especially if you have implemented your own Spring Web MVC handlers.
Removal of the CoreMedia Watchdog/Probedog component
The Watchdog/Probedog component made by CoreMedia is outdated and can be replaced by modern concepts like JMX and Spring Boot actuators.
Removal of LiveContext HCL legacy extension
The LiveContext HCL Blueprint extension has been removed. Existing customizations should be replaced on basis of the Commerce Hub architecture.
Removal of the Chef deployment
In times of container technologies and container orchestration, Chef is an outdated technology and providing an idempotent deployment process with Chef is far more complex and error prone, than using state of the art container technologies. CoreMedia container images are proven to function well in any container runtime environment.
A new container image build process
Container images are now build using the Google Jib Maven plugin. This plugin is designed to build container images without the use of Docker, providing a more secure way to build container images. It also provides reproducible builds with identical image digests on consequent builds on the same source state.
