Adobe Experience Manager Assets

Adobe Experience Manager Assets
Plugin Setup & Configuration
Introduction
The Adobe Experience Manager (AEM) Assets Plugin enables customers who hold both an
active Stackla License and an Adobe Experience Manager instance to seamlessly transfer
media assets from their Stack to their Asset Manager.
Requirements
The Stackla AEM Assets Plugin is available to purchase for clients who have the following
application licenses:
●
●
Adobe Experience Manager 6.1 +
Stackla Platform License
Limitations
The Adobe Experience Manager (AEM) Plugin is currently in Beta. Current known
limitations of the MVP deployment include:
●
●
●
Media transfer limited to only Image assets
Media can only be transferred to one folder at a time within an AEM Assets license
Only one AEM instance can be connected to the Stack
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
Setup
The Adobe Experience Manager (AEM) Assets Plugin is available to install and configure
within the Plugins section of Stackla.
Install the Plugin
First step to configure the AEM Assets plugin is to install the Plugin within your respective
Stack. To install the plugin, select the ‘​Plugins​’ section from the Stackla Menu, and search
for the plugin.
Upon finding the plugin, select ‘​Read More​’ and then select ‘​Install Plugin​’ from the Plugin
Description page.
Connect the Plugin to your AEM Instance
Upon selecting to Install the plugin, you will now be presented with the option to connect the
plugin to your AEM Instance.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
To connect to your AEM Instance, you will need to provide the plugin with the following
information:
●
●
●
●
Endpoint: ​The public facing endpoint for your AEM instance.
Port:​ Any configured port which can be called by Stackla from your AEM Instance.
Username: ​Username for any user with Read, Write permissions to Assets.
Password: ​Password for respective user account.
Often the Endpoint and Port can be found from your AEM Admin login.
Example:
Admin URL:​ ​http://www.stackla-aem.com:4502
Endpoint:​ ​http://www.stackla-aem.com
Port:​ 4502
Once populated, you can select to Connect to your account. Provided your credentials work,
you will have the opportunity to define where you would like Media from Stackla to be
pushed to.
Define Content Destination
The next available fields for the user to populate are the path to the Assets directory in your
AEM Assets instance, and the folder in which you wish Stackla content to be pushed to.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
Example:
Folder URL:​ ​http://www.stackla-aem.com:4502/assets.html/content/dam/client/stackla
Path:​ /content/dam/client
Folder:​ stackla
Note: If a Folder is specified in this section of the AEM Assets plugin that does not exist
within your Stack, the plugin will create the respective folder within your AEM Assets
instance.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
Define Content Push Rules
The final step of the Plugin configuration is specifying the rules around how Media is pushed
from the client’s Stack to their AEM Instance.
The options available are as follows:
●
Automation -​ Automatically send any Rights Approved content to your AEM Assets
instance.
●
Manual​ - Have the opportunity to send content to your AEM Assets instance as
either an individual asset or as a batch process.
These options are not mutually exclusive, and a client may enable both. If a client enables
the manual option (Content Moderation), they will have the opportunity to only enable this
option for ‘​Rights Approved Image Tiles​’ or ‘​All Image Tiles​’.
Once completed, the client can start pushing content from their Stack to their AEM Assets
instance.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
Using the Plugin
The next step is only relevant for those clients who have selected to ‘​Manually​’ push content
across from their Stack.
Batch Push
Users can push up to 100 Images from their Stack to their AEM Assets instance via the
Content Moderation section of Stackla.
Users can either individually select what Media pieces they wish to push across by checking
the Tile selector checkbox
on the respective Tiles or press the ‘Select All’ option within
the Content Moderation view.
This will present the user with the following batch options including the ability to ‘​Send to
AEM​’:
Individual Push
Users can individually push Images from their Stack to their AEM Assets instance by
selecting the ‘More Options’ button on their respective tile.
The ‘Send to AEM’ option is available at the base of the option menu.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
AEM Assets
Regardless of whether the client has configured for Image Assets to be automatically
pushed to AEM Assets or manually, all assets will be made available within the folder
designated in the Plugin configuration.
In addition to the Image Assets being pushed across, Stackla will also send the following
metadata which will be visible within AEM Assets:
●
●
●
●
●
●
●
●
●
●
●
●
Stack - Source Stack
Asset Title - Content Creator Username | Network |
Timestamp
Description - Social Text
Type - Media Type
Language - Recognised Language
Created - Timestamp
Creator Tool - Stackla
Width - Media Width
Height - Media Height
Creator - Username
ID - Tile ID
Location - Latitude / Longitude
Stackla also provides additional meta-data which can be
exposed by the client. Please read the ​AEM Assets Additional Metadata​ guide for further information.
--Disclaimer:
Commercial in confidence. Not to be copied or distributed without written consent from the author.
© Copyright Stackla Pty Ltd 2017.
Download PDF