Adobe I/O Runtime Action and AEM Events

Transcript

Let’s explore how to receive AM events using Adobe IO runtime actions. Adobe IO Runtime, a serverless computing platform, facilitates code execution in response to Adobe IO events. The high-level steps are create project in Adobe Developer Console using the App Builder template, initialize project for local development, configure project in Adobe Developer Console, and finally trigger and verify the AM event. Let’s get started. To create a project, first navigate to developer.adobe.com and click on the console button. Then click Create Project from Template button and select App Builder option. In the setup model, update the project title, add a workspace if needed, and save your changes. Next, we need to initialize this project for local development. To do that, we need Adobe IO Command Line Interface or AIO CLI for short. Make sure it’s installed locally. In the terminal window, run AIO app init, then select the correct org and newly created project. For the templates prompt, select all templates, and from options, select Extensibility template generator AIO app. Once project initialization is complete, open the project in your favorite editor. The selected template provides a generic runtime action. We will be using it to receive AM events. But before that, let’s make a few code changes to keep it bare minimum. Also, initialize this project as a git repository and perform initial commit. Next, let’s deploy the project on Adobe IO runtime using AIO app deploy command. This will make the generic action available for receiving AM events. So, let’s head back to the developer console project and select stage workspace wherein we deployed the code. As you can see, we have generic action available. Next, let’s add IOManagement API and AM sites to this workspace. Click the Add service button, then select API, then IOManagement API from Adobe services, and choose OAuth server to server as the authentication type. Save config changes. Likewise, add event, then select AM sites from experience cloud and click next. In the Configure event registration dialog, select the AM environments from which you won’t receive events. In the next step, choose specific event types. Select OAuth server to server auth type and provide a valid name for this event registration. Note that within a single project, you can have multiple event registration, receiving events from different AM environments and of different event types. A good naming convention is critical. Finally, for how to receive events, expand the runtime action option and select the generic action from the dropdown. Save your configurations. The event registration details page provides a summary of the AM site’s event registration. Let’s open the Debug tracing tab. You should see the challenge probe request and response. This is done to validate the action. It’s time to verify and receive an AM event. Let’s update a content fragment in the AM author environment and verify the received event details. The request header and payload object contains various details like where, when, who and what. Using this data, Adobe IO runtime action can perform tasks to develop a content ecosystem. In the next example, we will enhance this action to process AM events, call back AM author service to get content details, store details in Adobe IO storage and display them in a single page application. In summary, now you know how to use Adobe IO runtime action to receive AM events.