#cloud service configuration

[cq-ops]

How to Integrate CQ 5.5 with Adobe InDesign Server 5.5

Adobe InDesign comes in a server edition for automated batch processing.  CQ 5.5 comes with built-in integration with Adobe InDesign Server 5.5.  However, it needs configuration.  More documentation here.

----------------------- RUN INDESIGN SERVER ---------------------

The 64-bit version of InDesign Server is available at %IDS_HOME%\Adobe InDesign CS5.5 Server x64\ (On the Mac, it is by default available at /Applications/Adobe InDesign CS6 Server/InDesignServer.app/Contents/MacOS/)

You can start it with the following command, specifying that the Apache Tomcat Java process LISTEN on TCP port 8090

%IDS_HOME%\Adobe InDesign CS5.5 Server x64>InDesignServer.exe -port 8090

If everything goes well, you should see something like this:

================================================== .  InDesign CS5.5 Server Version 7.5 x64 .  Copyright 1999-2011 Adobe Systems Incorporated and its licensors. .  All rights reserved. See the other legal notices in the ReadMe. ===================================================== INFO  [server] Initializing INFO  [server] Loading the application INFO  [server] Scanning for plug-ins INFO  [server] Registering 110 plug-ins INFO  [server] Completing Object Model INFO  [server] Saving Object Model INFO  [server] Initializing plug-ins INFO  [server] Calling Early Initializers INFO  [server] Starting up Service Registry INFO  [server] Executing startup services INFO  [server] Using configuration configuration_8090 INFO  [server] Initializing the SING gaiji system INFO  [server] Initializing Application INFO  [server] Completing Initialization INFO  [server] Calling Late Initializers INFO  [server] Image previews are off INFO  [server] Server Running INFO  [javascript] Executing File: C:\Programs\Adobe\Adobe InDesign CS5.5 Server x64\Scripts\startup scripts\ConnectInstancesToESTK.js INFO  [javascript] Executing File: C:\Programs\Adobe\Adobe InDesign CS5.5 Server x64\Scripts\converturltohyperlink\startup scripts\ConvertURLToHyperlinkMenuItemLoader.jsx INFO  [javascript] Executing File: C:\Programs\Adobe\Adobe InDesign CS5.5 Server x64\Scripts\converturltohyperlink\ConvertURLToHyperlinkMenuItem.jsxbin INFO  [soap] Servicing SOAP requests on port 8090

---------------- CONFIGURE CQ ----------------

1) As 'Administrator', navigate to Tools->Cloud Services Configurations->Cloud Proxy Configuration.  See below:

2) In the right pane, dbl-click on "ids"

3) Choose 'Edit' in the menu.  See below:

4) In the dialog, change the default http://localhost:8080 to the fully qualified DNS name of the server that runs InDesign Server and the TCP port it LISTENs to.  See below for example:

For horizontal scalability, you can run additional InDesign Server instances ("IDS Workers") and add them to the pool in the above dialog.

--------------------------- TEST INDD FILE INGESTION --------------------------

5) In CQ's DAM console, drag and drop an InDesign .indd file into /content/dam/myFolder

6) Watch the InDesign Server console for messages that look like this:

INFO  [soap] Servicing SOAP requests on port 8090 INFO  [javascript] Executing Script INFO  [script] Fetching resource from CQ: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/myTestInDesignFile.indd WARN  [server] The document "myTestInDesignFile.indd" was converted INFO  [script] Posting to location: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/renditions INFO  [script] Thumbnail created and posted successfully... INFO  [script] Fetching resource from CQ: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/myTestInDesignFile.indd WARN  [server] The document "myTestInDesignFile.indd" was converted INFO  [script] Posting to location: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/myTestInDesignFile.indd/jcr:content/renditions INFO  [script] Posting to path: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/subassets INFO  [script] Posting to path: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/subassets INFO  [script] Posting to path: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/subassets INFO  [script] Finished XHTML export... INFO  [script] Fetching resource from CQ: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/myTestInDesignFile.indd WARN  [server] The document "myTestInDesignFile.indd" was converted INFO  [script] Posting to CQ: /var/proxy/jobs/3dc64365-b519-4b9f-8b6d-949431bc95bc/renditions INFO  [script] Finished IDML export...

[cq-ops]

How to Configure CQ 5.5 with Adobe Scene7

It is possible to upload ("publish") a CQ DAM asset to Adobe Scene7 (cloud SaaS offering).  In order to do this, some configuration steps are necessary.  More documentation is available here.

------------------------- GET SCENE7 CREDENTIALS -------------------------

1) Get details of your Scene7 account and the credentials (userID, password) required to login

2) Login using the Scene7 Publishing System (SPS) client and make sure you are able to upload digital assets

----------------------------------------- CONFIGURE SCENE7 CLOUD SERVICE IN CQ -----------------------------------------

3) As a CQ Administrator, create a new "Cloud Service Configuration" for Scene7.  Navigate to Tools->Cloud Services Configurations->Adobe Scene7

4) Click on the + (plus) sign next to 'Available Configurations'

5) Enter information.  Example below:

6) Enter additional information

7) Test the connection

8) If the connection test is successful, choose the company from the drop-down list

9) Choose the folder to which you'd like the CQ5.5 asset uploads to go to.  see below:

--------------------------------------- CONFIGURE THE CQ SCENE7 WORKFLOW ---------------------------------------

10) Edit the Scene7 workflow to configure it with this newly added Cloud Service Configuration.  As a CQ Administrator, navigate to Workflows->Scene7 and edit it by dbl-clicking it.

11) Dbl-click the 'Scene7' workstep.  See below:

12) Click on the 'Arguments' tab.  From the drop-down list for 'Configurations', choose the Cloud Service Configuration that you created for Scene7.

13) Click OK.

14) Save the Workflow.  See below:

If you forget this step, you will get the following NullPointerEXception:

Publishing to Scene7 failed JavaException: java.lang.NullPointerException: null

The Javascript code that executes the workstep is available at /etc/workflow/scripts/uploadScene7Asset.ecma

---------------- TEST AND VERIFY ----------------

Using DAM, choose an asset, dbl-click it to get to its details page and then click "Publish to Scene7"