Set up App Builder

Asset Compute projects are specially defined App Builder projects, and as such, require access to App Builder in the Adobe Developer Console in order to set up and deploy them.

Create and set up App Builder in Adobe Developer Console

Click-through of setting upApp Builder (No audio)

1. Log in to Adobe Developer Console using the Adobe ID associated with the provisioned accounts and services. Ensure you are a System Administrator or in the Developer Role for the correct Adobe Org.

2. Create a App Builder project by tapping Create new project > Project from template > App Builder

   If either Create new project button or the App Builder type is not available, this means your Adobe Org is not provisioned with App Builder.

   • Project title: WKND AEM Asset Compute
   • App name: wkndAemAssetCompute<YourName>
     • The App name must be unique across all FApp Builderirefly projects and is not modifiable later. Prefixing the your company or organization’s name, and postfixing with a meaningful suffix is a good approach, such as: wkndAemAssetCompute.
     • For self-enablement it is often best to postfix your name to the App name, such as wkndAemAssetComputeJaneDoe to avoid collisions with other App Builder projects.
   • Under Workspaces add a new environment named Development
   • Under Adobe I/O Runtime ensure Include Runtime with each workspace is selected
   • Tap Save to save the project

3. In the App Builder project, select Development from the workspace selector

4. Tap + Add Service > API to open the Add an API wizard, use this approach to add the following APIs:

   • Experience Cloud > Asset Compute
     • Select Generate a key pair and tap the Generate keypair button, and save the downloaded config.zip to a safe location for later use
     • Tap Next
     • Select the Product profile Integrations - Cloud Service and tap Save configured API
   • Adobe Services > I/O Events and tap Save configured API
   • Adobe Services > I/O Management API and tap Save configured API

Access the private.key

When setting up the Asset Compute API integration a new key pair was generated and a config.zip file was automatically downloaded. This config.zip contains the generated public certificate and matching private.key file.

1. Unzip config.zip to a safe place on your file system as the private.key is used later
   • Secrets and private keys should never be added to Git as a matter of security.

Review the Service Account (JWT) Credentials

This Adobe I/O project’s credentials are used by the local Asset Compute Development Tool to interact with Adobe I/O Runtime, and will need to be incorporated into the Asset Compute project. Familiarize yourself with the Service Account (JWT) credentials.

1. From the Adobe I/O Project App Builder project, ensure the Development workspace is selected
2. Tap on Service Account (JWT) under Credentials
3. Review the Adobe I/O Credentials displayed
   • The public key listed at the bottom has it’s private.key counterpart in the config.zip downloaded when the Asset Compute API was added to this project.
     • If the private key is lost or compromised, the matching public key can be removed, and a new key pair generated in or uploaded to Adobe I/O using this interface.

Business.Adobe.com resources