Migrating to the Cloud - Part 1

Transcript

Hey James, how you doing? Hey Darren, I’m doing well. It’s great to see you. I’m really looking forward to learning a little bit more today about AM as a cloud service. So I’d like to introduce to you and the audience our first ever guest, Dr. Applesmith. Thanks for having me. I’m truly honored to be the first guest on cloud 10. It’s cloud 5, Dr. Applesmith. Dear boy, there are more than five kinds of clouds. There are cumulus, cirrus, stratus, nimbostratus, altostratus, cumulonimbus, and cirrostratus just for starters. Cloud 10 might be a more appropriate name. This initiative doesn’t talk about literal clouds. We talk about cloud-based marketing solutions. Oh dear. I do believe I should have at least read up on this or watched an episode before appearing. Regardless, can either of you explain the four stages of cloud development at sea level? I’d like to talk a little bit about migration to AM as a cloud service. Now let’s say you have an AM 6.5 instance that’s operating normally on prem or even on our Adobe manages services infrastructure, and you need to move that cloud to cloud 10. content to AM as a cloud service. The first step you have to take is the evaluation steps. One of the first things that should be completed is this evaluation to make sure that the content you are planning to move will actually work with AM as a cloud service. This is usually completed during the pre-sales phase, but can obviously change depending on scope changes and other factors of the projects as things start executing. So you should complete this fitment or sizing operation at all times to make sure that nothing has been missed. Now, the easiest way to get started evaluating your targeted experience manager is to install and run the best practices manager or BPA. It’s supported all the way back to AM 6.1, and you’ll want to run it on a production or the closest analog to production like stage, preferably clone, and it’s important to have the content fully represented on the analyzed instance so that it can accurately assess the sizing needed. The end result of the BPA is a file that can be uploaded to the cloud acceleration manager or CAM within the experience manager landing page of your program for analysis. Clicking on the migration complexity assessment tab within the report will give you all the details you need to consider when planning a migration to cloud service. For example, if the report indicates that you exceed one of the limits, then action will be required to mitigate those issues before initiating the migration. So there’s another tool that you can use that only considers the raw repository content without considering best practices. It’s commonly called Repostats and can be useful for managing size and the health of your repository. The link’s down here below. However, I would still recommend using the BPA tool, as James mentioned, as it provides other project-based best practices and ranks them based on severity. You’ll find stuff like the old XJS dialogues that are integrated in foundation component usage that will arise from analyzing those older experience manager projects. Exactly, Darren. And this leads us to the next step, modernization or issue mitigation. Now the content we’re presenting here is limited to the migration process itself, but you can find a handy tool set called the AEM Modernization Tools, which can automate the refactoring of some of the common older structure and component practices. The link is provided below. And another handy set of tools that you can use in this is the Cloud Service Migration Tools. This tool set will help get your project structure in shape for compatibility with cloud service. Now this is for your project structure, not your content structure. And the link below is available if you want to check this out. Now, with some simple setup, these tools can really whip your project into shape and be ready for migration. Now, if your migration plan includes the use of the content transfer tool, and most projects do because you have a significant amount of content that you need to move over, you’re going to need to upgrade your instance to version 6.3 or greater, as that’s a minimum version supported with this tool. And we’re going to talk about the CTT or content transfer tool in part two of this video and give a demo of it in action.