AEM is often used in high impact deployments that might serve millions of users. In most cases, there are custom applications that are deployed on the instances, which add to the complexity. Any effort to upgrade such a deployment needs to be handled methodically.
This guide helps with establishing clear goals, phases and deliverables when planning your upgrade. It focuses on the overall project execution and guidelines. While it provides an overview of the actual upgrade steps, it refers to available technical resources where suitable. It should be used in conjunction with the available technical resources referred to in the document.
The AEM Upgrade process needs carefully handled planning, analysis and execution phases with key deliverables defined for each phase.
Note that it is possible to upgrade directly from AEM versions 5.4 and up to 6.3. Customers running 5.3 and below need to upgrade first to version 5.4 or above, with 6.0 being recommended. Also, the new OAK Segment Tar format is used now for the Segment Node Store, and repository migration to this new format is mandatory even for 6.0, 6.1 and 6.2.
|Operating System||Uncertain, but subtle effects||At the time of the AEM upgrade, it may be time to upgrade the operating system as well and this might have some impact.|
|Java Runtime||Moderate Impact||AEM 6.3 requires JRE 1.7.x (64bit) or later. JRE 1.8 is the only version currently supported by Oracle.|
|Hardware||Moderate Impact||Online Revision Cleanup requires free
disk space equal to 25% of the repository's size and 15% free heap space
to complete successfully. You may need to upgrade your hardware to
ensure sufficient resources for Online Revision Cleanup to fully
execute. Additionally, if upgrading from a version prior to AEM 6, there
may be additional storage requirements.
|Content Repository (CRX or Oak)||High Impact||Starting from version 6.1, AEM does not support CRX2, so a migration to
Oak (CRX3) is required if upgrading from an older version. AEM 6.3 has
implemented a new Segment Node Store that also requires a migration. The
crx2oak tool is used for this purpose.
|AEM Components/Content||Moderate Impact||/libs and /apps are easily handled through the upgrade, but /etc usually requires some manual re-application of customizations.|
|AEM Services||Low Impact||Most AEM core services are tested for upgrade. This is an aera of low impact.|
|Custom Application Services||Low to High Impact||Depending on the application and customization, there may be be
dependencies on JVM, operating system versions and some indexing related
changes, as indexes are not generated automatically in Oak.
|Custom Application Content||Low to High Impact||Content that will not be handled through the upgrade can be backed up
before the upgrade takes place and then moved back into the repository.
Most content can be handled through the migration tool.
It is important to ensure that you are running a supported operating system, Java runtime, httpd and Dispatcher version. For more information, see the AEM 6.3 Technical Requirements page. Upgrading these components will need to be accounted for in your project plan and should take place before upgrading AEM.
A lot of work goes into planning and executing an AEM upgrade. In order to clarify the different efforts that go into this process, we have broken down the planning and execution exercises into separate phases. In the sections below, each phase results in a deliverable that is often leveraged by a future phase of the project.
With any new release, there are potential changes to the UI and user workflows that may be introduced. Additionally, new releases introduce new features that may be beneficial for the business to leverage. We recommend reviewing the functional changes that have been introduced and organizing a plan to train your users on leveraging them effectively.
New features in AEM 6.3 can be found in the AEM section of adobe.com. Additionally, how-to videos for using these features can be found on the AEM 6.3 Feature Videos landing page. Make sure to note any changes to UIs or product features that are commonly used in your organization. As you look through the new features, also take note of any that can be of value to your organization. After looking through what has changed in AEM 6.3, develop a training plan for your authors. This could involve leveraging freely available resources like the helpx feature videos or formal training offered through Adobe Digital Learning Services.
Each customer's implementation of AEM is unique and has been customized to meet their business requirements. As a result, it is important to determine all of the customizations that have been made to the system so that they can be included in a test plan. This test plan will power the QA process that we perform on the upgraded instance.
The exact production environment needs to be duplicated and testing should be performed on it after the upgrade to make sure all applications and custom code still run as desired. You need to regress all your customization and execute performance, load and security testing. When organizing your test plan, make sure to cover all customizations that have been made to the system in addition to out of the box UIs and workflows that are leveraged in your day to day operations. These can include custom OSGI services and servlets, integrations to the Adobe Marketing Cloud, integrations with third parties through AEM connectors, custom third party integrations, custom components and templates, custom UI overlays in AEM, and custom workflows. For customers migrating from a version prior to AEM 6, any custom queries should be analyzed as these may need to be indexed. For customers who are already on an AEM 6.x version, these queries should still be tested to ensure that their indexes are continuing to work effectively after upgrading.
When upgrading, it is possible that you may also need to upgrade other components in your technical stack such as the operating system or JVM. Additionally, it is possible that due to changes in the repository makeup that additional hardware may be required. This usually only comes up for customers migrating from pre 6.x instances but is important to consider. Finally, there may be changes needed to your operational practices including monitoring, maintenance, and backup and disaster recovery processes.
Review the Technical Requirements for AEM 6.3 and ensure that your current hardware and software will be sufficient. For potential changes to your operational processes, see the following documents:
Monitoring and Maintenance:
Backup/Restore and Disaster Recovery:
Due to the wide variety in the amount and nature of customizations that our customers apply to their AEM environments, it is important to spend some time up front to determine the overall level of effort that should be expected in your upgrade. The most efficient way to do this is to perform an upgrade on a test instance and perform some basic smoke testing to see how much it performs. Adobe also provides some pre-upgrade compatibility checks that can assist in this effort by proactively identifying deprecated APIs that are in use by the custom codebase. Additionally, the list of Deprecated and Removed Features should be reviewed not only for the version that you are upgrading to, but also for any versions between your source and target versions. For example, if upgrading from AEM 6.1 to 6.3, it is important to review the AEM 6.2 deprecated and removed features in addition to those for AEM 6.3.
Upgrade a development instance to AEM 6.3 according to the instructions in Performing an In-Place Upgrade. Once complete, perform some high-level smoke testing on this environment. The goal of this exercise is not to exhaustively complete the test case inventory and produce a formal inventory of defects but to give us a rough estimate of the amount of work that will be required to upgrade the code for 6.3 compatibility. When combined with the pre-upgrade compatibility checks that are documented in Upgrading Code and Customizations and the architectural changes that were determined in the previous section, a rough estimate can be provided to the project management team for planning the upgrade.
While Adobe has documented the process for upgrading an AEM instance, each customer's network layout, deployment architecture and customizations will require fine-tuning and tailoring of this approach. For this reason, we encourage you to review all of the documentation that we have provided and use it to inform a project specific runbook that outlines the specific upgrade and rollback procedures that you will be following in your environment. If upgrading from CRX2, make sure to evaluate how long the content migration will take when moving from CRX2 to Oak. For large repositories, it could be substantial.
We have provided upgrade and rollback procedures in Upgrade Procedure as well as step-by-step instructions for applying the upgrade in Performing an In-Place Upgrade. These instructions should be reviewed and taken into consideration with your system architecture, customizations, and downtime tolerance to determine the appropriate switch-over and rollback procedures that you will be executing during the upgrade. Any changes to architecture or server sizes should be included when drafting your customized runbook. It is important to note that this should be treated as a first draft. As your team completes their QA and development cycles and deploys the upgrade to the staging environment, it is likely that the need for some additional steps may be required. Ideally, this document should contain enough information such that if it were handed to a member of your operations staff, they would be able to complete the upgrade completely from the information contained within.
We can use the output from the previous exercises to build a project plan covering the expected timelines for our test or development efforts, training, and actual upgrade execution.
A comprehensive project plan should include:
- Finalization of development and test plans
- Upgrading development and QA environments
- Updating the custom code base for AEM 6.3
- A QA test and fix cycle
- Upgrading the staging environment
- Integration, performance and load testing
- Environment certification
- Go live
We have provided procedures for Upgrading Code and Customizations to be compatible with AEM 6.3. As this iterative process is executed, changes should be made to the runbook as needed.
The development and testing process is usually an iterative one. Due to customizations, changes made during the upgrade could potentially make an entire section of the product unusable. Once developers have addressed the root cause of the issue and the testing team has access to test these features, there is potential for discovering additional problems. As issues are discovered that require adjustments to the upgrade process, make sure to add them to your custom upgrade runbook. After several iterations of testing and fixing, the code base should be fully validated and ready for deployment to the staging environment.
We recommend a final round of testing after the codebase has been certified by your organization's QA team. This round of testing will involve validating your runbook on a staging environment followed by rounds of user acceptance, performance, and security testing.
This step is vital as it is the only time that you are able to validate the steps in the runbook against a production-like environment. Once the environment has been upgraded, it is important to allow end-users some time to log in and go through the activities they do when using the system in their day-to-day activities. It is not uncommon for users to be leveraging a part of the system that was not previously considered. Finding and correcting issues in these areas before go-live can help to prevent costly production outages. As a new version of AEM contains significant changes to the underlying platform, it is also important to perform performance, load and security tests on the system as if we were launching it for the first time.
We have provided some steps in the upgrade instructions for environment validation. These include basic checks like scanning the upgrade logs and verifying that all OSGi bundles have properly started, but we recommend also validating with your own test cases based on your business processes. We also recommend checking the schedule of AEM's Online Revision Cleanup and related routines to ensure that they will be occurring during a quiet time for your company. These routines are essential to the long-term performance of AEM.