Adobe has made a significant contribution towards facilitating new capabilities and enhancements in the world of web experience management. Many businesses have leveraged products and services of Adobe Suite in their journey of digital transformation. The Adobe Cloud Manager is one such solution that enables customers using Adobe Managed Services to build, deploy, and manage their custom codebase with ease and efficiency. It reduces dependency on Adobe’s customer service executives to a great extent.
The purpose of this blog is to help the developers, architects, and business practitioners understand the significance of migrating to Cloud Manager and the best practices of successfully completing the migration process.
Check out various significant benefits of migrating to Cloud Manager for multi-brand companies using Adobe Experience Manager (AEM).
First, set-up local to simulate the Cloud Manager environment before starting the project. This can be done by setting up the sonar server/SonarLint. It helps with code quality and coverage. It is always better to find issues in a local environment before building it on the Cloud Manager.
Other steps are as follows:
To understand the steps further, refer to Adobe’s documentation.
When the Cloud Manager Git repository is created and connected to the cloud Manager pipelines, the below-mentioned steps can be followed to integrate an external Git repository:
Here are some of the best practices that you can follow to ensure a smooth migration to the cloud manager.
1. You can overwrite some testing criteria of the Cloud Manager. This helps in meeting the strict deadlines where the development team wants to keep fixing the issues in the incremental approach.
2. In the case of a multi-bundle project, it is always hard to calculate the code coverage in an integrated development environment (IDE) since the code coverage results are for the individual bundles. As a solution, you can set-up SonarQube with JaCoCo.
3. There is always a doubt about the versioning of a project. Cloud Manager adds a random hex to the versions of bundles and packages, which is nothing but a build number in the Cloud Manager. The final version looks like <pom-version>.<build Number>.
4. For estimating the effort of migration, an architect or lead must consider the below points.
5. To make the changes production-ready
6. Upload some heavy assets in the pipeline to test the performance.
This blog is an attempt to share our experiences while implementing AEM with Cloud Manager. This includes estimating the effort before starting the project, simulating the Cloud Manager environment in your local, and integrating with the Cloud Manager GIT repository. Businesses can get a lot of benefits by migrating to the Adobe Cloud Manager and using AEM with Cloud manager, and it’s a step towards ‘AEM as a Cloud Service.’