CoreMedia Content Cloud v13 Upgrade Guide / Version 2512.0
Table Of ContentsThis chapter provides a high-level overview of CoreMedia Content Cloud v13 and highlights the most important changes compared to v12.
It is intended to help you understand the overall scope and direction of the release before diving into the detailed upgrade information in later chapters. Use this chapter to get the big picture and to identify which areas are most relevant for your upgrade.
You do not need to read this guide from beginning to end. All chapters can be read independently. Use the structure of this guide and the search function to quickly navigate to topics that matter for your individual upgrade.
New Features - The Highlights
CoreMedia Content Cloud v13 introduces improvements across several areas, with a strong focus on usability and efficiency. A major emphasis of this release is the Studio user interface, with enhancements aimed at better supporting users in their daily work and making content creation and management more efficient.
Key highlights include:
Semantic Search
CoreMedia Studio has been extended with semantic search capabilities. This allows you to find content items based on their meaning and context rather than just matching keywords. This new feature contains the usage part in Studio and the configuration part. It requires an account at an embedding provider which may incur addition costs.
Technical Changes - Overview
In addition to user-facing improvements, CoreMedia Content Cloud v13 includes technical changes that may affect development, operations, and integrations.
The following list shows the most important changes in terms of upgrade effort. Chapter 7, Detailed Overview of Changes lists all changes in detail. See the https://releases.coremedia.com/cmcc-13/artifacts/CMCC 13 - Supported Environments.pdf document for the list of supported databases, operating systems, and browsers of this release.
Replacing CORBA with gRPC
The migration from CORBA to gRPC modernizes the inter-service communication layer. This change requires updates to network configurations and may affect custom integrations that rely on CORBA. See Section 7.3, “Adding gRPC Support for Component Communication” for details.
Upgrade to Spring Boot 4
Spring Boot 4 is required to build production-ready applications using Spring Framework 7. The upgrade was necessary because of the shortened Support Lifecycle of Spring Boot.
Upgrade to Java 21
Upgrading to Spring Boot 3.2 and Spring Framework 6.1 required upgrading to Java 21 as the minimum Java version as described in the official Spring Framework documentation.
Removal of XML Importer
The legacy XML Importer has been removed. If your workflow depends on this component, you must migrate to alternative content import mechanisms.
Refer to Chapter 7, Detailed Overview of Changes, for in-depth information and concrete migration steps.
