Architecture for PDF-Based Forms 

 

System Landscapes for Forms in AS ABAP

The following figure displays the usage of Adobe document services in different system landscapes.

In an ABAP+Java double stack installation, basic authentication is set up automatically as the default during the initial installation of Adobe document services. 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.

 

Communication AS ABAP – Adobe Document Services

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 this 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. If you want to use SSL, you have to configure this manually. For more information, see Configuration of the Web Service SSL Connection in the Adobe Document Services Configuration Guide.