Learn how you can deploy the Adobe Asset Link panel for your creative users.

Adobe Asset Link streamlines collaboration between creatives and marketers in the content creation process. It connects Adobe Experience Manager Assets (AEM Assets) with Creative Cloud desktop apps Photoshop, Illustrator, and InDesign. The Adobe Asset Link panel allows creatives to access and modify content stored in AEM Assets without leaving the creative apps they are most familiar with. Key capabilities include, but are not limited to:

  • Searching across AEM Assets and Creative Cloud Assets

  • Checking out/in content stored in AEM Assets to prevent duplicate work by team members and to maintain a single source of truth

  • Keeping work-in-progress assets and final production assets in separate locations

  • Enabling new assets to be uploaded to AEM Assets

  • Easily access through Single Sign On (SSO) with Creative Cloud account credentials

Perform the following tasks:

  • Download the assetlink-settings.json file.
  • Configure the assetlink-settings.json file on devices on which Adobe Asset Link will be accessed.
  • Install the Adobe Asset Link panel.

Configure Adobe Asset Link settings file for all devices

Connect your Creative Cloud applications to your AEM server by configuring the assetlink-settings.json file on all the target devices.

  1. Download the sample assetlink-settings.json file, and open it in a text editor.

  2. Modify the file to include the AEM Assets endpoint.

    {"aemServer":"SERVERNAME","aemPort":"SERVERPORT","aemScheme":"PROTOCOL"}

    Existing values To be updated with
    SERVERNAME AEM server name
    SERVERPORT Port on which AEM server is running
    PROTOCOL Protocol scheme of AEM server URL. Either HTTP or HTTPS

    For example,

    If your AEM server URL is: http://content.demo.com:4502, the .json file looks like:

    • {"aemServer":"content.demo.com","aemPort":"4502","aemScheme":"http"}

    Some other json samples:

    • {"aemServer":"author.customer.com","aemPort":"443","aemScheme":"https"}
    • {"aemServer":"localhost","aemPort":"4502","aemScheme":"http"}
    • {"aemServer":"author-nossl.customer.com","aemPort":"80","aemScheme":"http"}

    Note:

    The feature currently supports accessing one AEM Assets instance at a time. To access a different instance, change the AEM Assets endpoint within the .json file. For remote deployment, ensure that the script can create directories and set permissions, if not present.

  3. Copy the assetlink-settings.json file to the below location on the devices of all applicable users:

    • macOS: /users/<username>/Library/Application Support/Adobe/CEP/extensions/
    • Windows: C:\Users\<username>\AppData\Roaming\Adobe\CEP\extensions

    Note:

    If the folder path is not available on a device, create the CEP > extensions folder manually.

    Note:

    If an administrator is setting up a machine before a user is created on it, copy the assetlink-setting.json file in the common location /Library/Application Support/Adobe/CEP/extensions/ (Mac) or \Program Files\Common Files\Adobe\CEP\extensions (Windows). The Adobe Asset Link panel should copy the file to the user area automatically. In this scenario, the administrator should ensure that users have read permissions to the folder that contains the assetlink-settings.json file. The administrator should also ensure that all future users of the deployed machine have read access to the folder that contains the assetlink-settings.json file.

Install the Adobe Asset Link panel

 You can perform this task if you have any of the following roles assigned in the Adobe Admin Console.

  • System administrator
  • Deployment administrator

To install the Adobe Asset Link panel, include it when you build a package for deployment. Both self-serve and managed packages are supported.

When the deployment package is built in the Adobe Admin Console, enable the Include Adobe Asset Link option in the Package configuration options. For more information, see Create Named User packages.

Include Adobe Asset Link

This process makes it easier by allowing you to bundle extensions into the deployment package you create using the Adobe Admin Console. This way, the installation of Creative Cloud applications and extensions happens as part of or as a single deployment process.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy