Integrating Adobe DPS in Enterprise Server 9

The functionality of publishing content to Adobe DPS is provided through an Enterprise Server plug-in.

This article describes how to integrate Adobe DPS in Enterprise to make it possible to publish from Enterprise to Adobe DPS.

Note: If you are looking for steps to integrate Adobe DPS (2015), see Integrating Adobe DPS (2015) in WoodWing Enterprise.

Steps to perform

Steps need to be performed to install the necessary software and to configure Enterprise Server.

Note: It is assumed here that an Adobe subscription account for using Adobe DPS is available. The credential details are required during the setup of Enterprise Server for connecting to the service.

Setting up Enterprise Server - required steps

1. Installing the crossdomain.xml file

2. Making the PHP ZIP Module available

3. Verifying the Adobe DPS Server plug-in

4. Activating the Digital Magazine license

5. Setting up custom metadata properties

6. Adding custom metadata properties to dialog boxes

7. Setting up a Publication Channel

8. Setting up Multiple Device support

9. Setting up the folio export folder

10. Defining the folio file format

11. Connecting to the Adobe Distribution Service

12. Testing Enterprise Server

13. Scheduling the cleanup of the export folder

Installing software

14. Installing the Digital Publishing Tools panels for Smart Connection

15. Installing the Adobe DPS tools

16. Installing Content Station Pro

Setting up Enterprise Server - optional steps

17. Connecting to Adobe DPS through a proxy server

18. Configuring parallel upload to the Adobe DPS Server

19. Allowing Product IDs to be duplicate

20. Overriding the CA certificates

21. Overruling the folio creation behavior of Smart Connection

22. Adding Workflows for Widgets

23. Matching Enterprise metadata names to Adobe DPS terms

24. Setting the location of the HTML Resource folder

1. Installing the crossdomain.xml file

Creating the content for the publication is done in InDesign by using the Digital Publishing Tools panels which are part of Smart Connection for InDesign.Some of these panels (such as the Widget panel) need to receive information from and send information to Enterprise Server. This communication is established through the crossdomain.xml.

Step 1. Download the crossdomain.xml file from the software download page.

Step 2. Unzip the file and place it in the root of your server.

Example: /Applications/MAMP/htdocs/<server name> /var/www/html/<server name>

2. Making the PHP ZIP Module available

The Adobe DPS Server plug-in makes use of the ZIPArchive class of the PHP ZIP Module, which therefore needs to be installed.

• For Linux/Mac OS X: Compile PHP with ZIP support by using the --enable-zip configure option.

Note: If you have valid reasons not to (re)compile PHP, please use this alternative method. Show me When PHP is not compiled with the --enable-zip option, the Adobe DPS Server plug-in falls back on the Info-ZIP command line tools (zip and unzip). For Mac OS X these tools are pre-installed so no further steps are therefore needed. For Linux, make sure that these tools are installed: Step 1a. Open the Terminal and enter the following command: zip When you see the help page starting with Copyright (c) 1990-2008 Info-ZIP, then the ZIP tool is already installed and no further steps are needed. When you see an error: The program 'zip' is currently not installed, then the ZIP tool is missing. Continue with the next step. Step 1b. Enter the following command: sudo apt-get install zip

• For Windows: No installation is required; the ZIP extension is built into PHP (since PHP 5.3).

3. Verifying the Adobe DPS Server plug-in

The Adobe DPS functionality in Enterprise is provided by an Enterprise Server plug-in named 'Adobe DPS'. This plug-in is installed and activated by default. Verify that this is the case by following these steps:

Step 1. In Enterprise Server, access the Server Plug-ins page.

Step 2. Locate the plug-in named Adobe DPS and verify that it is enabled, as indicated by the green Plugged In icon .

Note: In case it shows a different icon such as the Unplugged icon , click the icon to activate the plug-in.

4. Activating the Digital Magazine license

In order for Smart Connection users to use the Digital Publishing Tools panels, a license needs to be activated.

Step 1. In Enterprise Server, access the License Status page.

Step 2. Activate the license named Digital Magazine (9).

5. Setting up custom metadata properties

Custom metadata properties are used for matching files in Enterprise with functionality in DPS.

Example: Setting the 'Dossier intent' property of a Dossier to 'TOC' indicates that the Dossier holds the table of content of an issue and ensures that the content is linked to the TOC button of the viewer.

Step 1. In Enterprise Server, access the Metadata Maintenance page.

Step 2. Make sure that the Brand list and Type list both show <All>.

Step 3. Scroll to the bottom of the page and click Add Custom Property. The Custom property page appears.

Step 4. Add the property (see list below).

Step 5. Click Update.

Step 6. Click the Left Arrow icon to return to the Metadata page.

Step 7. Repeat steps 4 to 6 until all properties are added.

Note: Make sure to add all properties, even when not using some of them; the test on the Health Page fails when properties are missing.

Tip: To separate the properties from the general Enterprise properties in a dialog box, use the Group field to display the Adobe DPS properties in their own tab.

6. Adding custom metadata properties to dialog boxes

The custom metadata properties that were added to Enterprise in the previous step need to be made available to the user. This is done by adding them to the Workflow dialog boxes of the objects for which the properties are to be used.

Example: The property for setting the intent of a Dossier needs to be added to the Properties dialog box of a Dossier.

Step 1. In Enterprise Server, access the Dialog Setup page.

Step 2. In the Brand list, choose the Brand to which you want the properties to be available.

Step 3. Add the properties listed in the table below by doing the following:

Step 3a. From the Object Type list, choose the object listed in the Object Type column.

Step 3b. From the Action list, choose the action listed in the Action column.

Step 3c. At the bottom of the page, click Add Action Property. Options for adding a property appear.

Step 3d. (Optional) In the Order field, enter a number that defines the order in which the property should appear.

Step 3e. From the Property list, choose the property listed in the Property column of the table.

Step 3f. Select the check box for the option Editable and (optionally) for the option Multiple objects (requires Enterprise 9.2 or higher).

Note: Enabling 'Editable' makes sure that the user can edit the property; enabling 'Multiple objects' makes sure that the property appears in the dialog box when a user selects multiple files.

Step 3g. Click Add Action Property. The property is added and a new set of options appear for adding another property.

Step 3h. Repeat steps 3a to 3g until all properties in the table are added.

Object Type	Action	Property
Image	Create	* Intent (INTENT)
Image	Set Properties	* Intent (INTENT)
Dossier	All	* Article Access (ARTICLE_ACCESS)
Dossier	All	* Dossier is Ad (DOSSIER_IS_AD)
Dossier	All	* DPS Section (DPS_SECTION)
Dossier	All	* Hide from TOC (HIDE_FROM_TOC)
Dossier	All	* Intent (DOSSIER_INTENT)
Dossier	All	* Kicker (KICKER)
Dossier	All	* Layout for TOC (LAYOUT_FOR_TOC)
Dossier	All	* Show Overlays in Browse (OVERLAYS_IN_BROWSE)
Dossier	All	* Story Navigation (DOSSIER_NAVIGATION)
Dossier	All	* Story Title (READER_LABEL)
Dossier	All	Author
Dossier	All	Description
Dossier	All	Keywords
Dossier	All	Slugline
Other	Create	*Intent (INTENT)
Other	Set Properties	*Intent (INTENT)

Note: The custom property named 'Widget Manifest' does not need to be added to a dialog box; it is used internally by Enterprise Server only.

Step 4. (Optional) To enable users to automatically add an image or layout to a Dossier when the file is added to the system, also add the following properties:

Object Type	Action	Property
Image	Create	Dossier (DOSSIER)
Layout	Create	Dossier (DOSSIER)

7. Setting up a Publication Channel

In Enterprise, publishing content to Adobe DPS is done through a Publication Channel.

Step 1. On the Brand Maintenance page, locate the Publication Channel options.

Step 2. Click Add.

The Publication Channel Maintenance page appears.

Step 2a. In the Name field, enter a name.

Step 2b. (Optional) In the Description field, enter a description.

Step 2c. From the Publication Channel Type list, choose DPS.

Step 2d. From the Publish System list, choose Adobe DPS.

Step 2e. Leave the Suggestion Provider field set to None, it is not used for Adobe DPS.

Step 2. Click Create.

The Editions and Issues sections appear.

Creating Editions

In Enterprise, Editions represent the device that is published to, such as an iPad, a Galaxy, a Playbook, and so on. An Edition should therefore be created for each output device.

Step 3. Click Add Edition.

The Edition Maintenance page appears.

Step 3a. Enter a name in the Name box.

Notes: The name must match the corresponding Device name, as defined on the Output Device Maintenance page (Output Devices are set up in the next step 'Setting up Multiple Device support'). The name should be descriptive, such as “Apple iPad”, “Samsung Galaxy”, and so on, especially because the name also appears in the Editions panel in InDesign and the Digital Publishing application in Content Station.

Step 3b. (Optional) Enter a description in the Description box.

Step 3c. Click Update.

The Publication Channel Maintenance page appears with the newly created Edition added to the Editions menu.

Step 3d. (Optional) Add additional Editions as required.

Step 3e. In the Order box on the Publication Channel Maintenance page, enter an order number for each Edition and click Reorder. This will determine in which order the Editions are displayed in the client application interfaces.

Notes: When a layout has multiple devices assigned (in the form of Editions), the first Edition that is assigned to the layout is used as the primary device. The Landscape Layout Width setting of this primary device (as set on the Output Device Maintenance page) is used for determining whether the layout should be treated as a layout in landscape orientation or portrait orientation. The number of Editions assigned to the layout could of course be different from the total number of devices configured. For example, assume that the following devices have been configured with the following order numbers: 10 iPad 20 Galaxy 30 Playbook If for a layout only the Galaxy and Playbook Editions have been assigned, then the Galaxy is considered as the primary device, even though the iPad Edition precedes it in the configuration.

Creating Issues

Step 4. On the Publication Channel Maintenance page, click Add Issue.

The Issue Maintenance page appears.

Step 4a. Fill out the details.

Note: At the most basic level, only a name and the Adobe DPS Product ID needs to be entered; all other options can also be set at a later stage by modifying the created Issue.

Step 5. Click Update.

Finishing the setup

Step 6. Click the arrow at the bottom of the page to return to the Publication Channel Maintenance page.

Step 7. Click the arrow at the bottom of the page to return to the Brand Maintenance page.

Step 8. (Optional, only if multiple Publication Channels have been created) From the Default Publication Channel list at the top of the Brand Maintenance page, choose the default Publication Channel that should act as the default DPS channel.

Note: In order for this feature to work properly, it is imperative that an order sequence for the created Issues is correctly specified on the Publication Channel Maintenance page. If this is not done (or not done correctly), Enterprise may not be able to properly determine the Previous and Next issues.

Figure: The Default Publication Channel list.

8. Setting up Multiple Device support

When creating content that is going to be viewed on the Adobe Content Viewer, it is important to know on which device the content is going to be viewed so that the design in the correct dimensions (height and width) can be used.

Similarly, when the content is exported by Enterprise and a folio file is generated, Enterprise needs to know which dimensions to use, which image quality settings should be applied, and so on.

In Enterprise, this is achieved by the following processes:

• Defining one or more Output Devices, each representing the properties of the device such as page dimensions, image quality and more.
• Setting up Editions that correspond to the defined output devices.

This configuration is subsequently used by the following tools:

• The page dimensions are used for creating DP Artboards in Smart Connection for InDesign, allowing the designer to see the boundaries of the device. For more information, see the Digital Publishing Tools User Guide, appendix C 'Working With DP Artboards'.
• The Editions are used by the Smart Connection for InDesign to assign and view content that is used in a specific output device only. Editions are also used in Content Station as a way to select the device to export the content to.

At least 1 Output Device and 1 Edition therefore need to be set up.

Tip For a step-by-step tutorial about setting up a multi-device folio production, using either pixel-perfect or actual size Artboards and properly configured templates, see the document Setting up Devices, Templates and Artboards for Adobe DPS.

Configuring Output Devices

Output devices are managed through the Output Devices Maintenance page in Enterprise Server.

The following devices are provided by default:

• iPad. Dimensions: 1024x768 pixels
• Kindle Fire. Dimensions: 1024 x 600 pixels
• Xoom. 1280 x 800 pixels

To create additional Output Devices, follow these steps:

Step 1. In Enterprise Server, access the Output Devices Maintenance page.

Figure: The Output Devices Maintenance page.

Devices for the iPad, Kindle Fire and Xoom are defined by default.

Step 2. Click New to define a new device or click the name of an existing device to change its settings.

Step 3. Click Create.

Step 4. Click the Left Arrow icon to return to the Output Devices page.

Step 5. Repeat steps 1 to 4 to create as many devices as needed.

9. Setting up the folio export folder

During the process of previewing or publishing stories, a .folio file is created and saved to the Enterprise Server export folder. The location of this folder is defined in the following file:

<server path>/config/config_dps.php

The definition is as follows:

define( 'ADOBEDPS_EXPORTDIR', EXPORTDIRECTORY.'AdobeDps'/ );

This means that the folio files are placed in a folder named AdobeDps in the location defined by the EXPORTDIRECTORY (set in the config.php file).

In a default setup, this results in the following location:

/Filestore/_SYSTEM_/Export/AdobeDps

Within the folder, the following subfolder structure is maintained:

• For Preview operations: files are kept separate for each user and will appear in the following folder structure:

user_1/operation_2/issue_3/device_4

• For Publish operations: files are shared between users and will appear in the following folder structure:

issue_3/device_4

• For both preview and publish operations: the device folder is archived into one folio file:

device_4.folio

Note: The value device_x corresponds to the defined device as set on the Output Devices page. The ID of an output device can be found in the URL of the Output Device Maintenance page.

Example In the following example, the device ID is 1: http://<server path>/server/admin/outputdevice.php?id=1

10. Defining the folio file format

A page in a folio file is essentially an image with optionally interactive objects placed above it.

These background images can be exported in one of the following formats:

• JPEG. Default setting.
• PDF. Allows zooming in on the page.
• PNG. Ensures color consistency with any content placed on top of the background (see comment below).

In case a format other than JPEG needs to be used, follow these steps:

Step 1. In the configserver.php file, locate the SERVERFEATURES section.

Step 2. Add or enable the DPSFolioFormat ServerFeature:

new Feature( 'DPSFolioFormat', '<EditionID>, <format>;<EditionID>,<format>' ),

Step 3. Use the following values:

• EditionID: the ID of the Edition (device) to which the issue is assigned. Obtain this from the URL of the Edition Maintenance page.

Example: In the following example, the Edition ID is 45: http://<server path>/server/admin/hpeditions.php?id=45&publ=1&channelid=63

• format: the file format to use. Possible values: PDF or PNG. In case any other value or an empty value is used, the folio is exported in JPEG format.

Example: new Feature( 'DPSFolioFormat', '23, PDF;28,PNG'),

11. Connecting to the Adobe Distribution Service

In order to be able to upload content to the Adobe Distribution Service, the credentials for the Adobe subscription account need to be configured in Enterprise Server.

Step 1. Access the following file:

<server path>/config/config_dps.php

Accounts can be set up per Publication Channel and/or per Edition. This allows publishing to different devices separately.

The definition is as follows:

define( 'ADOBEDPS_ACCOUNTS', serialize( array( 
1 => array(      // Publication Channel ID 
0 => array(     // Edition ID 
'username'	=> '', 
'password'	=> '', 
'serverurl'	=> ''
),

Step 2. Configure the ADOBEDPS_ACCOUNTS option as explained in the comments of the file.

12. Testing Enterprise Server

Step 1. In Enterprise Server, access the Health Check page.

Step 2. At the bottom of the page, click Clear All.

Step 3. Only select the Adobe Digital Publishing System (DPS) test.

Step 4. Click Test.

The test is executed and the result is displayed next to the test. It should display “OK”.

Note: If the test fails, an error is displayed together with instructions for solving it. Follow the instructions and then run the test once more.

13. Scheduling the cleanup of the export folder

When publishing an issue to Adobe from Content Station, all required data is collected in the Adobe DPS Export folder. After publishing, the folder is not cleaned up automatically; this is beneficial when updating an issue because only the updated content then has to be regenerated.

The Export folder for a user is only cleaned up when that user logs in. However, if a user stays logged in, the export folder will never be cleaned up. As a result, the file size of this folder can increase excessively.

We therefore advise to clean up the export folder on a daily basis, preferably by automating this task using an Enterprise Server Job.

Step 1. Access the Enterprise Server Job Config page.

Step 2. Click the AdobeDPS Server Job.

Note: This Server Job was automatically generated when the Enterprise Server Plug-ins page was accessed for the first time after installing Enterprise Server.

The configuration page for this job appears.

Step 3. In the Username list, choose a user with system admin privileges.

Step 4. Click Update.

The Enterprise Server Job Config page appears.

Step 5. (Optional but recommended) Set up a schedule to clean up the Export folder on a daily basis.

For more information about setting up a schedule, see Working with Enterprise Server Jobs.

14. Installing the Digital Publishing Tools panels for Smart Connection

The Digital Publishing panels of Smart Connection provide many tools for creating interactive content, such as adding Hotspots, Scrollable Areas, Internet content, HTML5 content and more.

To install the panels, install the Smart Connection plug-ins and make sure to include the Digital Publishing plug-ins.

For more information, see Installing Smart Connection 9.

Note: In order for the content of the Digital Publishing Tools panels in InDesign to be displayed, Adobe Flash Player needs to be installed on each client system running InDesign. It is recommended to install the latest version of Flash Player, obtained from http://get.adobe.com/flashplayer/.

15. Installing the Adobe DPS tools

The Adobe Folio Producer Tools are required in order to be able to preview stories in either InDesign or Content Station.

Make sure that the latest version is installed. For more information, see Adobe Help Installing DPS Tools.

16. Installing Content Station Pro

Managing the digital publication and publishing it to Adobe is done in Content Station Pro.

For more information about installing Content Station, see Content Station 9 installation.

Optional steps

17. Connecting to Adobe DPS through a proxy server

A proxy server can be used as a secure connection between Enterprise Server and the Adobe DPS Server.

Step 1. Install a proxy server with support for HTTPS (SSL) and the HTTP CONNECT method.

Note: Make sure that Enterprise Server has access to the network machine that the proxy server runs on.

As an option, Basic Authentication can be enabled for the proxy server (if supported). Other methods are not supported by Enterprise Server.

Notes: A wide range of proxy servers are available to choose from, including for example FreeProxy (for use on Windows systems) from Handcrafted Software. Apache can also be configured as a proxy server by using the mod_proxy module. When this Apache instance also runs other applications, such as Enterprise Server, we found it quite problematic to get Basic Authentication working since URLs cannot be used in proxies (should be IP or host name only). It therefore easily finds other rules through which access is gained, bypassing the configured authentication. Without Basic Authentication though, configuration is quite simple and takes away the need of a dedicated proxy server.

Step 2. Configure Enterprise Server as follows:

Step 2a. Open the configserver.php file for the Enterprise Server installation.

Step 2b. Locate the ENTERPRISE_PROXY section.

Step 2c. Remove the two forward slashes (//) in front of proxy_host and proxy_id and enter the following values:

• proxy_host: the IP for the proxy server
• proxy_port: the port number for the proxy server

Step 2d. (Optional) Remove the two forward slashes (//) in front of proxy_user and proxy_pass and enter the following values:

• proxy_user: the name of the user as registered on the proxy server.
• proxy_pass: the password for the user as registered on the proxy server.

Step 2e. Save the file.

Step 3. Test the installation by performing some publish actions to the Adobe DPS Server. The connection should now successfully route via the proxy server.

18. Configuring parallel upload to the Adobe DPS Server

By default, publishing or updating multiple stories to the Adobe DPS Server is done in parallel.

Uploading in parallel can hugely increase performance, especially for those installations where:

• Dozens of stories are being uploaded.
• The uploaded files are not too big or too different in size.
• The WAN connection has enough bandwidth (> 10 MB upload stream).
• The upload connection is not heavily used by other users in the meantime.
• The Adobe DPS server is far away, such as on another continent.

The maximum number of connections used is set to 5 connections by default.

When to increase or decrease the number of connections

• Increase the number when a lot of bandwidth is available and/or very few users are uploading at the same time. (Note that a value of 3 is considered to be very low.)

• Decrease the number when very little bandwidth is available and/or many users are uploading at the same time.(Note that a value of 10 is considered to be very high.)

To change the number of connections, follow these steps:

Step 1. Open the config_dps.php file.

Step 2. Locate the PARALLEL_PUBLISHING_MAX_CONNECTIONS section.

Step 3. Modify the default value of '5' for the following option to suit your needs:

define( PARALLEL_PUBLISHING_MAX_CONNECTIONS, 5);

Step 4. Save the file.

PHP requirements

For this feature to work, the following PHP requirements must be met:

• cURL library must be installed and enabled for PHP.
• The PHP memory_limit setting should be set to at least 512M or higher.

Do this by adjusting the php.ini file; after changing it, make sure to restart the Web Server.

19. Allowing Product IDs to be duplicate

The Adobe Product ID is a property of the DPS issue and needs to be unique for each device.

When a new DPS Issue is created in Enterprise, the system checks wether the Product ID is filled in and if it is unique. However, this functionality is too restrictive for configurations where different Publication Channels are set up for each type of device.

Enabling the AllowDuplicateProductID option in the config_dps.php file allows the use of duplicate Product IDs, although not within the same Publication Channel.

CAUTION: This option should only be enabled if separate Publication Channels are used for different devices. With this setting enabled it is possible to define the same product ID for the same device for separate Publication Channels. This will lead to mixed up content on the device and in the library.

To enable this feature, follow these steps:

Step 1. Access the following file:

<server path>/config/config_dps.php

Step 2. Locate the following option and set its value to true:

define( 'AllowDuplicateProductID', false );

Step 3. Save the file.

20. Overriding the CA certificates

The Enterprise CA Bundle contains a list of CA certificates for secure connections. This file is used by cURL to check the certificate of the server to connect to.

When upgrading or installing a new server, the Adobe DPS Health Check will search for this file. If not found, the latest version is downloaded from the Internet and installed on the given file path.

Should you want to override the default file by your own file, follow these steps:

Step 1. Open the configserver.php file.

Step 2. Locate the CA Bundle option.

Step 3. Modify the path to the bundle:

define( ENTERPRISE_CA_BUNDLE, WOODWINGSYSTEMDIRECTORY . /Certificates/ca-bundle.crt );

21. Overruling the folio creation behavior of Smart Connection

When using Smart Connection for InDesign to create content that is going to be published to Adobe DPS, the layouts are at some point converted to the Adobe .folio file format.

In order not to take up valuable time by generating folio files at moments when this is not really necessary (such as at the beginning of the creation process), folio creation is only done when a layout is checked-in while no folio is created when a layout is saved or saved as a new version.

When the layout is not converted to a folio file, a replacement folio (referred to as a dummy folio) is generated by Smart Connection and used in place of the original folio.

The default behavior of automatically having a folio file generated or not can be overruled. For more information, see Overruling the folio creation behavior of Smart Connection.

22. Adding Workflows for Widgets

It is very likely that Widgets will be used for creating interactive content. You might therefore want to set up a specific workflow for them. By default, Widget files are defined as type “other”.

For information about setting up Workflows, see Creating Workflow Statuses.

23. Matching Enterprise metadata names to Adobe DPS terms

Enterprise Server matches 2 of its metadata properties to properties of the Adobe Content Viewer:

• Slugline. (Enterprise 9.0 – 9.6 only. From Enterprise 9.7 onwards, a custom metadata field named 'Kicker' is used ¹) Matched to the Adobe property named 'Kicker'. The Kicker is used for displaying the section title of a magazine, such as Reviews, Features, or Editorial. It appears in the scrubber and in the Browse mode.

¹ Although Slugline can also be used in Enterprise 9.7 and higher, the advantage of using Kicker over Slugline is that the Kicker allows the user to choose from a list of values whereas with the Slugline the user has to manually enter the values (which increases the chance of making errors or using different writing styles).

• Keywords. Matched to the Adobe property named 'Tags'. Tags are a collection of keywords for the story. They appear in the scrubber and in the Browse mode.

You might want to change the name of the properties in Enterprise Server to match the names of the Adobe properties so that InDesign or Content Station users are better aware what these properties are used for.

Step 1. In Enterprise Server, access the Metadata page.

Step 2. From the Brand list, choose the Brand in which you want to make the change.

Step 3. In the list of Dynamic Properties, locate the property named Slugline.

Step 4. Click the name. The Dynamic Property page for that property appears.

Step 5. In the Display Name field, enter Kicker.

Step 6. Click Update.

Step 7. Repeat the process to set the display name of Keywords to Tags.

24. Setting the location of the HTML Resource folder

When HTML resources such as fonts or CSS files are used in multiple stories within a publication, it is possible to add them to the publication only once instead of having to add them to each Dossier in which they are used.

This is done by adding these files to a dedicated Dossier, referred to as the HTML Resources Dossier. The content of this Dossier (when in ZIP format and assigned to the correct Publication Channel) is extracted to a specific folder within the folio file. File paths can then be used to refer to these files from wherever they are needed in the publication.

Using this method can greatly decrease the total file size of your publication.

The location of where the files are extracted to is defined by the following settings:

• config.php file: PERSISTENTDIRECTORY setting. The location where persistent data is stored.

define ('PERSISTENTDIRECTORY', WOODWINGSYSTEMDIRECTORY . '/Persistent');

• config_dps.php file: ADOBEDPS_PERSISTENTDIR setting. The location where HTML Resources cache files are stored. By default, this is a subfolder of the PERSISTENTDIRECTORY setting in the config.php file.

define( 'ADOBEDPS_PERSISTENTDIR', PERSISTENTDIRECTORY.'/AdobeDps' );

To use a custom location, follow these following steps:

Step 1. Create a folder at the custom location and make sure that sufficient Read and Write access rights are applied.

Step 2. In the config_dps.php file, replace the section "PERSISTENTDIRECTORY.'/AdobeDps" by a custom path.

Example: In the following example, the custom path "C:/PersistentData/AdobeDPS" is used: define( 'ADOBEDPS_PERSISTENTDIR', 'C:/PersistentData/AdobeDPS' );