Friday, 21 March 2014

Storing LiveCycle ES process data in a remote Adobe Experience Manager JCR

As a user of both Adobe LiveCycle ES and Adobe Experience Manager, you can create business applications that make use of both platforms. That is, you can create an enterprise solution that uses functionality provided by Adobe CQ and LiveCycle ES. By combining the functionality of both server products, you can create applications to solve your business requirements.

For example, assume that you have a LiveCycle business process that uses PDF documents. Next assume that the process extracts data from the PDF document and you want to store the data in a JCR that belongs to a remote AEM server.

Process data is sent from a LiveCycle ES process to the AEM JCR
As shown in the previous illustration, you can create a custom LiveCycle ES Document Service Component (DSC) that is able to post process data to a custom AEM Sling Servlet. The custom Sling Servlet persists the process data in the AEM JCR by using the JCR API. The following illustration shows a LiveCycle ES process that sets process variables and then uses the custom DSC to persist the data into the AEM JCR.

To read this development article, see

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

No comments:

Post a Comment