OSGi configurations

Hello everyone my name is Varun Mitra, and welcome to the video. In this particular lesson, we are going to talk about using OSGi Configurations with Adobe Experience Manager as a cloud service.

After completing this training, you will be able to use OSGi Configuration in AEM as a cloud service instance.

Now, let’s just quickly go ahead and see how you can leverage maintenance tasks alongside your OSGi Configurations.

In the previous video, we have talked about the different maintenance tasks that you can schedule and also how you can schedule them. In this particular video, we are going to choose one particular maintenance task and then we are going to configure it. So over here, I’m going to quickly go over to the lifts location. I’m going to actually go over to lifts setting screen night operation maintenance, green night, weekly. And from over here, I’m going to simply copy the workflow push task. And I’m doing this on my local cloud Ready, quick start. Now, I’m going to simply go ahead and place this task into my green Knight daily folder. That is, I’m changing the frequency of this task from weekly to daily. Now, once this starts, it’s moved over here. It would be executed daily at a certain time period. This particular task for this particular maintenance task need to be configured alongside a particular OSGi property, that is Adobe gray night workflow verge configuration. Now, this particular property is available in the web console. And if we were doing this on an on-prem instance we would have simply gone ahead and modified this OSGi Configuration. But since we are doing this on a cloud, ready, quick start. And later on, these configurations need to be deployed. We have cloud manager on as a cloud service instance as such. We need to process this configuration within our apps, right? So in order to do this, what I’m going to do is I’m going to verify the correct configuration name by going to the green Knight dot task. And you can know more about which property you need to modify by directly going in here. So, the property name is Adobe gray Knight workflow fudge configuration. So, this is correct configuration. Now I’m going to quickly grab the persistent ID or or the factory persistent identifier over here. This is the factory configuration. So, this needs to be uphanded with a suitable identifier. Next, I’m going to go to apps and go to my project. This is the training project that I have got and I have got different configurations over here. I’m going to go directly to config.author and I’m going to create a new note over here. The note that I’m going to create will be called simply calm dot Adobe dot gray night dot workflow dot schedule plus a unique identifier. Anything of my choice can be added over here. Something like training, and the type of this note would be Slingerland OSGi config.

And I can add this in over here. Now as a next step I can add all of these different configurations in here. I can give the , simply copy these properties or you can simply look up the documentation for this and add these in over here. And I’m going to provide a name over here something simple like training.

Next, I will also get the workflow status. You can add multiple workflow status over here. You can add complete it dominated. You can verify it using this dropdown.

So, I have this over here and provide the status as completed.

Next, I will simply also get the property that is models to perch. You can add multiple model IDs over here, and you can also specify how many days these particular models have to run.

Now, I will leave this as blank and I will also add the days old property which will allow me to specify how old my models have to be. I will also set the correct value that is long and add 30 over here.

I have a saved this particular configuration. Now with this configuration in place my workflow first task is correct. I added it as a daily task and this particular property would be leveraged in order to execute this particular task. Now, what I need to do is I need to simply go ahead and persist these configurations within my code base. Once again, in order to process my maintenance tasks I keep up on my checkout and this should process my maintenance tasks directly to my code base. Another thing which I can do at this point is I can also perform the same operation within my apps’ directory.

Quickly go back Let me quickly navigate over to my UI dot apps folder and verify if I’m at the correct place. I need to go to src\main\content\ and then content, and then GCI route.

Once I’m in here, I can once again, run my VLT command.

So, what this will do is this will once again go back to my repository and check out the newly created configuration that is sent there. So, this is run for the first time. It is performing a mass checkout, how well my configurations are now processed within my code base. And can we check back into the GitHub and then can be applied to my AEM as a cloud service instance with the help of a cloud manager. So, this is how you can use OSGi configuration in conjunction with your maintenance task. If you just want to define and always check on for creation for some of the custom services you have created you can follow the same approach and you can simply neglect the first step that we perform that is creating a custom maintenance task. So, this is how you can perform maintenance tasks and create custom OSGi configuration. So now you should be able to use OSGi Configuration in AEM as a cloud service. Thank you very much for watching this video and have a great day. -