Content Migration AMS to AEMaaCS
Published
Content transfer is a crucial step when migrating AEM projects to AEMaaCS, especially with large volumes of content.
To streamline this process, Adobe provides Content Transfer Tool (CTT), which can be used to initiate the migration of existing
content from a source AEM instance (on-premise or AMS) to the target AEM Cloud Service instance.
Setting Up Custom Domain in AEM Cloud
Published
It is good practice to have a Domain for your site that is memorable for customer and reflects your brand's identity.
Adding a custom domain name in AEMaaCS requires interaction between DNS service and Cloud Manager. A user must be a member of Business
Owner or Deployment Manager role to complete this task.
Tailing logs on AEM as Cloud Service
Published
Tailing logs is a very basic need that every developer performs daily, as logs serve as the frontline for debugging
AEM applications. While AEM 6.5 allows tailing logs via the System Console or SSH into AEM servers, AEM Cloud Service no longer
provides this access. Instead, Adobe Cloud Manager supports accessing AEMaaCS logs via Adobe I/O CLI with Cloud Manager plugin,
which allows for downloading and tailing logs. Additionally, Adobe Cloud Manager allows for the download of logs, by day, via
environment's Download Logs action.
Environment Variables and Secrets in AEMaaCS
Published
Environment variables allow AEM code and applications to adapt based on context, enabling different configurations
for development, production, or staging environments. They can be updated or deleted as needed, no code changes or deployments
required. By separating code from configuration, they enhance security and keep sensitive information out of version control.
Update Java JDK to v11 for AEM Cloud
Published
By default, AEM projects are built by Cloud Manager build process using Oracle 8 JDK, but AEM Cloud Service customers are strongly advised
to set the JDK version used to execute Maven to 11 for improved performance, security, and support over earlier versions.
Update AEM Archetype using Repository Modernizer
Published
Viewed111 times
AEM Project Archetype is a Maven template creates a minimal, best-practices-based AEM project. Over the years, AEM Project
Archetype has been revolutionized with significant advancements, introducing many new features and possibilities into AEM projects. The
latest Archetype emphasizing the separation of content and code into discrete subpackages to maintain the distinction between mutable and
immutable content. To align existing projects with AEM’s Cloud Service structure, the Repository Modernizer tool can be used to refactor and
reorganize project packages, separating content and code into the appropriate packages.
Best Practices Analyzer for AEMaaCS Migration
Published
Best Practices Analyzer (BPA) evaluates the current AEM implementation, identifying
areas not in alignment with AEM best practices and offering guidance on how to improve. It also
expedites the assessment of readiness for transitioning from an existing Adobe Experience Manager
(AEM) deployment to AEM as a Cloud Service. This tool generates a report pinpointing potential
areas for refactoring, marking the initial phase of migrating to AEM as a Cloud Service.
Web Optimized Image Delivery for AEM Custom Components
Published
Web Optimized Image Delivery feature of AEM as a Cloud service delivers image assets from
the DAM in WebP format. WebP can reduce the download size of an image by about 25% on average, which
results in faster page loading.