AEM Best Practices Analyzer for on premise and AMS environments

Transcript

All right, Aditi, feel free to start. All right. Thank you so much, Goran, for those introductions. Hello, everyone, and welcome to the session. We are here to talk to you about some really cool tools that we have developed over the last couple of years. And these tools are being used by many of our customers extensively. And so we’d like to share a little more information about these tools, how they work, how they add value for you. And so we really hope that you find this session to be useful. And please don’t hesitate to ask your questions via the chat pod. All right, so as I mentioned, we’ll talk about some tools, we’ll show you some demos, and then we’ll open it up for some Q&A. So let’s start with the first one. It’s called the Best Practices Analyzer, or BPA for short. So the BPA, it’s a tool that provides analysis and reporting capabilities regarding an AEM instance. It generates an assessment of your current AEM implementation by indicating areas that are not following best practices. And it also provides you with some guidance as to, you know, what is that next step you need to take so that you can, you know, fix some of these potential issues. Now, our motivation behind developing the Best Practices Analyzer was to, you know, empower and enable our customers and partners so that they could self-assess their AEM implementation, they could identify and address opportunities to optimize their, you know, implementation. Because even by, you know, addressing that one issue, there is opportunity to reduce technical debt and, you know, lower cost of ownership. And so, you know, this tool is being used by hundreds of our customers. The value has been proven. And regardless of where you are, you know, in your journey, meaning maybe some of you are, you know, you’ve purchased AEM as a cloud service, you’re planning your migration journey, you know, this tool is still valuable for you. And maybe some of you, you know, haven’t, you know, made that decision yet. You haven’t purchased cloud service. You are not planning to move to cloud service anytime soon. This tool will still add value to you. And I’ll go into that in a little more detail. So I’d like to start with a little more detail about the tool itself. Some of you may be familiar with the pattern detector. So this tool is built on top of pattern detector. It performs an analysis on the current state by checking against the patterns that we have added. And we are continuing to add more patterns to, you know, increase our coverage of, you know, assessing an AEM instance. So the generated report, it displays a summary of all of the findings and then classifies these findings based on the severity level. So this is where you can, based on, you know, where you are in your project. So for instance, if you are planning to move to cloud service, you can identify the areas that you need to focus on based on the severity level, which is critical. So critical findings are those that you need to focus on so that you can fix and make your content and code ready to be migrated over to AEM as a cloud service. Now let’s say, you know, you’re not planning to move. You just want to understand how to better optimize your AEM instance. How to optimize your AEM implementation. You can then focus on those major findings that the BPA report provides you with and, you know, identify those areas of improvements. So that’s how you can use the severity level to figure out where you need to focus based on where you are in your journey. So the best practices analyzer, a couple more points about it. One is that you can run a clone of your production environment because that is going to give you an accurate assessment of your implementation. And Himani is going to go into a lot more detail regarding how to run the BPA. So the first thing that we recommend is that you run a clone of your production environment and that is going to give you an accurate assessment of your implementation. So with this understanding of the best practices analyzer, let’s move on to the next one, which we call Cloud Acceleration Manager, or CAM for short. So our motivation behind building the Cloud Acceleration Manager was to provide a one-stop experience to our customers and partners so that they could assess their existing AEM implementation and then, you know, get a better understanding of their application. So we wanted to provide them with a way so that they could navigate and manage their journey to AEM as a cloud service following Adobe’s recommended migration methodology. So the benefits as listed here, CAM does help you plan better and smarter. It provides you with a content assessment, code assessment. It streamlines your migration journey. It has built-in contextual help. So wherever you are in your journey, it will provide you with the right help at the right time. And it also provides you with automation tools so that you can optimize that migration effort. Now, again, if you’re not planning to move to cloud service, Cloud Acceleration Manager still provides you with a lot of value because it gives you a visual representation of your best practices analyzer report. And so you can focus on the best practices assessment. So, again, focus on those major findings, identify those areas where you can continue to optimize your current AEM implementation. And we also provide you with a feature that we call trend analysis. And so what this helps you with is it helps you keep track of your progress. So let’s say you ran your BPA today. You identified some of those findings and you fixed those. And then you come back after a month, you run it again. And then when you upload that report into Cloud Acceleration Manager, you can now see how those findings are trending over time. So that’s a screenshot that you see on the slide. It shows you over time how you’re doing with your optimizations. And so Vaibhav and Kiran will be talking a little more about Cloud Acceleration Manager. They’re going to show you a demo. So with that, I’m going to hand it over to Himani to give you a demo of the best practices analyzer. Thank you, Aditi, for the valuable insight. So now I would be presenting on how we can actually use the best practice analyzer on our AEM instance. So this is the software distribution portal. This is the portal where you can find the software related to AEM and download them. Over here, we find the best practice analyzer package, the latest version. We can download the package from here. Once the package is downloaded, we need to go to the CRX package manager of our AEM instance. It needs to be uploaded and installed like any other content package on AEM. Once the package is installed on your AEM instance, we need to go to the AEM start screen. We need to navigate from tools to operations. Over here, you’ll see a lot of tiles. We need to click on the best practice analyzer. This is the UI where you need to click on the generate report button. Since the report generation takes a significant amount of time, and to save that time, I’ve already generated a report for my AEM instance. So this is the AEM best practice analyzer report. I would now be going through various sections of this report. The first section over here gives us the report overview. It has the findings such as the report time and the expiration time. Once the report is generated, the expiration time for a particular report is set to 24 hours by default. But it can be configured according to your own requirement. Next, we have the generation time period, that is the total amount of time that it took for generating this report. It next has the total number of findings. So each finding in this report is a deviation from the expected best practice for an AEM instance. So for this AEM instance, we have total 88 findings that we will be discussing further. It also displays the BPA version, which is used to generate this report. It is recommended to always use the latest version of BPA for generating your report so that you are in sync with all the new features that go in. The next section is a classification of this total number of findings on the basis of finding type. For each finding type, we again have a classification based on the importance level. We can quickly discuss the importance level for these finding types over here. The findings which are listed as info are only for information purpose. They will not break the functionality or lead to performance loss. And it is good that you look into it. The findings that are listed as advisory are potentially lead to upgrade failures. So it is better that you address it and make sure that no failure is caused. The findings which are listed as major would definitely lead to an issue during an upgrade. So they must be addressed. The findings which are listed as critical in this section would lead to loss of performance or functionality and they must be fixed immediately. The next section in our BPA report is the AEM system overview. This section gives us the general information about our AEM instance. We have a lot of information such as the AEM instance type, the AEM version, the companion products such as forms, commerce, the data store type, the node store size. We also have information such as the CQ tag count, the smart tag count, the total number of vanity URLs, what is your use and index size. So instead of going over the JMX beans again and again, you can get all the information handy in this particular section. Now if you want to get more detail about this information, you can simply go to the documentation and get the relevance of each of these information. The next section that we have in our report is a detailed analysis of all the findings. You can either scroll through these findings or you can simply go to the table that we discussed in the beginning. Now if I want to go to a particular finding and see its detailed analysis, I can simply click on the count over here and it will take me to that particular finding and show me the detailed analysis. So the first column that it shows is the severity level which is associated with this. It gives us a short description about what this particular finding is about. Like we all know that we have navigated from classic UI and it is no longer supported. So this section shows us the custom components which are still using the classic dialogue in their implementation. More details around the risk that it could induce and the possible solutions can be found at the public documentation. So now we look at the table that is present here. We can see that it has some parts and a message. So this part is to the particular custom component which is using the classic dialogue. From the message we can see how this particular type component is creating a deviation from our best practices. It will also give you a deep solution for mitigating this finding. So let’s quickly copy this part from here. Now CRXD will paste this part. We can see that yes, this particular component is using the classic dialogue. Now if we want to mitigate it, we’ll simply go to the documentation. Look at the possible solution and use that to mitigate our finding. Since the number of findings can be very large at times for some instances and if it exceeds a particular limit, for example, 500,000, it is not readable. So for enhancing that experience, we have limited the number of findings to five. By clicking this button, you can view up to 20 findings on the BPA UI. We can also discuss another finding such as the upgrade misconfiguration issue. If we look at it, it shows us the name of our OSTI configuration. Now if this particular OSTI configuration is not set to its expected value, it leads to JSP compilation failure and hence loss of functionality. So from the message we can see that these particular properties in our OSTI configuration need to be set. So we can simply go to the configuration manager, search this configuration, and rectify the properties and it will be resolved. So these are about the sections. Now let’s quickly discuss the buttons that we get in the header of our report. As I discussed in the beginning, the expiration time for our entire report is set to 24 hours. Now suppose you’ve done some changes in your AEM instance and you think that it would impact the BPA report. So you can simply click on the refresh report, it would invalidate the existing report and generate a new one which would have the latest state of your system. Since I also mentioned that the total number of findings which are listed on the UI is limited to 20. So now if you want to view the entire report, you can download it in the form of a CSV report. This CSV can be viewed over here. This CSV has a lot of details which can be used for analyzing the entire report perfectly. But instead of going through the CSV, we have a tool, CAM, which will help you better for analyzing your entire BPA report. And for demonstrating that, I’ll be handing over the control to Vipar. Thanks Aditya and Himani. Hi everyone. We’re above this side. We’ll take, we’ll proceed this session further. We’ll discuss about Cloud Acceleration Manager for BPA report analysis. It gives us the better insight and analytical representation of BPA report. For accessing this tool, user need to access the Adobe Experience Cloud page. If user has access on software distribution page to download the BPA package, then he or she can access this page as well. At the corner of this page, you can see the Adobe ID and the organization. As for me, it is software distribution. To access the Cloud Acceleration Manager, you have to click on this experience manager. It will learn to you on this screen. Here you will see a couple of more options based on your access. For accessing the Cloud Manager, click on the launch button of this tab, Cloud Acceleration Manager. Here you can create a new project. For creating a new project, click on this button, create project. You can give the name of this project and any description, whatever you want to, and just use this button. For the demonstration purpose, I have already created one project by the name of gem session. Over this project card, you can find a couple of basic information of this project. As I have already uploaded a couple of reports like number of seven, so here you can see this number is seven. And I created all, that’s the timestamp when I created this project and the owner of this. Further, you have to click this object. Here you can see a couple of more tools. Certain tools are for the refactoring of the AEM and analysis of AEM instance. To access this, we need to access this best practice analysis. Click on this review button.

Yeah, so if you want to upload a newly generated report, then you can simply click this upload report button and you can upload any new report. Here you can see different section. First section is report properties. It has basic information about the report like report generation, date, duration, BPA version, AEM version, AEM host information. Second tab is report overview. Here it shows the total number of findings for this report. Total number of findings 88 here in this pie chart color indicates different importance level. As Himani and Ariti had already discussed in our talk, as you click on this card, it will take you to the report tab. It shows the further detail of findings. These are grouped based on the type of type, subtype and importance level. Here you can see the count of each type, subtype. If you want to get more details for any type, you can just simply click on this icon. Let me open and get the details for assets content validation. After clicking that, you will see this screen. Here you can get the information of type, subtype and description of this particular finding. So here the type is assets content validation. It validates the metadata of content and missing mandatory nodes. Here subtype is missing original rendition. It is the second level of finding type. It checks whether original rendition is present or not since their message was closed and there is the rendition on the basis of original rendition. The missing original rendition can impact the workflow process. For more details, you can click on this link, learn more. It will take you to the public documentation of this finding. Here you can check that the code of this finding is ACV. You can read the background, what it is. So you can go through that background. You can get more information of subtypes and possible implication in this and the possible solution. So based on this solution, you can refactor the code and use the following guidelines. In the next section in the items, you can see all the parts which is related to that particular finding. If you want to copy all the parts in one go, you can click on this and it will be copied to the clipboard. Similarly, you can traverse or you can navigate to any other finding and check the information. Let me check it again for that second one is like unsupported repository structure. Here you can see the type is unsupported repository structure. Subtype is node location. It validates if any node which is created under etc path, if it violates the best practice guidelines, then it comes in this finding type. So again, if you want to copy that path, you can just simply this one. So here is this one drop down to filter out the findings. If you want to specifically select any finding, just click on this one. Let me select this assets content validation. So it will show only this one. If you want to again filter out, you can select any of the important. So currently for this report, we have only one. This is critical. If I select anyone else, there will be no second section is best practice assessment. It will give you a more deep understanding of reported findings in the first table of this tab. You can see that a version instance type Java version production core components. Scroll down further. You can see that it is important findings on custom component and template. Basically, these components and templates are created by the customer. So it checks it validates those custom components, whether these are as per the guidelines or not. If it if any findings by any kind of violation find in these custom component template, it goes here with the content assessment. Further, we can. There is one more section is additional finding here. You can see that. So whatever we find in the legacy, you are. So it would. So it’s a category and for that one and it will give the assessment as well. So here you can read that best practice is to look at your to use the technical data. Further, you can get the information of slope queries. So you can get the queries held here as well. You can get the information of the time, duration and trigger count. You want to troubleshoot further for those. You can directly simply click on this link and get the information how you can troubleshoot. Furthermore, you can get the information for the maintenance task as well. If you want to read and get the information, the last state of the particular maintenance task or last time, you can get all that information. The next section is complexity assessment. It is more inclined to cloud migration. If you want to assess your instance for a service migration, then you can evaluate the report here. In case you want to learn more about the section in detail, please let us know. We can set up in another dedicated section for this. You can get on pool as well in this report. If you go further, you can see the code assessment content assessment will go down in this report. You can see the health check for the listing indexes here. It checks if customer has modified any indexes, then it checks whether that modification is for the best practice guidelines or not. If it is not, then it will give the alert and if it is, then no, it will change screen and it gives the size of that particular indexes. If you want to check that then graph of the report, you can just do that timeline report mode. Here you can see that that a graph line for that particular importance level. A customer can upload multiple reports as well for instance, like here I have uploaded multiple reports. Here you can change the level from this drop down. If I select it, it will come here. So it shows the progress of that particular instance over the period of time, like in July 2020 that number of financial like this and it went like this. So you can check the progress and how you are making the changes. Similarly, you can analyze for the custom component templates. You can select if I select inherited foundation component and I can select anyone or I can analyze how it is going. So you can analyze your implementation journey. It can help reduce the total cost of ownership and bad code for the instance. If you want to share or for this board, then you can print this as well. So you’ll have to switch again. You’ll have to select the current report and if you will click on this print review, then it will look like this. You can directly download it. And if you click on this button, you can get the printable PDF format so you can see it further for the analysis. That’s all from my side for the game. Over to Kiran. Thank you very much. Can you share my screen? OK, great. Thanks everyone for joining. So the team has given a quick overview of what BPA is and what CAM is. Now, I would like to walk through some real time use cases and how can we get all this information going into the development streams to whether you are in the stage of optimizing the existing solution or if you are upgrading from one AM version to another AM version or when you are migrating. So it’s all. OK. This probably would be a little bit better. I’m sorry for not starting this slide. So going back, as I said, we the BPA report itself gives a whole lot of information for sure, because it scans through all the content that is available, all the code that is available, and it detects a lot of patterns and provides a lot of information and throws it as right. So I was kind of thinking to based on my experience working with customers, how customers in different stages use all that information. And I’ll give some strategies and insights for you to take back and, you know, and that motivates to run the report and look at these things and take some actionable items. So, for example, BPA report collects and gives a certain information such as, for example, the core component version or ACS AM comments version. And that’s the easiest place to see whether you’re running on the latest core component version or AM, you know, ACS comments version and also critical information such as it will show the total number of components and total number of templates. So that are available if you’re a site’s customer. If you have more, way more than components, sometimes it’s like eye opening when we look at some of the customers BPA reports, they have like 125 components. And if we go back and ask them, are you using all these components, then that probably comes as an answer saying that probably we don’t use all of them. And another area is if you look at the whole group memberships and the number of groups available in the system, which is kind of reports that, okay, hey, you have this many number of groups. And the nice thing in the report is it will tell you exactly how many number of users available in that group as well. So in one customer scenario, I have found like there were 80 groups for 20 users. Could it be a mistake? Somebody created some groups and they were never used. And at the same time, if you see there are a lot of number of users ended up in AM administrators group that is causing it, I mean, basically raising a red flag. So that gives you an action item to look into your overall permission model to see what is going on. And another important area is the maintenance task status. So BPA report clearly reports what are the maintenance tasks that are being successfully running and what are not running. For example, if your audit purge, version purge, workflow purge, or using cleanups and data store, call based collections are not working, the BPA reports it. I know you have another means of looking at it as well. But if you put a lot of these data points together, it gives an actionable item. For example, let’s say in the BPA report, you have 50 million nodes. And out of 50 million nodes, if you have like 40 million nodes in the versions themselves, that tells us that the version purge is not working. That gives us an action item to go and make sure that your version purge configurations are how long and how many versions that you’re keeping in the system to be reviewed and de-configured. So if you put the data points that BPA is giving together, it will give some actionable items. And other areas that I would encourage everybody to look at is the slow queries and the number of vanity guardouts that we have set up, which directly have performance implications on your system. So those are some of the common areas. And now I’d like to focus on specific BPA codes. So I have put the full forms for the BPA codes. It’s super easy to decode them whenever it says ASO. That means AM system overview, DZ to offer guidelines, LEI, legacy user interface. So it’s like for the sake of shortening those things, we shorten them in the reports, but we have the full forms. So in this table, what I try to do is based on my experience interacting with the customers, no matter where, which stage that you’re in, let’s say for example, you’re on AMS or on time, you’re not in the stage of migrating. But if you have some development cycles or if you have some intention to optimize your system, then if you are a foundation, sorry, if your site’s an assets customer, the foundation applies for everybody. If you’re a site’s customer, look at those codes. If you are an assets customer, look at those codes closely. If you are in the optimization phase and if you’re upgrading, look at these codes in the migration. Look at this. Right. So let’s quickly go through some of these, you know, course and how they basically give you value by looking at them and taking the actionable things. So the URS is nothing but the unsupported repository structure. So anybody who has been here for longer from AM 6.0 to 6.4, 6.5, there was in 6.4, there is an introduction of repository restructuring. The primary reason being to separate out the customer code and product code for various reasons. So for it could be, you know, frictionless upgrades or it could be for making sure that the custom code is not stepping on the product code or upgrades are not wiping off the custom code. So there are scenarios. No customer implementations doesn’t take care because there is backward compatibility, but leaving them there, they work. Like, for example, you could leave the time-lapse or workflow models in the XE, they still keep working for you. But when it comes to the point where you are upgrading or migrating, it’s going to be a problem. And at the same time, you know, increasing that, you know, overall tech depth and you’re kind of moving further, further away from best practices that we are providing out there, we are putting out there. So it’s better to take a note of those things and making sure that you’re closely taking some of these items into your ongoing sprints and working at these things. And system overview, I already spoke about it. It gives the total number of nodes that are in the system. And if you see that there are a lot of nodes ending up in the Russian stories, please take a look and see what’s going on. Group membership, we touched on it. And another critical item is unprocessed assets. So as we all know, if you are an assets customer or even size customer, when you upload assets, they are going to be processed by, you know, ImageMagick if you’re a configure or if you’re doing any processing for those things. But if they are failing, that means there is something going on. So if you are ending up with a lot of unprocessed assets, so it gives an action item to look at what’s going on. Could it be your custom workflow process that is failing or something is going on to take a look? And moving on to the sites, especially. So sites big ticket items are Legacy is an interface and using the eXt.js dialogues. And we are crazy to use core components, editable templates, the modernization tools is a great way to start. And we have released recently modernization tools 2.0, which has a ton of features. So please take a look and then again, follow the process to modernize your content to best leverage all the advanced features, which would obviously increase your content velocity. And also, you don’t have to manage all the components by yourself. You’re utilizing core components and proxy patterns and component guidelines. So and PCX is a page complexity assessment. So we think that any page having a lot of sub-nodes is going to cause performance implications based on what we have seen. That’s why we are reporting the PCX factor in there. So if a page has a lot of sub-nodes, see whether it is still required or can you take an action? And moving on. So if you’re an assets customer, I would encourage you to take a look at your overall asset health. So asset content validator is the basically is the code that we give. And under that code, we have sub-codes which will give more information. So let’s say, for example, there are lots of assets that are having missing original editions. So missing version edition happens basically whenever you upload an asset and then the asset node has been created, but the binary somehow didn’t get there. So it could be several reasons. It could be a customization that is holding it back or some network issues or whatnot. And also, if you have an asset without original edition, obviously that asset when it is used is going to cause some issues. So it’s better to take a look and then clean those things as well. And also, if whenever you are creating some folders, if the JCL content for that folder is not getting created, that means rather what the settings that are setting at the parent folder are not propagating. So that’s going to cause issues as well. So in summary, there are a lot of information. There is a lot of information that comes in BPA and putting all of this information together, no matter which stage you are in. And whether you’re a site’s customer, an asset’s customer, or sites and asset’s customer, it gives a lot of actionable items that you could slowly keep taking into your development sprint and get closer to the best practices. So with that, I would hand it over to Aditi, but I’m going to share the next slide.

Thanks, Kiran. So this brings us to the end of our session. I hope you found it useful. There are some takeaways that we wanted to put on the slide so that you can take those next steps. So first, Kiran spent a lot of time talking about those BPA patterns, and we know there’s a lot in there. So please familiarize yourself with those BPA patterns. So Hemanee went over how to install the BPA, and this is something you can do today. You can run your BPA on your environment, on a clone of your production environment, and get that first step done. And Vavil spent a lot of time showing you how to use the Cloud Acceleration Manager, or CAM for short. And this is available to all our AM customers. He showed you that all you have to do is log into your Experience Cloud, and you’ll see that card. So upload your BPA report, get more insights about your current system, review your findings. And you can also reach out to Customer Care. You can share that report. Vavil showed you how to create that report, how to create a downloadable version of that report. Or you could also share the CSV file that the BPA generates. So there are lots of options here for you to choose from. And finally, the next slide will show you some really important links. Kiran, if you…yeah. So the first one is the BPA patterns, link to the BPA patterns, understanding them. Then the second one is, you know, how do you start using the BPA? And the third one is how do you start using the Cloud Acceleration Manager? All right. So this brings us to the end of our session. And I guess we will open it up to some Q&A. Great. Thanks a lot, Aditi and team, for your presentations and demo. So let’s move on to Q&A. And while we’re waiting for questions to appear, I would kindly like to ask to complete our ending poll. It’s just a brief general and anonymous ending poll. You will complete this in about two minutes. We’ll post it in general chat. On the right-hand side. Okay. Let’s look at the questions. Okay. There is one. What is the most efficient way to migrate from AM65 to AM as a cloud service? Is it better to use Cloud Manager and AMS first or migrate directly to the cloud? Sure. I can take that. And then maybe, Kiran, if you wanted to jump in, that would be great as well. So again, you know, if you are on AM65, like on-premise, you don’t have to go to AMS first. You can directly move to AM as a cloud service. So the first thing, again, what we recommend that you do is run that BPA tool on a clone of your production and then upload that report into CAM. And so since you are thinking of moving to cloud, you should focus on those findings that are marked as critical and resolve those first. So that is the best way to move to AM as a cloud service. And Cloud Manager, I mean, that is a CI CD tool that you have to use to deploy your code, you know, into cloud service. So I hope that helps. I don’t know, Kiran, if you wanted to add something to this.

Yeah. So as I mentioned, you don’t have to go to AMS because all the tools that are required to migrate, could be content migration, content transfer tool, or BPA or any other tool that we develop are compatible with on-prem. So I don’t see a reason why you don’t. You have to go to AMS, number one. Number two is Cloud Acceleration Manager is your portal that would give you guidance around what phases that are involved. So I would highly encourage everybody on the call, even if you have not trying to migrate, Cloud Acceleration Manager, we have put together such a way that it’s going to be a single point of contact. It will give the phases, could be a readiness phase in which what you would be doing, an implementation phase. So you have decided you are ready now. We have fixed all the issues that are available that have come from BPA. And then in the implementation phase, what you’re going to do and in the go live and post whether what you’re going to do. It’s all pretty much laid out in the camp. I encourage you to take a look at that.

Thanks Aditi and Kiran. Next question is in general, who is responsible to apply the recommendations in BPA? CSE, customer or customizer? Sorry, I’m trying to understand this question. When you say who is responsible to apply the recommendation in BPA, meaning like a slide finding, sorry, the resolutions of it or not sure I quite follow that question. Maybe I think I can try to decipher that question. So the mostly the problems that BPA report is going to identify and report is either on code or content. So the code pieces must be fixed by the development team, whoever is involved, whoever is aware of the code intimately. And the content pieces primarily driven by the business users. So let’s say for example, as I was mentioning, if you have an asset that doesn’t have an additional condition, now you are making a decision to delete it or re-upload it. I think that is going to go to business users. I think the CSE, if you are an AMS customer, will come into picture only to click the buttons, not resolving any of these things. So I think it’s primarily driven by customer or customer implementation team with the help of CSE to apply those changes. Right, right. Yeah, so it depends if you have a partner helping you, then obviously you can involve the partner in the implementation. Correct. Yeah. Thank you. Thank you. The next question is, is BPA is compatible with all the versions of AM? Yeah, so the BPA works for AM 6.1 and above.

All right. That was a straightforward answer. We answered all the questions. There’s just one popped up. Can the BPA report be stopped? The BPA report, once you start generating the report, I don’t think we can stop it. So you would probably have to wait until it completes generating the report. So we don’t have a cancel button, if that’s what you’re asking for.

And to add to it, we do have a progress bar which would notify how long will it take.

All right. Thank you. The next question is, currently BPA doesn’t cover dispatcher best practices. Is there something in the pipeline? So I don’t know. Maybe I’ll try to take a hit at that question. As you see, technically, the way BPA works is BPA goes into JCR. And basically whatever is available within the JCR is, is it what it’s going to look at. So that’s how the tool has been designed. The dispatcher configurations generally are separate. They are deployed onto the dispatcher, even though they are in the code repository, they are never going to get into JCR. So that’s why BPA generally don’t have the ability to collect the dispatcher best practices. But you could use the dispatcher, the migration tools and the SDK if you are migrating to AMS cloud services, you could use the dispatcher refactor tool. And is that as your primary guide to fix the issues? Thank you. Okay. I see some questions popping up in the general chat. To everyone, please use the Q&A tab in chat to post your questions because it’s easier for us to answer and you have additional features. Okay, so which is recommended instance to run BPA author or publish? I would say both because each of them have their own content pieces. Generally, if you run BPA on the author instance, that’s that’s what is heavily used with respect to the customizations. And also, obviously author is going to have more content. I would recommend to run an author, but there is no harm in running unpublished and finding any issues on the publish as well. Maybe just to add to that, again, you can run it on your production. However, we recommend that you run it on a clone of your production. So production author instance just, you know, in order to avoid any impact on your business critical instances. Thanks. Sorry, by the way, for the background noise. The fire department is near to me, so you can hear this sometimes. Okay, next question. How can we make the existing code of AM65 instance cloud ready for future migration? So, if you put any important to CAM and go through resolutions. Yeah, go ahead. Yeah, I was just gonna say that, again, so this is, as we covered in the session, if you are planning to move to cloud, run BPA, upload that report into CAM, focus on those critical findings. So the severity levels go from critical major advisory and info. So if you’re planning to move to cloud, focus on the critical findings because those are the findings that you must resolve to make sure your code and content is ready to be migrated to cloud service. Thank you. Next question. Can we run this in Mongo author cluster? I think so. Yeah, I don’t think there’ll be any problem running BPA on an author instance that has Mongo. Thanks. And what are most common issues we have seen when migrating customers to AM as a cloud service? That’s a tricky one, because, you know, every, every, at least in our experience, pretty much every customer has a different implementation. So it’s hard to generalize. But, I mean, yeah, so I don’t think if there are, if I know of some common ones, maybe if you’re using legacy wise, so those, those I’ve seen, they’ve come up. I don’t know, Kiran, if you have seen anything else you want to share? So the most common things that we see is the development guidelines ones which are then on premise, when we’re on premise, we have a lot of leverage because infrastructure, even on premise, right? So you have a lot of disk space, a lot of CPU. But when you’re going cloud, there are certain aspects that you have to look at, especially in the developer guidelines section. So for example, if you’re using Igo streams directly streaming into the disk, that’s a big no in the cloud, number one. Number two is, if you’re using Sling jobs, then it’s better to convert them into Sling schedulers, because in the cloud, the other parts could come and go. And also we see a lot of content issues. As I mentioned, like, because, you know, we have the content sitting there for a long time. People have forgotten about a lot of, you know, content that is not working for you, like missing words and renditions. And also we see a lot of nodes that have larger lengths, which causes problems as well. And we see a lot of unused groups and members. So it goes on, as Aditi mentioned, customer to customer, but I have seen more issues in the content as well as in the development guidelines areas that takes up time, apart from users of legacy, you know, user interface.

Thank you, Kieran. Next question. I’m not sure if this got answered previously. Probably did, but if we can run in Mongo author cluster, are there any considerations like running BPA tool only in primary author node, Mongo cluster in brackets? Yeah, I would, I think, I don’t have a, I haven’t had a recent experience running the BPA on the Mongo, but my guess is because it is running on, on a JCR level, because author primary or secondary are going to look at the same as the, you know, the document or store, and they’re all connected to the one blob store. So I don’t think it would make any difference, but something that please try it out. And then if you have any issues, you put us back. Thank you. Okay. So this is my first webinar. How do I find this recording? That’s a great question. So our landing page, which includes the session archive is on Adobe.com slash go slash gems. I will reply to this question in written as well. And also you will find it in the contextual thread from tomorrow on. Both in the landing pages and also in the contextual thread, the recording will not be available until tomorrow. I will also post the link to your question. Then next question. One of my customers who is in upgrade from AM six, the four to six, five state doesn’t have a good development team in house. So Tam asked ACS to run the BPA report for them. The customer doesn’t have enough resource to apply the recommendations and rely on ACS to apply them, which hasn’t happened yet. Do you have any recommendations? I think at this point, I mean, I, I, we don’t have any recommendations, but we can take this and, you know, come back with, with an answer, hopefully.

Yes, we can. That is, that’s more of an account, account team or sales team kind of a question. Right. Yeah, that’s true. Yes. Please contact us. Post session.

And another question regarding the recording. I will post the link shortly. We have one minute left, so practically we can answer one more question. In the meantime, I would again like to ask you to complete the ending poll. This is going to give us some feedback around the session rating, for example, and also what kind of topics you would like to see in future gems webinars. So please fill that out. I have posted the link in the general chat just now. Okay. So, so I’m going to go back to the chat. I’m going to go back to the chat. I have posted the link in the general chat just now.

Okay.

Last question. Are there other tools to run on a current AM as a cloud service instance to find any potential issues? I understand BPA is for AM on prem and migrating to AM as a cloud service. Yeah, I can take that. Yes, you’re right that BPA is for AM on prem or, you know, AMS. And currently we don’t have a similar tool for cloud service. However, you know, cloud manager, when you use cloud manager to deploy your code, I mean, it does give you an assessment of your does do a code check. So that’s there that obviously I’m sure you’re using or will use in the future. And however, we are kind of thinking about building something similar for cloud service as well. Something similar to BPA for cloud service. So that is something that is in our pipeline. However, we don’t have an ETA for when it will be available.

Okay, great. Thank you very much. We’re at the end of the session. Thanks to the team for presenting and demoing and answer all these questions. And to the audience, thanks a lot for your interest and attention. That’s great. Thanks a lot for all your feedback and questions. That’s really great for us. So I wish everyone a great day or evening. Thanks a lot and bye bye. Thank you. Bye. Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.

Bye.