AEM Modernization Tools

Transcript

Hello everybody, my name is Brian Stauf, I’m a Senior Cloud Architect with Adobe, and in this video I’ll be going over the all-in-one conversion feature of the AM Modernization Tool Suite. The all-in-one conversion feature is designed to perform the other three features that are in the suite as a single operation on the indicated pages for a given job. So those operations are the structure conversion, the policy importer, and the component conversion tool. So with the structure conversion tool, in order to perform the operation you must have the editable template for the conversion tool to have as a target. So in this demo I’m going to be converting the geometric shapes to the home page. This page uses currently a side template, here’s the side template as you can see here, and here is the editable template that we will be converting the page structure to. Now one thing to note that in addition to performing the operations and the conversion operations for the pages, when policies are imported, this tool also will apply any policies to the editable template based on what was found on the individual pages. So what that means is in this case this title, small blue text is a design configuration that will be converted into a policy and then it will automatically apply that policy on the editable template. We can look at the editable template now and look at the title component reference here in this paragraph system, sorry in this responsive grid system. As you can see there is no policy currently applied. Let’s go ahead and look at the JCR for the content that we’re about to transform. If we go over here we can see that this is the editable template and these are the policies that exist in the policy mappings. There is no mapping for the home page title component. We go down to the policies and we look at the title policy list. Let’s see there is only one which is the experience fragment title. If we go down to the content of the page, you can see that it is still in the legacy format which is the paragraph system, header, news list, etc. All these things will be changing as we execute the all-in-one conversion tool. So let’s take a look at the tool now. So we go down here to modernize tools. This is available once you’ve installed the modernization tool suite into your AEM instance. And then if we click on that, you can also then see that we’re going to click on the all-in-one conversion tool. This view is a list of all of the completed or scheduled jobs for the conversion. In version 2.0 of the modernization suite, the conversions are performed as slain jobs. So they are scheduled and then executed asynchronously. And this view will show you any jobs that already have been executed. There’s none now, but we’re going to go ahead and create one and I’ll show you what this view looks like once we have a job that’s been completed. Click on create. Now as with all the tools, a job does require, the scheduling of a job does require job names. We’re going to put geometrics home page here for the job name. Because we are performing page structure conversions, we must also configure that particular feature of the tool suite. In that case, we need to specify how we want to handle pages, handle the pages. So there’s three options for handling a page. First is none. That is, simply convert the page in place as it sits in the repository today. In that case, what you see here. Now the next option is restore. As the all-in-one conversion tool executes or when the page structure conversion tool executes, it creates a version of the page as it processes each page. That version is then tracked on the page as a property so that way if we need to, we can restore back to the pre-conversion page and re-run conversions. This allows teams to change rules or update a rule based on additional information and then re-run already processed pages with the new rules. It will simply revert the page, identify the rules, apply the rules, and then you’ll see the updates once the job is done. Last but not least is the other option is to copy the target. What this allows us to do is, it allows us to select a route path that we want to start all of our searching off of. And then we also get to select a target path that we want to copy the pages to. So when we do this and we select our target, what will happen is all pages must exist under this route and every page’s path portion that matches this will be replaced with this. So therefore, if we were to say, select the Geometrics English page on the next screen and then when we select that page, it will then be copied to Geometrics, sorry, content geodemo and then we’ll access EN. Now because in this particular example, the EN page already exists, the conversion job would actually fail that particular entry because it will not overwrite an already existing page. We’re not going to do either of those options, we’re just going to leave the page in place for processing and we’re going to continue on to the next option list. The next option is the policy import because we are also going to import policies, we need to specify where in which conf we want to save those policies. In this case, we’re going to use the Geometrics demo new conf location which is used by this editable template as its policy storage. So we’re going to go down here. The next option is include supertypes. I go into more detail about this in the policy importer tool. Just be aware that the reason this is disabled and is not allowed to be changed from a selected option is because in order to find the design configurations for the page, we need to search the entire hierarchy for possible references in order to find them and then apply them once the page has been converted. Over on existing, again I go into more detail about this on the policy importer video, but basically you should be aware that this will allow you to reprocess already processed design configurations and it has new policies. Selecting this where a design configuration has already been imported may create duplicates in the repository. That is not going to be the case for us because we are in a clean slate so there is nothing to reimport. So now we’re going to go into the next screen. In this view you will select the pages that you want to process. So as we select the pages we’re going to select the Geometrics demo English homepage. That’s going to be the one we’re going to process. We select that. You can see now that it has found one structure rule, so one template to convert. One policy rule that applies to three different designs will match that policy rule so three policies will be created. There are seven component rules which match ten components on the page. So these are the operations that are going to be performed when we execute this job. It should be noted that the policy rules and the component rules are fuzzy matches. What that means is that it’s possible that more than one rule may match a given node but only one rule will be applied to a given node. That has to do with the fact that you may have prioritization of rules in the system. I’ll go into more detail about how this functions in the nitty-gritty details video which you can find on the documentation site. So now the other thing about this, just like all the other tools, you can add more pages. You can select as many as you want by going into here, selecting another page, or you can choose to select a page and then include its children. When you try to select children you can choose to only include direct descendants or you can uncheck that to conclude the entire hierarchy underneath that node or that page. So I’m going to show you what that looks like now. So it’s going to go through and it’s going to read those pages and it’s going to look them up. It’s going to identify the policies and the components and rules and whatnot that may need to be applied or that will be applied for those pages. Once it’s found all the children, you’ll see that it’s going to set its 31 conversions and it shows the list of all the different children here. Now I actually don’t want to schedule this job to have more than one. I’m just going to go ahead and unselect everything and bring us back to just the one page. You can choose to add more than as many pages as you want to a given job. If a job is more than 500 operations or 500 pages really, then it will be split into multiple jobs. Each job will have a maximum of 500 operations. A job is completed as a single atomic save. So as it goes through the process it converts the pages and components and templates. Once it’s done it saves them all in one fell swoop and then the next job is scheduled. Only one job can run at a time, but you can have as many you can add as many pages as you want. Once you are ready you can schedule a job here by clicking schedule job. It will confirm that you really want to convert this page. So yes I do. And then we’ll move over to the job detail view. This job detail view shows you the paths that have been requested to be processed. And if you look on the left here you can see that there is a bucket list. If you have again you have more than 500 items in the desired list it will create a bucket for every 500 or portion thereof. And each bucket is its own job in the Sling Job Scheduler. We don’t have an example for that particular view at this moment, but just know that there will be multiple buckets here with the number of items in each bucket listed for the operation. Now right now the job has been scheduled but it’s an unknown state because it has not finished execution or at least to our mind it has not finished execution. Let me refresh the screen and we can see what it has done. And once I refresh the screen you can now see that the job has been completed. We have a success on the page and the bucket is overall successful. We can now return to the list of all the jobs and we can see that here is the job that we just executed. In a card view we also have a list view available which you can then see. This shows you when it was executed and whether or not it’s a multi-bucket. Multi-bucket basically means whether or not there was more than one job that you executed. If there was multi-bucket in the list view it will have a little check box right here. If it’s in the card view it will look like a stack of cards as opposed to a single card. Let’s go look at the page that just got converted. So here’s the page pre-conversion. Let’s refresh the screen and take a look at it in post-conversion. Well, and here we have it. So as you can see, it does look a little bit off and that has to do with the fact that I don’t have any of the proper CSS rules for the new editable template, but as you can see it has been fully converted. The lead component is here, the right teaser is here, the image, title, and text components are here. For this particular component, we’re going to have to go to the next section. So we’re going to go to the next section and we’re going to go to the next section. So here we have the editable template structure. For this particular conversion, what we decided to do was use the responsive grid. Instead of having column controls, each of these columns became a container in the parent responsive grid that you see here. Let’s take a look at the JCR. So if we come back to this page inside the JCR and we refresh this, we now see that it is a container, right container, and inside that is our lead container. You can see here is the left container and the right container that used to be the column controls. Now if we go up to the policies that were created, we can click on title here and refresh, and you’ll see that there is a title that was created, or title policy. Just click on that. You can see that it was converted, so this is a new main container title policy with each three as a rule and three allowed types. If we go back to the editable template, we saw before that this component did not have a policy applied. I’m going to refresh the screen so it looks up the reference again. And once this page loads and we can click on that component and look at its policy, we can see that, here we go, the policy has been applied, main container title, properties are all set. So that allows us, the all-in-one tool allows us to apply policies as the pages are converted. It will apply the first policy of fines for a page conversion process for the associated editable template. That’s everything for this particular tool. Thank you for your time.