Why isn’t a Dynamic Media PDF published when I expect it to?
When the DynamicMedia CloudConfiguration in AEM is set to publish immediately, it would be logical for a PDF that is synchronized to DMS7 to be published accoring to those settings, but that doesn’t happen. Why is that and what can we do?
Description description
Description : We are facing an issue with Dynamic Media for PDFs. During upload, both the PDF and its associated image are generated and available in Dynamic Media. However, the PDF is not getting published and we want it to.
Resolution resolution
The reason why DynamicMedia Scene7 doesn’t publish the PDF is historical.
In fact, in DMS7 there are two different workflows for PDF files:
-
Generation of eCatalog assets This workflow is applied when some kind of processing is included in the jobOptions. It typically generates three types of assets:
- The page images. These are images extracted out of each individual page of the PDF. These images are named using the basename of the PDF, followed by -1, -2, etc. for each page.
- The eCatalog. The eCatalog is a collection asset containing all the page images. It can be displayed in the eCatalog HTML5 viewer to flip through the pages just like a magazine with zoom function and image maps (hot spots). The name of the PDF without extension is reserved for the eCatalog asset.
- The PDF itself. This asset is named as the original PDF without extension, with “pdf” added. Please note that the “.” goes missing.
Since the purpose of this workflow is to display the eCatalog, the page images and the eCatalog assets are published according to the publish setting for the upload job, but the PDF file itself is not, since most customers don’t need the original PDF with this setup.
Even the defaultpdfprocess="thumbnail"setting AEM uses to sync PDF files employs this workflow, which explains why the PDF itself is not published. -
PDF upload as-is (no processing) With this workflow, the PDF is named like the original PDF name without extension, and is published according to the publishing settings of the upload job.
The jobOption used for the sync from AEM to DMS7 can be found in crx/de at:
/conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes/application_pdf
By default, the setting is:
jobParam: "keywords=false&colorspace=auto&links=false&pdfprocess=Thumbnail&pdfbrochure=false&resolution=300"
If you want the PDFs to be published and have no need for the thumbnails, you can change the setting to:
jobParam: "pdfprocess=None"