We have a question concerning the delivery and installation
LiveCycle Data Services ES web applications.
Within an LCDS application the LCDS jar files
common.jar, …) and config files
(data-management-config.xml, …) are
needed and have to be within the same WAR(or EAR) file as
code (custom Assembler implementations and so on).
We have received the information from Adobe, that unbundling
LiveCycle Data Services is not allowed. So how to add those
and config files to your WAR(EAR) file without unbundling the
file, which is included within the LiveCycle Data Services ES
Has anybody already had this problem?
Is an approach which adds the
LCDS jar files and the adapted config files to your
(EAR) file EULA conform?
Such an approach is also described on the last page of
documentation "Chapter 2: Building and Deploying LiveCycle
Services ES Applications":
One option is to package your application and assets in a
Data Services ES web application, and then create a single
that contains the entire web application. You can then deploy
single WAR file on your production server.