Adobe LiveCycle (Archived)

Report · 1/8/13

Hi All

I am here for some high level administration information on Adobe
LiveCycle ES. In Our Organization, Output ES is used for Customer
Communication letter generation (Will generate at least 1000 page pdf
every time).

I am not happy with Adobe from day one onwards. Though it is good tool
and has very good functionalities, Its very complex to develope for
multiple developers.

Pls share your feedback on Output ES2

The production server frequently throws OutOfMemory error whenever DDX
is used in generating Letters.

Few queries for my better understanding

1) What is the maximum No. of objects(Process, Forms, XSD & etc.) a
application can hold(I have applications with only 25 Objects still it
hangs).
2) If particular Process is called regressively with different Input,
Is it better to keep it as Long-lived process to avoid memory
consumption and speedup the response time.

3) If adobe process response is slow, what are all the parameters
which need to be checked in Appserver and DB level.

4) Is there any alternate way to avoid process hitting Adobe server
every time, It should generate pdf in client machine itself.

Our Application server is in WAS with DB2 backend.

Kindly revert and show some light on Adobe Output ES.
I dont know whether I have furnished all what I want to convey, Pls
ask if more information required on it.

Rajasekaran T

Raghu_Nagireddy · 1/9/13

We followed adobe blogs, documentation (links provided below) and it worked to some extent improve the things. Also its may have some differences to the needs of the projects.

1000 page in single PDF,If possible divide the 1000 into possible splits. If this is must the form design should have best performance.

http://partners.adobe.com/public/developer/en/pdf/lc_designer_perf_guidelines.pdf

Q1. As per adobe blogs it is better to have less than 50.

We have three applications (as assets count got increased split in to 3 applications, tried with one and it never worked) ranging from 30 - 60 assets in each application. When assets are only LiveCycle processes even 50 assets may not work. if it is a mix of all like processes, xdp, xsd it works for even more than 50 count.

Links for more documentation and approaches how can split the assets.

http://blogs.adobe.com/livecycle/2011/10/best-practice-for-developing-with-livecycle-workbench-es2-%...

http://blogs.adobe.com/livecycle/2011/06/best-practice-for-developing-with-livecycle-workbench-es2-%...

If the applications in between have a reference (near and far), have to be very specific while split the assets. Explained well in the above links.

Q2. Best to make as sub process and access. This also from adobe blogs and documentation of above links.

Q3. Need to see how the process designed and doc size and server performance. all these may increase the performance.

Check process configuration : Transaction properties: Supports/RequiredNew/....etc.

http://blogs.adobe.com/livecycle/2008/10/livecycle_tuning_knob_default.html - doc size issues covered here

Q4. Generate PDF is a service it should use the service on server, and cannot be avoid this call.

-Raghu.