Here are some frequently asked questions about the Content Workflow AEM integration. If you have any other questions please get in touch.
Who should set up the integration?
We'd advise that the integration is set up by a technical AEM user, working closely with the people who set up the Templates in Content Workflow.
How long does the import or export take?
This all depends on the number of items you’ve selected for import. The number and size of attachments will also impact the import time.
Can I map a Content Workflow Template to multiple AEM templates?
You certainly can. Please review our support article on how to set up your mappings.
What happens to my Content Workflow Item hierarchy in AEM?
All imported Items will be created in a hierarchical structure under the selected parent node (so the Content Workflow Item hierarchy will be replicated). The Content editor is free to rearrange all Items and the new structure will be kept during further updates.
How are assets attached to Content Workflow Item stored in AEM?
All assets stored in DAM, each of them has the following generated path in AEM:
<dam_path> - path to dam, may be configured in mapping for each import;
<item_id> - item id as folder name, that has item name as title;
<asset_id> - asset id as folder name, that has asset name as title;
<asset_name> - real asset name.
How many times do I need to install the module?
The module needs to be installed once per environment on the author AEM instance.
Can I map multiple Content Workflow fields to a single field in AEM?
The plugin supports many-to-one field mappings for text and guideline field types. It means, that it is possible to map, for example, two Content Workflow fields into one AEM field. The content of such fields will be concatenated and placed in the AEM field. Please check the mappings table in our help documentation that shows all the supported field mappings.
How do the integrations work with the AEM workflow?
Every time the content is imported to AEM, new nodes are created or updated, which trigger appropriate workflows (e.g. create renditions for uploaded images in DAM).
Does the integration support custom components?
Integration is not limited to components, so content can be migrated to any component, which is allowed by mapping properties. Please check the mappings table. However, content may be copied only as it is, without any transformation. We intend to add a plugin system to support data transformation and custom mapping rules for properties.
Does the integration work with AEM tags?
At this stage, the Integration does not interact with AEM tags. However, existing tag id may be migrated as generic content. Such migration won't create AEM tags.
NOTE: AEM Tags support is planned for future releases and is to be implemented via a plugin system.
Does the integration work with AEM publish?
The Integration may be installed on any AEM instance, but we suggest using it on the author instance only.
How to get imported content on AEM to publish instance?
Imported content will not be published automatically. It is available for the editor to review first and it can be published like any other content in AEM. For example via siteadmin or activation tree.
What happens if the Import/Update progress page has been closed during content import/update from Content Workflow to AEM?
The Import/Update page has a unique URL. You can save the page URL and get back to it later to track the progress and see the results. If the page is closed for some reason, the process will continue in the background. Make sure data was migrated or updated prior to working with the same project.
Why rapid growth of the repository and/or significant CPU consumption may occur and how to avoid it?
Content import from GC to AEM consists of three simultaneous actions:
Pages properties filling in.
Media assets import into DAM.
The session save action occurs for each new page, page properties and for each asset. If you perform an import of a large number of rich media pages (more than 500), you may discover two issues:
Significant CPU consumption.
Rapid growth of the repository.
These two issues have a single reason, after every new asset written into DAM, Update Asset Workflow begins creation of multiple renditions for images, and thumbnails for PDF files.
To avoid issues with CPU consumption you can:
Limit count of 'Maximum Parallel Jobs' in 'Granite Workflow Queue' configuration. You can find this config in system configuration '/system/console/configMgr'. This is the best option.
Exclude your GC import path from Workflow Launchers: Node Created, Node modified. For example '/content/dam(?!/gathercontent).*'. In this case, you will not get multiple renditions for images, and thumbnails for PDF files, therefore it is not the best way.
Quick storage growth is due to tarMK works in 'append only' mode. You can produce repository compaction, please follow the Adobe guides:
Online repository compaction (AEM 6.2 and above), manual: https://docs.adobe.com/docs/en/aem/6-2/deploy/platform/storage-elements-in-aem-6.html#Performing Online Revision Cleanup. Also you can configure 'Cleanup Strategy', 'Reference expiry time', 'Pause Compaction' in 'Apache Jackrabbit Oak Segment NodeStore Service' in system configuration '/system/console/configMgr' for efficiency.
Offline repository compaction, manual (AEM 6.0, 6.1, 6.2 and above): https://docs.adobe.com/docs/en/aem/6-2/deploy/platform/storage-elements-in-aem-6.html#Performing Offline Revision Cleanup.
How to control import/update process speed?
The integration plugin speeds up import and update processes using parallel requests and parallel handler threads. The default is 20 threads, a maximum of 200 threads. If you need to speed up the import or update process, you can increase the count of worker threads in the system configuration: go to the system configuration '/system/console/configMgr', find 'Content Workflow': Fixed threads count pool provider' configuration and increase 'Property count of pool threads' value. Please keep in mind that during Content Workflow peak loads, you can get failure responses from Content Workflow API.