An assembly implementation supports the process of merging the element list, which results in complex document output as defined by the configured business rules. In some configuration scenarios, a third-party product is required to generate the required output. On the other hand, no third-party assembly server is required for XML, WordML, or DOCX files.
This decision is driven by output format requirements. If you opt for PDF, Apache FOP and Adobe LiveCycle are possible tools. If you opt for DOCX or WordML, no third-party assembly server is required.
Another criterion for the decision is whether PDF forms are attachments or are embedded. Adobe LiveCycle, DOCX, WordML, and Apache FOP do not support embedding PDF forms.
Tool |
Description |
Advantages |
Limitations |
Requirements |
Apache FOP |
Supports generation of PDF legal document from multiple HTML elements |
|
|
SAP NetWeaver or Apache Tomcat |
Adobe LiveCycle |
|
|
|
Adobe LiveCycle PDF Generator ES is a third-party tool and requires Windows XP; Adobe LiveCycle Designer is part of the SAP NetWeaver GUI installation |
Other |
Customers choose different third-party editors and create own implementations |
Customers choose their own tool to meet their requirements |
Requires time and effort to create implementation |
Depends on the implementation |
The following table lists configuration options:
Adobe Document Services (ADS) provides form design and generation capabilities and is part of SAP NetWeaver. You can generate forms, but you cannot embed forms into complex assembled documents.
Standalone PDF forms are contained in their own files compared with forms contained in an assembled document.
Embedded PDF forms are contained in an assembled document.
Microsoft Word 2003 supports WordML also.
Third-party ActiveX Control is needed only for WordML
This configuration includes Microsoft Word-based forms embedded in the assembled document.
This configuration supports embedding a PDF or Microsoft Word form.