If you are using the generatePDFOutput operation of the Output service to process a dynamic PDF document (i.e. to flatten it), you may notice that images referenced by relative paths are missing from the resulting flat PDF file.
This problem will be accompanied by exceptions in the server log similar to the following:
DataManager E com.adobe.service.DataManagerImpl createFileDataBufferFromUrl TRAS0014I: The following exception was logged javax.ejb.EJBException: An unexpected exception occured: ALC-REP-018-000: Resource [/orange_haus.jpg] does not exist or you do not have sufficient rights to access it. at com.adobe.repository.bindings.url.provider.RepositoryUrlDataProviderBean.getInputStream(RepositoryUrlDataProviderBean.java:249) at com.adobe.url.EJSLocalStatelessRepositoryUrlDataProvider_d16709f6.getInputStream(Unknown Source) at com.adobe.url.Util.openUrlStream(Util.java:105) at com.adobe.service.DataManagerImpl.createFileDataBufferFromUrl(DataManagerImpl.java:211) at com.adobe.service.DataManagerPOATie.createFileDataBufferFromUrl(DataManagerPOATie.java:54) at com.adobe.service.DataManagerPOA._invoke(DataManagerPOA.java:91) ... Caused by: com.adobe.idp.dsc.DSCRuntimeException: ALC-REP-018-000: Resource [/orange_haus.jpg] does not exist or you do not have sufficient rights to access it. at com.adobe.repository.commands.RepositoryUrlDataProviderCommand.execute(RepositoryUrlDataProviderCommand.java:178) at com.adobe.repository.commands.CommandProcessor.execute(CommandProcessor.java:135) at com.adobe.repository.bindings.dsc.RepositoryProviderServiceImpl.repositoryUrlDataProvider(RepositoryProviderServiceImpl.java:674) ... 15 more ... XMLFormServic W com.adobe.service.ProcessResource$ManagerImpl log ALC-XTG-029-698:  InvalidSourceException Exception on URL: repository:///orange_haus.jpg Exception: javax.ejb.EJBException: An unexpected exception occured: ALC-REP-018-000: Resource [/orange_haus.jpg] does not exist or you do not have sufficient rights to access it. XMLFormServic W com.adobe.service.ProcessResource$ManagerImpl log ALC-XTG-016-649:  Error attempting to read from file XMLFormServic W com.adobe.service.ProcessResource$ManagerImpl log ALC-XTG-029-461:  XFAImageService: Image cannot be resolved for node: StaticImage1.
You may have rendered the PDF initially using the images referenced by relative paths (i.e. they were available at these relative locations on the server at render-time). This image content is then stored in the PDF file for the initial page views. Static PDF files do not re-render and therefore the image content already stored in the PDF remains valid, so the images are always displayed. Dynamic PDF files can re-render later (where the relative paths to the images may no longer be valid), in which case Acrobat/LiveCycle will attempt to resolve the relative paths to the images again.
Acrobat can display the images without any problems, even if you force Acrobat to re-render the PDF document (by merging again with data). Acrobat recognizes that the image is referenced by relative path, discovers it cannot resolve the path anymore, and therefore picks up the image content which is stored in the PDF already.
LiveCycle however does not handle this correctly. This is a bug in the Output service for PDF files with a target version > 8.0. If the target version is < 8.0 then the images are retained.
This issue will be fixed in the next LiveCycle ES2 service pack (if there is one) and future versions (e.g. ES3). There is a patch available for LiveCycle ES2 SP2 18.104.22.168 (XMF-2.204, FRM-2.202, OPT-2.201), so contact your LC support representative should you require this patch.
The solution exposes a new option “Use Following Resources from PDF” in the generatePDFOutput advanced settings. If you set this option to “IMAGES”, it will include the image content from the PDF, rather than attempting to resolve the relative path.