Why AEM is More Powerful in the Cloud

Transcript

Hello, everyone, and welcome to Espressos and Experience Manager. I’m your host today, Alana Cullen, and I’m joined by Rajan Kumar and Casey Witter. And they are going to take us through a presentation on why Am is more powerful in the cloud. So I’m going to go ahead and get us started because we’ve got a lot to get to today. So.

Let’s go again. So again, welcome to espresso. As an experienced manager. Today’s agenda, we are going to say our hellos as we just did. And then Rajan and Casey are going to take us through today’s presentation. We are going to pause for a live demo from Rajan in the product, and then we’re going to conclude with Q&A. So let’s go ahead and get started. I’m going to pass it off to Casey.

Thanks so much Alana. So what let’s talk about investing in cloud service. When we think about upgrading to cloud service this is really an investment in innovating your content. Meaning that long deployments and version upgrades are no longer a focus, so that your creative teams have more time to focus on content, and your technical teams can attack your technical roadmap. So first, when we’re just going through thinking about if you want to upgrade. Think about these questions and examine them with your team. Are there any efficiencies your current deployment plan? We make sure deployment plans and cloud service are really tight and ready to go.

What is your current technical roadmap? Maybe an upgrade fit in there? Are you looking to upgrade in general? If so, maybe we would look at cloud service as well as a part of that other upgrade. Are there resources in place to begin? Meaning, is your team stacked and ready to go and is your current instance and mature, meaning that maybe it’s time to upgrade just in general.

So I want to briefly talk about the benefit of being on cloud service, and the first of those being the Performance Cloud service customers have a 400% improvement in page load time, and this is due to the architecture, the asset processing and ingestion process, and your instance staying current and no longer needing to continuously upgrade the system. So we manage this even. We have global data centers and additional published regions that handle all of those aspects of the system. We also have a secure architecture and options to leverage edge delivery service and cloud service.

The next benefit would be the access to our latest content innovations. And this is what really gets me excited, as cloud service is the latest and greatest aspect of and new and features are rolled out with a focus on the cloud service instances. These features include quick site creation. We’ve seen customers create web pages 144 times faster and cloud service. Also includes features like Adobe, Jet and Studio, which basically means being able to leverage the Adobe Cloud for all touch points throughout your entire content lifecycle.

Are innovations like auditing your content quality, easier analytics integrations, custom tagging, and searching, and using our Universal Editor. You can also leverage our enhanced security, and I’m sure you’ll all be happy to hear that cloud service is in compliance with HIPAA.

Again, with edge delivery services, you can enable document based authoring, which is a huge focus in the CMS industry right now.

You also may hear a lot about these features at Adobe Summit in a couple of weeks, but feel free to reach out to your Success Account Manager for any other questions about some of these innovations specific to cloud service.

Finally, the last benefit I want to emphasize is being able to rapidly deliver experiences. We’ve found that that cloud service customers have a two times faster time to market as non cloud service customers. This is due to an automated CI CD. Improved options for headless rapid development environments, flexible deployments and more containers to dynamically scale. Cloud service has web app firewalls that include penetration testing, and I’m sure many of you would be happy to hear about the highly frequent backup and recovery compatibility and options to restore content.

So say you do want to upgrade to cloud. Let’s talk about where to begin. We want to emphasize that we want you to take a crawl walk run approach. First we will leverage our free tools to all and customers that you all should have access to these. It’s called the Best Practices Analyzer Report. I’ll refer to that as the API and the Cloud Acceleration Manager tool, which we refer to as the Cam tool. Which these tools assess your current and instance to see how compatible it would be to an upgrade to cloud. And later on we’ll be demoing to us just exactly how to use these tools. But based on the output of these reports, you can begin the walk phase, which would be preparing your current instance into adhering to these best practices. For example, if you have many custom aspects that may break during the upgrade, begin to refactor them to adhere to the best practices so that your system will have a smoother migration.

Once your team has prepared your existing Am instance to be ready for cloud service, you are ready to run, which would be to engage an implementation team and begin the upgrade.

So this is a high level overview of Adobe’s recommended methodology to move to cloud. We break it down into five phases readiness planning and set up implementation, go live and optimization for this part of the presentation. We want to focus on the readiness phase, which include the assessment of and best practices, which ones are being followed, etc. and a high level migration complexity assessment.

Breaking down this phase further. This looks like three steps. First is installing and executing the tool and downloading the report. Now this looks like a CSV which can be difficult to interpret. So that’s why we made the cam tool to put it into, which is an easier format to read.

Logging into the admin console to view the Cloud Acceleration Manager. This screen should be accessible to all and customers, and once you can get into the screen, you’ll upload your BVA report into the cam tool to review your assessment. So now I’ll hand this off to Rajan to demo this process.

What I think you might be muted at this time. I was just going to say. So thank you Cassie. So. And, walk through with the all the exciting and new features, in a major cloud services and, covering at very high level of, how the migration approach looks like. So, so now you must be thinking from where to a start, right? Now you are on aims or either on, on prem, and you wanted to live with these cool features, and you really want to, like, migrate on image cloud service. So starting point, it would be, looking into the best practice analyzer. So what does this tool do. Right. So this tool will help you to determine your current status of your implementations, how complex you are, with the current system. And, it gonna identify all the, variations and, violations currently, which can stop you for the migration journey. So how you can use this tool to this tool can be downloaded from the Software Distributions tool, which I will be showcasing on the demo, how you can download it. And this tool can be accessible from the tool and then operations. And then you will see the card based practice analyzer. One interesting thing to know about this tool can be only run by the administrator or a user who are a part of the admin group. And then this tool can be run, especially we recommend, if you are on higher versions of the 6.1, then, this tool is compatible. And what we recommend, this tool to run on, specially on the replica of her products sklearn instance where you have all the content as like a productions or you may run it on the stage where you have a similar content. So which will give you the right set of the data. And this report is going to give you the, different types or different levels of the violations, which will have a info advisory measure and, critical. So I will be, talking about in this, all violations in more details in the, while the demo.

So moving on to the next, cloud access lessons manager. So, cloud resource manager, basically is a cloud based applications designed to guide your IT team throughout the transition journey, starting from the planning to going live on the cloud services. So what is actually it mean, like, so you can assume, like a, cam is a one stop experience for Mac migrations, which come in the form of guided Journey by providing the initial assessment, pointing to the right direction. What are the best practices? So you can have a, better idea, what are the violations in the content side and then court side? Then it will guide you through the all the, best practices. It will also talk about that very high level of the estimations, like, how complex your journey, is going to look like. And then based upon that, you can just plan. So, we will showcase this all, reports how it’s going to look into the demo. So let’s, quickly move on to the, demo part.

So if you can just, bear with me, I’m going to just share my screen.

Loading. One moment. You.

All right. I hope my screens are visible. So, All right, so, starting with the how you can just download, VBA tool. So first, what do you want to do it? You want to go on, software distributions. Click on the Image Cloud Service tab. And then if you scroll down you will see Best Practice Analyzer. And you always have to make sure you are downloading the latest versions. You might see, older versions as well. It’s always recommended to have latest versions which will have all the rules incorporated with the latest. So how you can download, download this tool. Right. So you can just click on the link. You have to accept that and then click on the download. It will download the package. And once you download the package and it’s completed, the next step, what are you going to do. You gonna go on your app instance either on the clone or the stage where you’re going to run it. You will navigate to the, package manager and then, you will to just upload a package which you downloaded it by clicking on the upload package option and then browse the downloaded. So, you can just plot and then select and click on the okay button. And then it will just upload it since I have already uploaded. So you can see over there this is already present. You can just click on the install button, since it has me already installed. So for me it’s showing the install. But for you, if you’re installing the first time, it will so installed. So you can just click on the install. Once you install this tool you want wanted to make sure whether it got successfully install or not. So how you can confirm again you go back to the your m sites m welcome page and then click on the hammer tool. Navigate to the operation. You can see the one card with the best practice manager. So what are you going to do. You just going to click on the best practice analyzer over there. Once you click on this link, you will see report if you have already done it, since I have already uploaded the report, you can see all the details. If not, what do you want to see? Over here.

If you click on that generate report, it will just, generate the report and it will just count, it will show the progress, how the report is going to, look like. And then, it will show you the data. So once it is completed and then, you can see the report. And the good thing about, BP running the BP report can take significant amount of the time from several minutes to a few hours. So, amount of the time required is highly depend on size and nature of the repository content and what a convergence. And there are many other factor as well. So because of the significant time it’s going to take, the way of tool, this has been designed in a way, even though if you close this project browser, the job will run in the background. And once the reports are that it is being cached. So next time on what? Whenever you have to download an, report, you can just come to the, VPN analyzer tool and it will just say, okay. So if you see, on the report, right. So you you might have seen the first time when I open it was already showing the reports. It just pulled the data from the cache. So coming to the report sections, if you see over here, we have a, report time when it is going to expire. What are the findings? And then the virgins on what was once you have run it and cool thing is about this report is going to categorized into the all the segment. Or you can see all the different area like a missing data are contained. If they had any content area violations, whether you have a custom, classic dialog widget or whether you have a static template, it is going to, look into all the areas where, wherever it is, just, guide you to you have to improve these violations before you go for the migrations. And it will also categorize into the different, variations like info, which is like a just provide the additional information and then advise you it is just, you need to further investigate, for this one then, major, this is likely to be an upgrade issue and should be addressed then critical it is mandatory to address those issues before you plan for the migration. So this will give you the high level of the data and, the all the details, how it is going to look like with the, details. If you want to see the, how your ATM system will look like. So it will give you the all the details over there, then, once you are, got a better idea about this report? What you going to do? You can just, click on export CSV. So if you click on CSV, report is going to be downloaded. And the same report you will be using for that analyzing with the cam tool. So how you can navigate to the cam right. So for that what you’re going to do you’re going to open experience.adobe.com. And then click on the Experience Manager. Make sure you all you are on the right org. If you are a part of the multiple org, then you want to click on the, launch of the Cloud Experience Manager. So once you click on, it’s going to populate, this landing page. So initially if you see you might see there is nothing since I have already created a few of the projects. So just to create a project, you’re going to click on the create project and just give the, name. And then you have to click on the create. So once you create project, if you go inside that, you will see the different cards and it segregate into the multi, different three sections I would say. So first is the readiness which talk about how you, how is your, current implementation is going to look like in terms of the, your migration journey. Then you will have implementation, then implementation stacking where you will be first doing the local setup, refactoring the code based upon the report, and then, plan for the deployment, then last in with the content migrations with the content transfer. So and then the last section is go lab. So this interface with the help of that, you’re going to just track all your progress for the migration journey. And now, how are you going to analyze, all reports which you downloaded from the BPO. So you have to go inside the best practice analyzer, click on the review, and, you will be uploading this report by clicking on clicking on the upload. And then select the report what you downloaded. So it’s going to take a couple of a minute, based upon the report. And then it’s going to analyze, and it will give you the data. So I do have already, loaded this report for the different projects. So let me open that if I go to the, review section. So. Yeah. So once the report is completely loaded, it’s going to look like this, view. So you will have a report property. Report property. We will have a informations about, when the report was generated and, when it was uploaded and what was what was the project and then most then, report overview will provide you the data. What are the critical measures and advisor info level, details and total findings. Then best practice assessment will have a, data, what you are looking for probably, total number of the component. How many are the core component? How many are in it from the on foundations. How many are the custom component. And then what how many are the, editable, static template. So this data will help you to determine, effort, how long it’s going to optimize towards. And then the last sections we will talk about, complexity, whether it’s low, medium, high based upon your report. And it will, give you that idea. Okay. This migration journey have a lot of violations and it is going to impact. So you have a amount of effort is going to be high.

Then coming to the this section report, they said that, also the report will be segregated into the different segments with the categories. So you can see over here all index commerce indications, if you have the non compatible changes legacy user interface. So these are the different segmented. You have to make sure focus on focus on the critical issues. And it will it will showcase all the cons as well. Just to further get the more details you want to click on this, icon, it will just provide you the all the list. What exactly the issues are. And then you can just analyze this and then coming to the next tab best practice assessment, which will have information about Am instance overview where it was run. And then it will have a detailed information with the custom component and the template which will give provide you the data, which will help you to determine, amount of the effort for the these optimizations. Or you can just, fixing those violations then, it will also have the additional finding with the legacy UI or content idea violations since, legacy UI will be not supported with the cloud service. So you have to make sure you fix these items. Before you plan for the migrations and then again for the content area violations as well. You will not just fix those, violations then coming down to the, more, it is gonna provide you all to us all the slow query informations, basically. So you will have to look forward for the optimizations if it is, really slow and then look for the indexing, optimization. So you have it all sort of the data with this tool and then last with the maintenance task, few of the, maintenance activity in a major cloud is internally managed, and few of them are, managed by the customer. So with the this report, you will have a data. How exactly? We, your maintenance task. It is. And, for the image cloud, you have to ensure all the customer manage, maintenance that should be captured into the, code base you have to put into the code repo. So in a nutshell, if you see about this, report, you will have it all high level of the informations and, to, help you with the migration journey and determine the effort. And then you can plan accordingly. Yep. That’s it. About the demo. We will go back to the slide now and then cover a few of the more points.

Sure thing. Like that. Cool. Thanks again. So yeah. Moving on. To the, notable changes in the image cloud service. So I think is a very important video coming from the image or see image as image and on prem, instance, you must know about, changes stunning image of cloud services. So starting with the asset processing. So the way of, handling, asset mechanisms when you upload an asset. Right. So, it is leveraging the asset either, I would say, and in some time for the, when you go inject ingesting a lot of asset, it take longer time and it engage JVM of other which impact the performance. So in a image cloud service, this has been, outsourced to the, Adobe IO pipeline, which internally used the asset compute services. So which is quite, helpful in case of if you are, ingesting a lot of asset it still, it will not impact the performance. You can easily, upload all the asset then, mutable and immutable. So, in an image cloud service, is kind of, rule has been segregated where you can make the code changes and what part you are not supposed to do. So it’s being a restrict a strictly follow. So inside the live you are not supposed to change anything. And you have to make sure, only make the changes only at the right places and not all the wherever you have the read access, then, run mode. So with the image or on prem, you must have a lot of environment and you might have a custom van mode. You have to ensure those run mode will be not supported. So run mode, in a image cloud service is going to support other published development stage and productions. And then last newly added updates. So you have to ensure beforehand, if you have any custom make sure you just update those remote configuration.

Then moving on to the deployment process. So deployment process overall is going to look like all this will be handled by Cloud Manager and by CD pipeline. There is no manual deployment going to the NXT and uploading the bundle or the package. Everything always go that go with ci CD. It does have a, different level of the, pipeline. So you will have a product non prod with the only you can deploy the configurations, only you can deploy the fronting code. Only you can deploy the CL dispatcher changes. So kind of we do have a different sort of the pipelines which you can leverage it then OCI configurations. All the OCI configurations must be part of the, your source code for any changes. It has to go via that deployment process. There is no flexibility to go to the directly on the system console and then update the configurations. So make sure you adapt with the all the process if you have any configurations, which is directly applied on the instance, you have to put into the code base repo, then, as I said, like, for the classic, UI support is not, possible in, which has been removed from the cloud, services. So make sure if any component or any widgets you are leveraging with the image, you have to get rid of that fixed code. You can you have to migrate from classic to that, that UI. And then you should be good for the migration. Then last session fastly. So, with the architecture of the image cloud services, it comes, as a Adobe managed, client, which is internally a fastly. And, so with the help of this one, you can leverage the all the client features.

Will move on to the next. So this is a very important, I would say, tool to understand what are the different tools, what Adobe does provide, which can help you with the migration journey. So we do have a first starting with the code repository Mac Modernizer. So this tool is going to help you with, if you have a folder structure in different act which is not competitive with the image cloud services. So to make that changes, this tool is going to help you restructure and ensure all the immutable, immutable structures is being followed. So you can run this tool either the Adobe IO command line tool or the Node.js you can leverage is then, a modernized tool come with the suits with the different setup, the utility, which can help you to, migration journey. Like if you have a static template, you have to migrate to that editable template. So this tool gonna help you with that. Since you have a static number, you probably have a design level configuration. And all those design level configuration has to be migrated into the policy. And most of the foundations component has to be migrated into the core components. So these are all things violations you will see in the report. And then you’re gonna leverage this tool, to, mitigate those violations and, leverage this tool, full fledged with, also migrating from classic to touch UI. Then next tool you can leverage, asset workflow migration. So the way, workflow, processing mechanisms has been, different in image cloud services. So you can leverage this tool to migrate those all configurations and update those configurations, which will be compatible with the, cloud services.

Another tool I am a dispatcher, which I would say very important because, this structure of the IAM, despite respect, there has been little change. So if your dispatcher configuration is not compatible with the cloud, you’re gonna leverage this tool to move all those configurations, restructure and then add all your custom tools, whatever you will have it. So this tool is gonna help you. And then last but not the least, content transfer tool, which talk about, basically migrating your all the content to the image cloud service. So once you are ready with the migration journey code your code red ready and everything you have deployed to the Your Image cloud service. And the last step is going to be, migrate your all content. So this tool is going to help you with migrating all your page or all the assets.

So that’s about the tool part. This tool, we will be very helpful to, migration journey. And I’ll be covering at very high level of, AMM, cloud service architecture, which is just you can see at the top we have a client services which is internally fastly. And then you have a different layer styles like a publisher tire preview tire and then author, tires and the left certificate for the replication services. So all the replication thing happening using the sync distributions, which is the internally the pipeline then ci CD services, which is basically used for the all the deployment. So we do have a cloud manager which leverages the deployment process. Then watch services, you can leverage the web services for any DOS attack, which has been recently introduced, where you have the flexibility to optimize the rules based upon your, use cases. And you can just deploy those code changes, by the cloud manager.

And then lastly, you can see identity management service. So all the users and groups be will be managed in the admin console. And that will get sync into the A. And once the user logging. So and the recommended approach is to manage all the users and group into the admin console. On the right side you can see Asset Compute Service, which I was talking about. For them, handling the asset processing, which has been outsourced to the Adobe IO runtime. So this is a service asset compute service will be taking care of the processing of the, assets. And then the will send back to the, a model instance. Then we do have a testing service. So you can leverage the testing service as well to hybrid, testing, in place automations in the place. So this is all, at very high level of the, architecture of the image cloud service with that, I will pass it to the Casey to talk about, all the methodology and how you can just migrate.

Thanks so much, Rajat and Nikki, for that demo. So now that we have a good grasp on the readiness phase, I want to quickly outline the subsequent phases. Like any implementation project, we will also want to emphasize the use of a partner during this time. It is vital to success. So during planning and setup, this is where we will we will be provisioning Am as a cloud service and reviewing a detailed migration assessment and the project plan for the upgrade.

Then we’ll have implementation. The code and project structure will be prepared for cloud service. You’ll move any existing content and skills into cloud service, and you will enable IMS or SSL for author environments.

During Go Live, there will be code and content freezes. You will have performance and security tests. And finally cut over to cloud service. And then, like any software development lifecycle, there will always be an optimization phase to continue to modernize your code and content.

So a huge emphasis on any implementation project also is just the understanding of the effort that your internal teams will need to prepare to commit to. So we’ve listed out three workstreams that need to be run in parallel to ensure a smooth migration. The first workstream is for content migration that will be using the content transfer tool like Ross on just displayed running the initial migration. Looking into easy copy and pre copy, identifying any type of migrations that need to be addressed for the final goals. The second workstream is the code migration which will handle the project structure. Configuring the cloud, manage your pipelines, refactoring the dispatcher configurations, and doing any iterative deployment necessary to make sure everything’s up to date between the two instances. And finally, do not overlook the operational Workstream which will QA the environment, review the security and performance testing, and this will also include user acceptance testing. Just again, to make sure everything has been properly tested and it’s ready to go. And of course you will work hand-in-hand with a partner during this time.

So I want to show just an example of a very high level timeline of what it could look like to to upgrade to cloud. Of course, this timeline is extremely dependent on your team’s availability, how much a partner will be involved, and the complexity of your BPA results. But for example, during that crawl phase that I spoke about earlier is where you will run and analyze the BPA report. This will help you define your migration approach and roadmap. And maybe that whole all those conversations. Last one quarter next during the walk phase is where you will review the critical findings of the report. You have to clean up your content and code and begin to plan and set off the migration. So your instance is now prepared for that. Again, we scoped the quarter for this effort, but it could take many more if there’s a ton of customization. Really just depends. And then finally during the run phase is where we will be implementing cloud service code and structure is being prepared and the content is being moved to cloud. And so that after testing and kind of write your team that live on cloud. And of course we include optimization for broke ECS because we’re constantly innovating and working on these environments.

So what next? Some key takeaways I want to emphasize and just think about your immediate next steps after this call would first be preparing for cloud by leveraging a and best practices. Even if we’re not going back and refactoring our old code or old content, any that new content should try to adhere to those. Even just to make sure everything’s up to date in your day to day.

Next would be understanding the level of effort to move to cloud again with the tools that we discussed today, taking that level of effort. Thirdly, into your roadmap, and making sure you’re using the recommended methodology that we discussed, to treat this upgraded migration as an implementation project. And lastly, begin to scale and optimize until you are ready to migrate. So I know we just a lot of information that you may think now is time for some Q and A.

That it is. Casey, thank you both for an awesome, awesome presentation and demo. We did get a bunch of questions, so I am going to jump right in. Are you guys ready? Yeah, I believe you’re both off mute. Perfect. Okay, so first question actually came from Melissa is ATM managed service also am asset essentials.

I can dig this one. So am, managed services basically. Yeah, I am, six start virgins which is manage on the cloud and am asset essential is. Yeah. Another product or Stu and you can say that, where it will be used as a lightweight of, asset management, tool, kind of we do have asset, which is a free enterprise, Tam, but, with, with the ATM asset, essentially, you can just, leverage these features with the managing asset during the assets searching features almost. It is going to be same. But with the last couple of the less features, this use case will be applicable. Who are going to leverage, asset management tool as a lightweight. They can go with, a m asset essentially.

All right. Thank you. All right. Next questions from Mark. Are there any differences in uploading a bundle class package, the cloud instance from how it works in on prem. Yeah I can take this also. So I just said right. So all the deployment process in Amazon Cloud service is going to take care with the CD pipeline to the way of the legacy way you are following in, on Prem Amis manually uploading, package via the package manager or uploading directly bundle to the system console, those things would be not possible. We do have a different, different pipelines, which you can leverage it like, only deploying the code, only deploying the configuration. So based upon the your need, you can just leverage, all the required pipelines, but yeah, flexible what you had with the on prem, all AMS would be suited to ensure, you are just following the standard with the using the ci CD.

Right. And another one from Mark you mentioned, what services can we utilize our own or have to use Adobe services.

Yeah, I can take this also again. So yeah, I said web service you can utilize from the Adobe sites as well, although there is a possibility you can go with your own. And so, but most of the use cases, what we have seen, Adobe CD and works on top of that web services. But if, you have any custom requirement which is not getting fulfilled with the web services, what Adobe does provide, you always can go ahead with, your own CDM. And for that, you have to, with the Adobe support ticket to get the key to configure Adobe my to configure customer ID. And then on top of that you can just have a web service. So I would recommend evaluating both the possible way and determine what is going to be cheaper or what is the best way to go forward. So yeah.

Great. Thank you. Okay. Next one, what would be stability of a cloud service.

I can take this one. So of course Adobe has many products on the cloud. And we leverage the cloud native performance excellence that I touched on briefly at the beginning of the presentation. But we have backups and recovery processes, National publish regions. We manage the CBN, we have global data centers, etc., etc. we do all all of our I’s and cross all of our T’s to make sure that the cloud is extremely stable. Great. Thank you. Okay. Next question. How does APM handle content authoring and publishing workflows? Yeah, I can exist. And so, by interface and the user behavior, it is not going to be a change. You will be leveraging the same features but internal mechanisms and they of earlier working the replications. So they were using the replication service which has been get rid of with the same distribution. So technically it has been changed to improved and make it the faster process. But yeah, in overall in terms of the user, perspective, is going to be still remains the same.

Great. Thank you. Okay. Another question. I think for you, Rajan, challenges of moving to an extremely, I’m sorry, what are challenges of moving an extremely large repository to cloud? Yeah, that’s a good question. I have seen a lot of, customers asking having a, large project. So, as we know, that largely depend upon, multiple factors, like having large content or large assets. We do have asset magazines process in the place in, content migrations. We do have, content migration tool available in that list. But again, copying many blob with the content, transfer tool take multiple days as well. So in terms of to speed up the process, you can leverage a G copy, as optional, which is the previous step which will, help to just foster the process. And this can be used. And moreover, we do have a dedicated team, Professional Services, who has helped a lot of customers with the large repository migrations. If feel free to reach out to the, you, Sam, they can get you to the right team. They can help you with, how you can just go further with the larger migrations process.

Great. Thank you. We’ve got time for a couple more here.

What will no longer work in a cloud that’s currently work that currently works in six five? I can take that a lot of, so I want to emphasize that you’re not losing any functionality of an between six, five and cloud. Everything will be the same in any work. That anything that may no longer work would be identified during the migration process that you can, refactor it during that time. But in terms of what will no longer be necessary, like we mentioned, you no longer have to manage server stack update, and you’ll have access to the all new features that you are on cloud. So again, no, not losing anything, just gaining more functionality with this migration.

Great. All right. I think we’ve got time for one more and we have this question and registration. But I also so I think Harish asks something very similar. So what’s the future plan of Adobe for Am on prem customers? Is moving to cloud the only answer are you going to continue to support, the on prem solution? So we can’t speak to a timeline, but I know that there is no current plans to sunset on prem. I think what we could predict is that will continue to get less support from Adobe. And like we’ve mentioned, all the new functionality is being rolled out on cloud service. So start to just think about where that looks like in your timeline. But, as of now, I don’t think we can speak to or have any ideas into if on Prem would be going away.

Great. Well, thank you for the insight. And that’s actually all the time that we have today. So I do want to thank Casey and Raj on for the awesome presentation and demonstration that they took us for today. Very helpful stuff. Don’t forget to grab the white paper on your way out. It’s got a bunch of resources, and we will follow up with many of those resources in our email tomorrow with the recording of today’s webinar. So thank you everyone for joining. Thank you, Casey and Raj on. We hope you all have a great day and we hope to see you at one of our future events. So thanks everyone. Have a good one. Thanks everyone.