This is the last part of the journey so you will learn to how to monitor for issues and improve performance once the migration is complete. You should ensure the clean-up of temporary files, review best practices for continuous development and manage logs.
In the previous step of the journey, you learned how to perform the migration and Go-live once the code and the content were ready to be moved over to AEM as a Cloud Service.
This document describes the tools that are available to troubleshoot AEM as a Cloud Service environments:
Debugging AEM as a Cloud Service developer environments is available in the Developer Console for development, stage, and production environments.
Refer to Implementing for AEM as a Cloud Service to learn more about development tools.
As a user, you can access CRXDE Lite on the development environment but not stage or production.
Writing to immutable repositories such as
/apps at runtime results in errors. Additionally, you do not have access to developer tooling for staging and production environments.
Refer to Developing with CRXDE Lite to learn how to develop your AEM application using CRXDE Lite.
Users can access a list of available log files for the selected environment.
Refer to Accessing and Managing Logs to learn how to access and manage logs through UI or from API via Cloud Manager.
If you have questions about access to Cloud Service, contact your Adobe representative or Support for Experience Cloud for more details.
Once the migration is complete, you should document the knowledge gained during this process. Some questions that might help the documentation process are:
You should then share these post-migration learnings with stakeholders and teams inside your organization.
Congratulations! You have completed the AEM as a Cloud Service Migration Journey! You should have an understanding of how to: