Automatic Updates in AEMaaCS / Blogs / Perficient

AEM Version Updates

Adobe uses a continuous release model in AEM as a cloud service. This means the application is auto updating on an ongoing basis. There are two types of updates:

Feature Releases – these are done on a predictable monthly schedule and are focused on new capabilities.
Maintenance Releases – these can be released on a daily basis and are focused on security updates, bug fixes, and performance enhancements. They have minimal impact since changes are applied regularly.

Note: If the update to the production environment fails, Cloud Manager will automatically roll back the staging environment. This is done automatically to make sure that after an update is completed, both the staging and production environments are on the same AEM version. If custom code was pushed to staging and not to production, the next AEM update will remove those changes to reflect the git tag of the last successful customer release to production. Therefore, the custom code that was only available on staging will have to be deployed again.

Composite Node Store

Updates in most cases will incur zero downtime, including for the authoring instance, which is a cluster of nodes. Rolling updates are possible due to the composite node store feature in Oak. The general sequence of events is as described below, where Blue is the old version of customer code and Green is the new version. Both Blue and Green are running on the same version of AEM code.

Blue version is active and a release candidate for Green is built and available.
If there are any new or updated index definitions, the corresponding indexes are processed. Note that the blue deployment will always use the old indexes, while the green will always use the new indexes.
Green is starting up while Blue is still serving.
Blue is running and serving while Green is being checked for readiness via health checks.
Green nodes that are ready accept traffic and replace blue nodes which are brought down.
Over time, blue nodes are replaced by green nodes until only Green remain, thus completing the deployment.
Any new or modified mutable content is deployed.

Dispatcher Tools and Validations

When you create an AEM project using AEM Project Maven Archetype, it is prepopulated with a set of dispatcher configuration files. The Dispatcher Tools provide a set of Apache HTTP Web server and Dispatcher configuration files that define behavior for all environments, including local development.

A complete description of the configuration files is available in the unpacked Dispatcher Tools as dispatcher-sdk-x.x.x/docs/Config.html.

Use validate.sh script when validating your project-specific Dispatcher configurations against the latest Dispatcher Tools version.

Update the immutable files using the update_maven.sh script

Inspired Digital Experiences for Manufacturing and Automotive Lookbook Cover

Inspired Digital Experiences for Manufacturing & Automotive

Whether you’re just beginning your digital transformation journey or are well on your way, we invite you to explore our partnership with Adobe and our diverse capabilities in manufacturing and automotive.

Download Lookbook