What are the technical implications of the migration to LiveCycle Output ES?
Document templates need to be converted and new methods are needed to integrate into enterprise systems. LiveCycle Output ES accepts only XML data input, for instance. A template conversion tool is included that converts templates created in Output Designer to LiveCycle Designer ES. Templates created using the standard Output Designer tools typically convert easily and accurately. If you modified the preamble to customize your implementation, however, you will need to rework these aspects manually. Similarly, integration points previously handled by the Job Management Database will need to be migrated to the LiveCycle J2EE environment.