Solving AEM DevOps Challenges, Part 2: Relevant Content

Solving AEM DevOps Challenges, Part 2: Relevant Content

Over the last 10 years of working with Adobe Experience Manager and JCR related technologies, we’ve dealt with hundreds of AEM projects and many processes. We have seen a variety of challenges in dealing with the AEM infrastructure and development landscape, in particular, where those two meet. We asked ourselves, how do we increase efficiency and reliability for both our developers and our enterprise clients while making AEM development feel more enjoyable and competitive with modern frameworks? Our answer is AEM Cloud.

In this series, we’ll discuss several challenges that we see in the ecosystem that we wanted to correct and how AEM Cloud does it. Our first article discussed Inconsistent Environments. This article will talk about the challenge of Relevant Content for Testing and Validation.

Challenge 2: Relevant Content for Testing and Validation

The production instance of Adobe Experience Manager is always the source of truth when it comes to content and, depending on the AEM implementation, this authored content may play a vital role in the configuration of the application. This is also true when a newly developed feature requires a specific content structure to exist in order to function properly. Syncing content across developer, automated testing, and pre-production review environments often ended up as a manual process.

Solution: AEM Cloud Package Tool

To address this we have developed the AEM Cloud Package Tool. The Package Tool will build content packages and make them available to the various environments on a regular schedule or can be triggered manually. This is possible via AEM Cloud’s package repository. You can define a package in any environment and have other environments utilize the latest version of that package. When a new environment is created, it will automatically pull in all the latest configured content from AEM Cloud.

A typical approach is to create a few different content packages in your production environment that are built at a given time. The packages are then automatically uploaded to AEM Cloud’s package repository and environments will pull in the latest packages when provisioned (both local and on-demand).

Want to learn more? AEM Cloud.

Other articles in this series:

Part 1 Inconsistent Environments

Part 3 Slow Development Cycles

Part 4 Cumbersome Release Process