Assets can be presented in a virtual file system using the Adobe Drive integration. Thus, you can access assets stored in the CoreMedia system from your Adobe applications. To make use of this feature, a server web application must be deployed and the Adobe Drive installation must be configured.
Mapping CoreMedia content and folder on the file system
CoreMedia Asset Management stores assets
as content in the content repository. All assets are stored below
a base folder, typically named /Assets.
For the file system mapping, CoreMedia folders are represented as directories
with the same name as the folder.
Asset contents are represented as directories with a special name prefix
to distinguish them from folders.
In the default configuration each picture asset is prefixed with
Asset Picture and each document asset with Asset Document.
For example, an asset
Foo would be represented by the
directory Asset Picture Foo.
Each asset directory contains one file for each rendition.
In the above example the directory
might contain the files Foo_original.psd,
Foo_thumbnail.jpg and
Foo_web.jpg holding the original asset,
the thumbnail and the web rendition, respectively.
![[Note]](../common/images/note.png) | Note |
|---|---|
It is not supported to change the type of an asset by renaming the asset directory using a different prefix. It is not supported that two different users check out renditions of one asset at the same time. It is not supported to add further rendition files that do not indicate one of the configured rendition properties in their name. |
Adobe Drive Web Application
The extension module am-adobe-drive-server-webapp contains the
web application that serves as the backend for the Adobe Drive integration.
For a compact deployment you add this web application
to the Studio Tomcat, modifying the file
blueprint/packages/services/studio-tomcat/pom.xml
to include a dependency and a configuration of the context name.
Alternatively, a new application container can be created
that is dedicated to the Adobe Drive connector web application.
The file application.properties
of the module am-adobe-drive-server-webapp
contains configuration information about the server location
and the content type model.
In any case, you need to configure at least the reference to the
Content Management Server
in the property repository.url
and the password of the webserver user
in the property repository.password.
The property cm.assets.assetBaseFolderPath can be used
to specify the root folder of the content repository for storing
assets. Typically the default /Assets is appropriate.
Further properties in the file application.properties
specify various aspects of the content type model like the names of the
properties storing thumbnails, previews or metadata.
See the configuration file for details about these properties.
In the file src/main/webapp/WEB-INF/application.xml
of the am-adobe-drive-server-webapp module you can
configure the naming scheme for individual asset types.
For each asset type you can configure the name of the content type
storing such assets, the name pattern for directories
representing entire assets and the name pattern for file representing
individual renditions.
The following XML fragment shows the default configuration of the picture asset type:
<bean id="pictureAssetMapping" class="com.coremedia.cms.assets.drive.config.AssetTypeNameMapping">
<property name="contentType" value="AMPictureAsset"/>
<property name="folderPattern" value="Asset Picture {0}"/>
<property name="filePattern" value="{0}_{1}.{2}"/>
</bean>
In the name patterns, the placeholder {0} refers
to the asset document name. {1} represents the
name of the property storing the rendition. {2} is the user-chosen
file extension.
When parsing file names, the parameters {1} and {2}
match alphanumeric strings, only.
Directory patterns must be unambiguous, that is, no conceivable directory name
may match two different directory patterns. The file pattern must contain
all three placeholders, ending in the file extension placeholder {2}.
Modify the given pattern and add further patterns as needed. Update the mapping when you update the content type schema.
Adobe Drive Connector
Before you can install Adobe Drive, you need to have an Adobe client installed, such as Photoshop or Bridge. When you have installed Adobe Drive, add the CoreMedia Drive Connector as follows:
Download the
com.coremedia.adobe.adobe-drive-client.bundle.jarfile from the CoreMedia Adobe Drive Connector REST back-end. Simply enter the connection URL to the back-end into your browser. Click the Download Client Bundle link on the Welcome page.Stop Adobe Bridge or any other Adobe client application, Adobe Drive and the background process
AD4ServiceManager.When the configuration of the CoreMedia Adobe Drive Connector REST back-end was changed, or when the content IDs in the CoreMedia repository have changed (for example, due to re-import in a development or QA system), delete the following cache folders:
Windows:
C:\Users\USERNAME\AppData\Roaming\Adobe\AD4ServiceManager\databaseC:\Users\USERNAME\AppData\Roaming\Adobe\AD4ServiceManager\diskcacheMac:
/Users/USERNAME/Library/Application Support/Adobe/AD4ServiceManager/database/Users/USERNAME/Library/Application Support/Adobe/AD4ServiceManager/diskcache
Add the file
com.coremedia.adobe.adobe-drive-client.bundle.jarto the plugin directory of Adobe Drive. The directory can be found at the following locations:Windows:
C:\Program Files\Common Files\Adobe\AD4ServiceManager\pluginsMac:
/Library/Application Support/Adobe/AD4ServiceManager/plugins/
Restart Adobe Drive.
Now, you can add a new connection using the CoreMedia connector. You are asked to configure a remote URL, which is the root URL of the Adobe Drive web application. Also enter your user name and password for the CoreMedia system.
 |  |  |
 |