How To Upgrade Your CoreMedia Content Cloud Service (CMCC-S) System

Last updated 2 months ago

"tbd"

What you'll learn

Prerequisites

Time matters

10 minutes

Should I read this?

This guide is for Developers, Administrators \ Project Managers.

Table of Contents

1. Introduction
2. Phases & General Tasks During the Upgrade Process
3. Common Challenges

1. Introduction

If you are a CMCC-S customer, you have the option to perform an AEP Upgrade yourself by using the Self-Service.

NOTE TO US:

INSERT LINK to self-service.
PROVIDE MORE INFO - for example, who / how to contact when help is needed.
A graphic would be nice at this point, too!

2. Phases & General Tasks During the Upgrade Process

Now, we will have a look at each phase and the (most common) tasks during each phase.

Preparation Phase

Task 1: Define the scope and objectives of the upgrade.
Task 2: Communicate with stakeholders to gather requirements and set expectations.

Initiation Phase

Task 1: Assemble the project team and assign roles.
Task 2: Develop a detailed project plan, including timelines and resources needed.
Task 3: Set up the workstream* and sandboxes.

Term Definition - "Workstream": In this context, the workstream is a combination of several things. In most cases, it is a dedicated branch in the code repository, which is then typically pulled with a dedicated pipeline from the CI to typically deploy to a dedicated environment (sandbox). You see, it often says "typically". Because it also works without it. But ideally, you isolate the work from the "everyday business". That’s why we chose the term workstream to summarize Git repo, CI pipeline, environment instance and whatever else is necessary. Some customers even build virtual machines for the developers to deploy. Or some developers set up IDE instances specifically for this purpose.

Code-Migration Phase

Tasks 1-5: Merge codebase; Successful build for frontend and backend; Migrate extensions/ customizations; upgrade external APIs
Task 6: Prepare deployment.
Tasks 7-9: Bug-fixing, documentation, and training.

Testing Phase

Tasks 1-2: Perform developer testing to ensure individual components work correctly.
Task 3: Execute user acceptance testing (UAT) with a select end-user group.
Task 4: Obtain go-live approval.

Rollout Phase

Task 1: Create and communicate the cut-over/go-live plan (including the rollback scenario).
Task 2: Execute go-live.
Task 3: Communicate go-live.

Post-Rollout

Task 1: Monitor system performance and user feedback.
Tasks 2-3: Conduct a post-implementation review and document lessons learned.

3. Common Challenges

Last, but not least: Being aware of the challenges can help to maneuver through the upgrade process as smoothly as possible.

Deployment and Downtime Management: Upgrades can result in system downtime (as it is normal for any CMS), affecting business operations. Schedule deployments accordingly.
Budget Overruns: Unforeseen complications can lead to costs that exceed initial budget projections.
Change Management: Resistance to change can hinder the adoption of new software and processes.
Quality Assurance: Ensuring the new system meets quality standards requires extensive testing.
Security Risks: New vulnerabilities may be introduced during the upgrade process.

Is this page useful?