By moving to Adobe Experience Manager as a Cloud Service, your teams can always stay ahead of the curve in CXM innovations with a lower total cost of ownership. In this training workshop delivered by Experience Manager product experts, get best...
Wednesday, Apr 28 10:30 PM - 12:30 AM IST
Anthony Rumsey - Senior Computer Scientist, Software Development, Adobe | Umberto Andreozzi - Alliance Lead - Italy, Deloitte Digital
Q. We might not resolve all on day one on all items identified by BPA. What are the mandatory ones that we should consider refactor our code (6.4.6) before moving to the cloud? Are there mandatory ones to resolve for cloud migration?
A. The Best Practices Analyzer categorizes findings based on severity levels. We recommend resolving the Critical ones first as those need to be resolved to be compatible with Cloud Service.
Q. Will migrating to CS be easier if we are already using Cloud Manager with our AMS-hosted AEM instance?
A. We're on AEM 6.5.2
It definitely makes things easier, as things you would have had to refactor with respect to your deployment, dispatcher configurations, etc will be well along the way by the time you finish a Cloud Manager migration.
Since you are already on the CM and 6.5.2 makes things better, you still have to go through migration activities and refactor the code for Cloud compatibility.
Q. Can we use the tools to determine the level of effort to move to CS without purchasing CS?
A. Yes. You need to install a BPA package on your on-prem instance and run it.Which will give a report for you to assess. You can get the package from software distribution
The Best Practices Analyzer accelerates the assessment of your readiness to move to Cloud Service. But it doesn't provide an effort estimation in terms of hours or days.
Q. Hi is there any plan for the customer we are currently in 6.5 and not willing to move to CS?? or Only option is to move to CS inorder to get all the new features
A. New features are available on Cloud Service first and are then side-ported to AEM 6.5 at a later point.
Q. Does the User Mapper move groups and rep:policy nodes as well?
A. Hi James, yes, the User Mapper will move groups and rep:policy nodes as long they are associated with the content that is being migrated.
Q. If you already use Archtype 24 we still need to use this tool to modernize maven modules? I am referring to adobeio toolset which helps code repo modernizer.
A. Thank you for clarifying. if you're following the package structure introduced in archetype 23, then you should be in good shape. the archetype is always improving so best to use the latest release if you can.
Q. There are some AEM ACS Commons plugins that are not compatible with AEM as a Cloud Service. Will those be updated/made compatible?
Q. Do you find it is more common for customers to navigate these upgrades and migrations, or do more customers to sync the AEMCS upgrade with a full rebuild of the site application and content?
A. We recommend building on your years of investment in AEM and modernize it to make it compatible with Cloud Service. As you can see, we have also invested a lot in developing tooling to help you with this process. It also depends on your requirements and goals for modernizing and therefore encourage you to work with your customizer who can help you provide the best possible path forward.
Q. How do we update/install new features on AEMaaCS SDK for Local development setup
In particular, scroll down to the "When to update the QuickStart Jar" section.
Q. Can we access to this beta version?
A. Yes, you can reach out to your Adobe rep saying that you're interested in the Cloud Acceleration Manager Beta program.
Yes, Cloud Acceleration Manager is on Experience Cloud and you can get access to it before you purchase Cloud Service. Also, CAM is a free application. Currently, we have a beta program for CAM that you can join by reaching out to your Adobe rep.
Q. How will all the ACLS be sent from the current AEM to cloud author/publish. What is the best practice?
A. Hi Jaimala, yes, the ACLs will be sent from the current AEM to the cloud author/publish as long as they are associated with the content that is being migrated.
So, when you package content,conf, and home the ACLS gets packaged with it,no ACL packaging needs to be done separately, in on-prem we use ACLpackager and install thepackages.
Q. Where is the access token located? Is it in the experience cloud?
A. Hello Anish. The access token is obtained from the cloud service instance you are transferring to. The "open access token" button will open to the required location for you.
Q. How the access to internal services(not exposed over the internet) will work from AEMaaCS?