I have a simple xdp containing only text fields set to read only. A xsd data connection have been set up and the fields are bound to this. Topmost subform are set to repeat when encountering a specific elemet in the xsd.
All works fine when a limited amount of xml is sent to the adobe server. However, when I try with bigger xml files the server times out.
I have noticed that files generated by Adobe LC is generally much bigger than whats generated in a product like Jasper reports. I've tried setting up a similar report in Jasper an after about 3 minutes it returnes with a generated pdf file containg about 700 pdf pages (Adobe LC timed out presented with the same xml-file)
Sending just a small snippet of the xml to Adobe LC Server and Jasper yielded following results:
PDF-size from LC Server: 1MB
PDF-size from Jasper: 150KB
There is no difference in the visual appearance of the pdf files.
(The 700 pages pdf from Jasper reports had just a size of 1MB.)
My questions are:
1. Is there a way to reduce the pdf file size generated by Adobe LC server? (Using a service or somehow?)
2. Can I tweak anything on the server or else where that would make the big-xml job complete without timeout?
In the Designer template you can have a look at the Save options in the Form Properties Under the File menu. By deafult, there is font embedding and Generate accessibility tags set on. Turn these off and you should be getting a PDF of similar size.
These options are already turned off. Further more it says on the tab: "These options aply only when saving form designs as PDF files. They do not apply to pdf files rendered using LiveCycle Forms ES."
Speaking of fonts, I am using Times New Roman, which as I understand already should be included in adobe reader (No embedding should therefore occur).
Here is a bit more about my setup:
I am using the following services: renderPDFForm and AssembleService (for flattening the document).
I have tried optimizing the xdp in every possible way. Setting read only on text fields, setting a max length on text fields, using only few subforms etc. Still I find the rendered pdf to be quite big, compared to the contents and what Jasper report generates (from the same xml).
With regards to the xml feeding. Is it possible that the served xml file is to big for the Adobe Server to handle?
I can easily send you an archive containing the processes, xdp, xsd and sample xml file, if you would like that. Maybe you can spot something which could be optmized.
I'm quite positive that its due to the size of the generated pdf form.
I'm starting to think Adobe LC may not be the answer in situations where large amounts of xml data is used to populate forms, unless something can be done to somehow reduce the size of the pdf being generated.
I do not think it is a timeout ...I think your data file is too big and you are running out of heap space hence causing the timeout. Even when I bumped up the timeout values it dod not make a difference. When I ran your form and data using output (with a parameter that loaded the data in chuncks) it completed in the 30 sec timeframe. The difference between the two products is the way that data is loaded.