The figures below give you an overview of the architecture of SAP Interactive Forms by Adobe.
The following figure displays the usage of Adobe document services in different system landscapes, for example for creating PDF-based print forms.
You can run the wizard-based configuration in an ABAP+Java double stack installation. If AS ABAP and AS Java are not installed on the same server, you must perform the configuration steps manually.
You also have to perform the configuration steps manually, if you added AS Java to an existing AS ABAP system (Java Add-in).
Adobe LiveCycle™ Designer is installed locally on the developer’s PC and integrated into the ABAP Workbench. You install LiveCycle Designer from the separate CD/DVD delivered by SAP.
In the graphic below you can see the communication paths between the components used in the SAP NetWeaver Application Server.
The Form Processing Runtime sends the application data of the form and a link to the form design (template of the form) to the Adobe document services using SOAP, through the RFC destination (SM59). The user for the access is ADSUser.
Before processing the form and creating a PDF or PCL file, the Adobe document services calls the form design, which is stored in the Form Design Repository. Thus the Destination Service communicates with the Internet Communication Framework (ICF). The user for the access is ADS_AGENT.
The protocol for both communication paths is HTTP using the default HTTP port. In the case of SSL, it is HTTPS, respectively HTTPS-Port.
The following figure displays the usage of Adobe document services in different system landscapes.
The user ADSUser is required for the communication between the forms application, for example in Web Dynpro for Java and the Adobe document services. When ADS and Web Dynpro are both installed on the same system you can run the wizard-based configuration. When ADS and Web Dynpro run on separate systems you need to set up the communication manually.