Using the App, the assets within AEM are easily accessible on your local desktop and can be used in any desktop applications. Assets can be easily revealed in Mac Finder or Windows Explorer, opened in desktop applications, and changed locally – the changes are saved back to AEM with a new version created in the repository.
Such an integration allows various roles in the organization to manage the assets centrally in AEM Assets and to access them in the Creative Cloud and other applications, while making it easy to adhere to the various standards including branding.
For detailed information, see the AEM Desktop App release notes.
For details, see Install and connect AEM Desktop App to AEM server.
Only one instance of the AEM Desktop App can be installed and be active at a time.
AEM Desktop App uses system's pre-defined proxy to connect to the Internet over HTTPS. The app can only connect using a network proxy that does not require extra authentication.
If you configure or modify proxy server settings for Windows (Internet Options > LAN Settings), restart the AEM Desktop App for the changes to take effect.
If your proxy requires authentication, the IT team can whitelist the AEM Assets URL in the proxy server settings to allow the application traffic to pass through.
When changing a file from a network share location mounted by the Desktop App, files are saved to that location in two phases. In the first phase, a file is saved locally. A user can save the file and continue working on the file, without waiting for the transfer to complete.
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 View Asset Status option to view the status of the upload operation.
- Upload an asset to AEM Assets.
- Click/tap the AEM Desktop App icon from the toolbar.
- From the menu, select the View Asset Status option.
- From the dialog, review the status of the upload operation.
AEM Desktop App can handle assets up to 40 GB.
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.
You can customize the Asset Info dialog by overlaying one or both of these components:
- The Granite user interface page at /libs/dam/gui/content/assets/moreinfo
On Windows, the cache is at %LOCALAPPDATA%\Adobe\AssetsCompanion\Cache\, where is an encoded version of the AEM host configured in the Desktop App. For example, http://localhost:4502 appears as http%3A%2F%2Flocalhost%3A4502%2F.
On Mac OS X, a similar directory is at ~/Library/Group Containers/group.com.adobe.aem.desktop/cache.
You can control the amount of disk space made available for local caching purposes. The artifacts from the AEM Assets server are cached locally for a smoother experience. You can change the defaults to suit your requirements. Also, you can clear the cache to fetch all assets afresh. To set the desired options, click the application's icon and click Advanced > Manage Cache.
When you clear the cache, it preserves your unsaved changes. Any assets not checked into AEM server are retained and not deleted.
The default location of the cache for the AEM Desktop App is:
- Windows: %LocalAppData%\Adobe\AssetsCompanion\Cache\EncodedAEMEndpoint
- Mac: ~/Library/Group/Containers/group.com.adobe.aem.desktop/cache/EncodedAEMEndpoint
EncodedAEMEndpoint is AEM Desktop App's configured AEM endpoint URL. The value is an encoded version of the targeting URL of the AEM server. For example, if the application is targeting http://localhost:4502, the directory name is http%3A%2F%2Flocalhost%3A4502. The Windows path to the cache directory in this example is %LocalAppData%\Adobe\AssetsCompanion\Cache\http%3A%2F%2Flocalhost%3A4502.
To point the application to a different folder or a different drive, edit the application's configuration file.