Adobe Experience Manager Desktop App lets you map the AEM Assets repository to a network directory so assets within AEM are available at your local system.
Depending upon the operating system, you can view and browse assets in AEM from Mac OS X Finder/Windows Explorer. In addition, you can quickly switch between Finder/Explorer and AEM Assets using convenient links.
You can create, edit, or delete files from Finder/Explorer. The changes are automatically synchronized with AEM Assets and vice-versa. In other words, any changes that you make to the assets from Finder/Explorer are reflected in AEM Assets. Similarly, any changes you make within AEM Assets are visible from Finder/Explorer.
Adobe Experience Manager Desktop App is a new name for AEM Assets Companion App, introduced in AEM 6.1 release.
To use AEM Desktop App, ensure that your AEM server version is supported by AEM Desktop App, download the appropriate installation file (binary) for your operating system (Mac or Windows) from AEM Assets and install the app.
On Windows, the default Windows 7 setting prevents AEM Desktop App from handling assets that are larger than 50MB.
Adobe recommends that you use an HTTPS connection to connect to the author node to ensure that you securely transfer assets to/from AEM. Moreover, intermediate firewalls, proxies, and load balancers don't support WebDAV well and interfere with the AEM Desktop App. Using SSL ensures that the traffic reaches the AEM author unmodified.
The version of AEM Destkop App you are planning to install on your local machine might require a specific AEM server version/additional server-side components (service packs, hot fixes or feature packs). Ensure that the AEM server is properly configured before you connect to it for the first time. If you require help, contact your AEM administrator.
Prerequisites for AEM 6.3
AEM Desktop App is compatible with AEM 6.3. No additional AEM packages are required.
Prerequisites for AEM 6.2
AEM Desktop App 1.3 is compatible with AEM 6.2.
Install the following packages on AEM 6.2:
As of now, AEM Desktop App is tested to be compatible with Mac OS X 10.10 or later, with latest bug fixes.
In the Adobe Marketing Cloud Sign-in page, specify the user name and password for your instance to sign in to Marketing Cloud.
If you have configured Proxy Server settings for MAC OS (System Preferences > Network), AEM Desktop App will go through the preconfigured proxy server when attempting to connect to the AEM instance that you specify.
AEM Desktop App lets you check out files to prevent other users from modifying files you’re working on.
The local path to the assets mounted with Desktop App 1.3 is different than the local path mounted with Desktop App 1.2. For example, when you open the More File Info dialog on the same AEM asset, the following server locations are displayed:
- Desktop App 1.3: smb://localhost/DAM/geometrixx-outdoors/logo.png
- Desktop App 1.2: http://localhost/content/dam//geometrixx-outdoors/logo.png
This change may impact assets that have other assets placed through the Place Link command (in Illustrator, Photoshop, InDesign). You may have to relink assets in the Adobe Creative Cloud applications. Alternatively, mount AEM as a WebDAV drive (works even without the Destkop App), and use it along the new Desktop App mounting point before all assets are relinked.
If you use AEM Desktop App 1.3 on Mac OS, files are saved to a network drive location mounted via Desktop App in two phases. In the first phase, a file is saved locally. This way, a user need not wait for the file to be fully transferred to AEM after saving the file. Instead, the user can resume work as soon as the file is saved locally. In the second phase, Desktop App uploads the updated file to AEM server after a predefined delay (for example, 30s). This operation occurs in the background. Use the Show Background File Sync Status option to view the status of the upload operation.
The Copy and Move methods in the Assets API require the following additional headers to be passed to AEM:
AEM Desktop connects to AEM using a URL that includes the default port. Therefore, the virtualhosts setting in the dispatcher configuration should include the default port number. For more information around virtualhosts configuration, see Identifying Virtual Hosts.
For additional information on configuring the dispatcher to pass through these additional headers, see Specifying the HTTP Headers.
As of now, AEM Desktop App is tested to be compatible with the following:
- Windows 7, with latest service packs and bug fixes
To map your AEM instance with AEM Desktop App, specify the name of the host machine that runs your AEM instance and the port number (http:<aem-url>:port).
If you have configured Proxy Server settings for Windows (Internet Options > LAN Settings), AEM Desktop App will go through the preconfigured proxy server when attempting to connect to the AEM instance that you specify.
You can customize the Asset Info dialog by overlaying one or both of these components:
- The Granite UI page located at /libs/dam/gui/content/assets/moreinfo
After you map the AEM Assets repository to your local drive, you can enable additional icons and the Folder Upload feature to appear for the mapped assets and folders.
Navigate to the Assets UI and hover the mouse pointer over a folder or asset. The following desktop actions are displayed as quick actions in the Card view:
- Open on desktop
- Edit desktop
These desktop actions are also available when you click/tap the Desktop Actions icon in the toolbar after selecting the asset or from the toolbar in the asset page.
Click/tap the Edit desktop quick action to open the asset for editing in an Adobe Creative Cloud application. Opening the asset in edit mode using this quick action checks the asset out. After you finish editing, check the asset in to update the changes in AEM Assets.
If you attempt to open or edit more than five assets simultaneously, a dialog is displayed notifying that the maximum limit has been reached and your request is not processed.
Using AEM Desktop, you can upload an entire folder containing assets from your local file directory to AEM Assets. This way, all assets within the folder are uploaded in bulk instead of having to upload them one at a time.
To link the version history for the assets edited through WebDAV, configure the DAM WebDAV version linking job from Configuration Manager.
Here are some additional resources and knowledgebase articles on Desktop App: