A proxy to distribute the load of certain processing tasks. A proxy is an AEM instance that communicates with a proxy worker to fulfil a specific task, and other AEM instances to deliver the results.

A proxy worker to define and manage a specific task.
These can cover a wide variety of tasks; for example, using an InDesign Server to process files.

To fully upload files to AEM Assets that you have created with Adobe InDesign a CQ DAM Proxy is used. This uses a proxy worker to communicate with the Adobe InDesign Server, where scripts are run to extract metadata and generate various renditions for AEM Assets. The proxy worker enables the two-way communication between the InDesign Server and the AEM instance(s) in a cloud configuration.

If the InDesign Server is not installed or not configured, then you can still upload an .indd file into AEM. However the renditions generated will be limited to png and jpeg, you will not be able to generate html, idml or the page renditions.

Configuring the AEM Assets Workflow

This workflow is setup with default values that can be adapted for your setup on the various author instances (this is a standard workflow, so further information is available under Editing a Workflow). If you are using the default values (including the SOAP port), then no configuration is needed.

After the setup, uploading InDesign files into AEM Assets (by any of the usual methods) will trigger the workflow required to process the asset and prepare the various renditions. Test your configuration by uploading an .indd file into AEM Assets to confirm that you see the different renditions created by IDS under <your_asset>.indd/Renditions

Media Extraction

This step controls the extraction of media from the .indd file.

To customize, you can edit Arguments tab of the Media Extraction step.

ExtendScript library
This is a simple http get/post method library, needed by other scripts.

This library provides the HTTP functionality required to communicate with Sling. This setting specifies the library to be send to the InDesign Server for use there.

The ThumbnailExport.jsx script run by the Media Extraction workflow step generates a thumbnail rendition in .jpg format. This rendition is used by the Process Thumbnails workflow step to generate the static renditions required by AEM.

You can configure the Process Thumbnails workflow step to generate static renditions at different sizes. Ensure that you do not remove the defaults, because they are required by the AEM Assets UI. Finally, the Delete Image Preview Rendition workflow step removes the .jpg thumbnail rendition, as it is no longer needed.

Page Extraction

This creates an AEM page from the extracted elements. An extraction handler is used to extract data from a rendition (currently HTML or IDML). This data is then used to create a page using the PageBuilder.

To customize, you can edit the Arguments tab of the Page Extraction step.

Page Extraction Handler
From the drop down list, select the handler that you want to use. An extraction handler operates on a specific rendition, chosen by a related RenditionPicker (see the ExtractionHandler API).
In a standard AEM installation the following is available:

Page Name
Specify the name you want to have assigned to the resulting page. If left blank then the name is "page" (or a derivative if "page" already exists).

Page Title
Specify the title you want to have assigned to the resulting page.

Page Root Path
The path to the root location of the resulting page.
If left blank the node holding the asset's renditions will be used.

Page Template
The template to use when generating the resulting page.

Page Design
The page design to be used when generating the resulting page.

Configuring the Proxy Worker for InDesign Server

Nota:

The worker resides on the proxy instance.

In the Tools console, expand Cloud Services Configurations in the left pane. Then expand Cloud Proxy Configuration.

Double-click the IDS worker to open for configuration.

Click Edit to open the configuration dialog and define the required settings:

IDS Pool
The SOAP endpoint(s) to be used for communicating with the InDesign Server. You can add, remove and order items are required.

Click OK to save.

Configuring Day CQ Link Externalizer

If the InDesign server and AEM run on different hosts or either or both these applications do not run on default ports, configure Day CQ Link Externalizer to set the host name, port, and content path for the InDesign server.

If there are multiple machines running InDesign Servers, add SOAP endpoints (number of processors per machine -1) for each machine.

Nota:

You may choose to enable Blacklisting of IDS workers when working with pool of workers.

To do so, enable the "enable.retry.name" checkbox, under the com.day.cq.dam.ids.impl.IDSJobProcessor.name configuration, which enables IDS job retrials.

Also, under the com.day.cq.dam.ids.impl.IDSPoolImpl.name configuration, set a positive value for max.errors.to.blacklist parameter which determines number of job retrials before barring an IDS from the job handlers list

By default, after the configurable (retry.interval.to.whitelist.name) time in minutes the IDS worker is revalidated. If the worker is found online, it is removed from the blacklist

Enabling support for InDesign server 10.0 or higher

For InDesign server 10.0 or higher, perform the following steps to enable multi-session support.