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.

Using AEM Desktop App

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.

Uwaga:

On Windows, the default Win7 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.

Prerequisites for AEM Server

Uwaga:

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.

Double-click the DMG file, and then click/tap Open to install AEM Desktop App.

Uwaga:

Only one instance of the AEM Desktop App can be installed and be active at a time.

After the app is installed, an icon appears on the MAC menu bar at the top right of the screen.

To configure the URL to AEM Assets, select Preferences from the menu and specify the URL for your AEM instance in the AEM Assets Server URL box. Then, press Enter to save the changes.

Uwaga:

The default URL is http://localhost:4502/content/dam.

From the AEM Desktop App menu, select Mount AEM Assets to mount the AEM Assets server to your local drive.

In the Adobe Marketing Cloud Sign-in page, specify the user name and password for your instance to sign in to Marketing Cloud.

Uwaga:

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.

Checking out assets on Mac

AEM Desktop App lets you check out files to prevent other users from modifying files you’re working on.

From the Context menu, select the Open AEM Assets Folder to open Finder.

Navigate to the location of the asset you want to check out.

From the context menu, select More Asset Info.

Uwaga:

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:

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.

In the Asset Info dialog, click/tap the Checkout icon to check the asset out. The Checkout icon is a toggles to the Checkin icon after you click/tap it.

To check the asset in so it is available to other users, click/tap the Checkin icon in the Asset Info dialog.

File handling

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.

Upload an asset to AEM Assets.

Click/tap the AEM Desktop App icon from the toolbar.

From the menu, select the Show Background File Sync Status option.

From the dialog, review the status of the upload operation.

Connecting to AEM Behind a Dispatcher

The Copy and Move methods in the Assets API require the following additional headers to be passed to AEM:

Double-click the downloaded MSI file, and follow the instructions in the installation wizard to install AEM Desktop App.

Uwaga:

Only one instance of the AEM Desktop App can be installed and be active at a time.

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).

Uwaga:

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.

In the login screen, specify the user name and password for your instance.

Checking out assets on Windows

From the Context menu, select the Explore Assets to open Explorer.

In Explorer, navigate to the location of the asset you want to check out.

Right-click the asset and select Open on Web from the context menu.

In the Asset Info dialog, click/tap the Checkout icon to check the asset out. The Checkout icon is a toggles to the Checkin icon after you click the Checkout icon to check the asset out.

Review the asset in Explorer. A lock appears on the asset that you checked out.

To check the asset in so it is available to other users, click/tap the Checkin icon in the Asset Info dialog.

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

The HTL /css/javascript component located at /libs/dam/gui/components/admin/moreinfo

Which component is overlaid, depends on the nature of the customization. To change which components are displayed as part of the Asset Info dialog, overlay the Granite UI page. To change the HTML/CSS/Javascript content of the dialog, overlay the HTL component.

Enable Desktop icons for mapped assets

After you map the AEM Assets repository to your local drive, you can enable additional icons to appear for the mapped assets and folders.

Navigate to the Assets console and hover the mouse pointer over a folder or asset. An additional icon Reveal on desktop is included as Quick Actions in the Card view.

From the Assets console, click/tap an asset to open its Asset Details page. The icons Reveal on desktop and Open on desktop appear on the toolbar.

Click the Reveal on desktop icon to locate the particular asset in your local file system.

Click the Open on desktop icon to open the local asset in a Creative Cloud application for editing.

(AEM Desktop version 1.6 onwards) If you install AEM cumulative fix pack 8 on AEM 6.2 Service Pack 1, you can open upto five assets from a folder or collection simultaneously on desktop for preview or editing. Select multiple assets from the UI (maximum 5) and then tap/click the Desktop Actions icon from the toolbar.

Select the Open menu option. The selected assets are opened in preview mode.

To edit the assets, select the Edit option. The assets are opened in edit mode.

Linking asset versions edited through WebDAV

To link the version history for the assets edited through WebDAV, configure the DAM WebDAV version linking job from Configuration Manager.

Go to http://<AEM Server>:<Port>4502/system/console/configMgr to open Configuration Manager.

Open the DAM WebDAV version linking job configuration.

Select Enable Version Linking.

Specify the time interval for the scheduler to run the job and the staging timeout time, and save the settings.