Setup a developer environment create-dev-environment

To create a setup that allows you to develop for Asset Compute Service, follow these requirements and instructions.

  1. Acquire access and credentials for Adobe Developer App Builder.

  2. Set up the local environment and the required tools.

  3. Some more tools that help you get started developing smoothly are:

    • Git
    • Docker Desktop
    • NodeJS (v14 LTS, odd versions are not recommended) and NPM. User of OS X HomeBrew can do brew install node to install both. Otherwise, download it from the NodeJS download page
    • An IDE that is good for NodeJS, Adobe recommends Visual Studio Code (VS Code) as it is the supported IDE for the debugger. You can use any other IDE as a code editor, but advanced usage (for example, debugger) is not yet supported
    • Install the latest Adobe aio-cli (aio)
  4. Make sure to meet the prerequisites

Set up an App Builder project create-App-Builder-project

  1. Ensure that there is a system administrator or developer role in the Experience Cloud organization. A system admin, in the Admin Console, sets up this role.

  2. Log onto the Adobe Developer Console. Ensure you are part of the same Experience Cloud organization as the Experience Manager as a Cloud Service integration. For more information about Adobe Developer Console, go to Console documentation.

  3. Create an App Builder project. Click Create new project > Project from template. Select App Builder. It creates a new App Builder Project with two workspaces: Production and Stage. Add additional workspaces, for example Development, as required.

  4. In the App Builder Project, select a workspace and subscribe to the services needed for Asset Compute. Click Add to Project > API and add Asset Compute, IO Events, and IO Events Management services. When adding the first API, it prompts to create a private key. Save this information on your machine as you need this key to test your custom application with the developer tool.

    note note
    NOTE
    JWT is deprecated and Private Key is not available for download. While we are working on updating the testing tools, note that custom workers created using OAuth can be deployed but devtools would not work.

Next step next-step

With your environment set up, you are ready to create a custom application.

recommendation-more-help
b027be24-3772-44c0-a56d-a4ba23dcb50b