sections in the article
This article describes what the Adobe Experience Manager (AEM) Assets integration is and lists the main features.
The AEM Assets integration is referred to as the AEM integration in this article.
About the integration
The AEM integration provides seamless access to all your product media in AEM from inriver.
The integration uses the inriver External Asset Service which is an integral service of the inriver core. In order to communicate seamlessly with AEM Assets, there is a server-side package running inside the customer’s AEM asset instance. There is also an EntityListener running inside inriver to deliver changes from the Resource entity to AEM Assets.
The AEM integration provides the following features:
- Bi-directional functionality of mapped fields between the Resource inside inriver and the Asset inside AEM Assets.
- Synchronization per asset can be toggled on or off from AEM. If synchronization is off, media will remain in both systems but will not be actively updated.
- Publishing or unpublishing an asset in AEM will determine if actual media is displayed in inriver.
- Support for assets initiated in AEM Assets.
- Allows for manual change as well as a programmatical change of assets in AEM.
- Support for AEM Assets as a Managed Service.
- No customization required, only configuration.
- Utilization of smart linking mechanisms in inriver to link assets in AEM to Products in inriver.
- Asset removed from AEM can be configured whether it should be removed or not from inriver.
The below illustration is a conceptual view of the information flow between AEM and inriver.
- Asset uploaded to AEM.
- When an asset is placed into a folder associated with an inriver Metadata Schema, inriver-mapped fieldtypes will appear as properties on the asset.
- In this example, the AEM Asset has not been published yet.
- Open the asset’s properties, and check the Sync to inriver flag. The asset will then be sent over to inriver for synchronization.
- Resource Entity is created inside inriver.
- Metadata is passed over from the AEM Asset to the mapped inRiverFieldTypes.
- Linking can be created in two ways:
- By providing the exact value of the configured fields relevant for link lookup.
- Link properties can be extracted out of the filename of the asset being synchronized.
- The asset’s mapped metadata is available on the Resource entity:
- if AEM asset is published the image will be visible in inriver.
- if AEM asset is unpublished the image will not appear in inriver.
- Asset inside AEM Assets is seamlessly accessible from inriver as a standard Resource entity with all its related features.
Asset metadata synchronization
- If a change is made to the Asset properties inside AEM and it is mapped in the AEM inriver setup it will be synchronized to the fieldtype on the Resource entity in iniver.
- If a change is made to the Resource fieldtype inside inriver, it will be picked up by the AEM entity listener running in inriver and instantly synchronized to the mapped property on the asset inside AEM.
Accessing the integration
You must have a license agreement in place to download and use the adapter. Contact email@example.com for more information.
Once you have a license you will be able to access the adapter download link in this article. Note! If no license is in place you will receive an error message when attempting to use the link.
Get an inRiver license to view below content: