Migration Guide to Adobe Experience Manager as a Cloud Service for Partners

Adobe Experience Manager (AEM) as a Cloud Service offers a re-architected foundation for Experience Manager, built upon a container-based infrastructure, API-driven development, and guided DevOps process, allowing marketers and developers to always keep ahead of the curve in customer experience management innovations.

Cloud Service brings together rich out-of-the-box capabilities and extensibility of Adobe Experience Manager with agility of the modern cloud-native architecture enabling brands to meet the ever-evolving consumer demand.

This one-pager outlines the recommended phased approach to transition customers from various Experience Manager deployments to Experience Manager as a Cloud Service and help existing customers deliver connected, continuous experiences on this modern, purpose-built platform for experience management.

See the diagram below for a general representation of the migration journey.

Getting Started with Adobe Experience Manager as a Cloud Service

Developer Journey in Adobe Experience Manager as a Cloud Service

Developing

The fundamentals of code development are similar in Adobe Experience Manager as a Cloud Service compared to the Adobe Experience Manager On Premise and Managed Services solutions.

Developers write code and test it locally, which is then pushed to remote Adobe Experience Manager as a Cloud Service environments.

See self-help resources about implementation for Experience Manager as a Cloud Service to learn how to customize your Experience Manager as a Cloud Service deployment.

Deploying

Developers write code and test it locally, which is then pushed to remote AEM as a Cloud Service environments.

Cloud Manager, which was an optional content delivery tool for Managed Services, is required. This is now the sole mechanism for deploying code to AEM as a Cloud Service environments.

See self-help resources about how to configure and deploy to AEM as a Cloud Service environments.

1. Configure CM Pipelines
   • Production Pipeline
   • Non-Production & Code Quality Only Pipelines
2. Deploy Code
3. Understanding Your Test Results
4. Accessing Logs
   • via CM UI
   • via Adobe i/o cli
5. Operations and Maintenance
   • Configuring OSGI configuration
   • Backup and Restore

Help and Resources

1. Debugging tips and tricks
2. Developer Console
3. CRXDE Lite (Only available on local SDK and Experience Manager Cloud Dev environments)
4. Logs and logging
   • CM Logs (build-unit-testing, code-scanning, build-image, deploy)
   • Experience Manager Cloud Service Logs (aemerror, aemaccess, aemrequest, aemdispatcher, httpderror, httpaccess)
   • Local SDK Logs (under host:port/crx-quickstart/logs)

Moving to Adobe Experience Manager as a Cloud Service

Experience Manager as a Cloud Service provides a scalable, secure, and agile technology foundation for Experience Manager Sites and Assets, enabling marketers and IT to focus on delivering impactful experiences at scale.

With Experience Manager as a Cloud Service, your teams can focus on innovating instead of planning for product upgrades. New product features are thoroughly tested and delivered to your teams without any interruption so that they always have access to the state-of-the-art application.

The transition journey to Cloud Service involves three phases - Planning, Execution, and Post Go-live.
For a successful and smooth transition, you should ensure proper planning and adhere to best practices outlined in this Guide.

The figure below shows a high-level representation of the recommended transition journey to Cloud Service.

Planning

Before beginning your transition journey to Cloud Service, you should familiarize yourself with Experience Manager as a Cloud Service and review the notable changes that have been made to it and also review the features that have been replaced or deprecated.

Execution

Before you start the Execution phase of a project, you should be on-boarded to Cloud Service. You also need to familiarize yourself with Cloud Manager. This is the mechanism for deploying project code to an Experience Manager Cloud Service instance.

Cloud Manager enables organizations to self-manage Experience Manager in the Cloud. It includes a continuous integration and continuous delivery (CI/CD) framework that lets IT teams and implementation partners expedite the delivery of customizations or updates without compromising performance or security.

Content Migration

1. Content Transfer Tool : used to move existing content over from a source AEM instance (on-premise or AMS) to the target AEM Cloud Service instance.
2. Package Manager : used for importing and exporting of mutable content of the repository.

Refactor/Optimize

Deployment/Go-Live

1. Deploy to Cloud Manager git
2. Run customer code through the Cloud Manager Quality Pipeline
3. Deploy to Development Environment
4. [Migration only] Content transfer using packages or Content Transfer Tool(CTT)
5. Perform recommended testing cycles (smoke, QA and more)
6. Promote to the Cloud Manager Production Pipeline
7. Smoke test validation
8. Go-Live

Post Go-Live

In the Post Go-live phase, you should ensure clean-up of temporary files, review best practices for continuous development and manage logs.

Tools & Resources