Professional Documents
Culture Documents
Ads Prob
Ads Prob
Purpose
The purpose of this configuration information is to describe the configuration steps required to set up the Adobe document services (ADS). ADS is part of the SAP NetWeaver installation, usage type AS Java. ADS can be used in different scenarios. This guide covers all configuration steps that are required to run the ADS. Some scenarios may only need a subset of the configuration steps listed below. A detailed description of the purpose of each scenario and the corresponding system landscapes are given in the Master Guide.
Introduction
Adobe document services allow SAP applications (either Java or ABAP) to take advantage of the full range of capabilities in Adobe Acrobat Professional, Adobe Acrobat Standard, and Adobe Reader. For example, enhance the document handling capabilities of SAP NetWeaver Application Server. These capabilities enable SAP customers to: Create and deploy interactive forms that look exactly like their paper counterparts Work with forms in online and offline scenarios Annotate PDF documents and collaborate on PDF document reviews Capture data using forms and import that data directly into the SAP system Allow users to digitally sign PDF documents Embed other file formats inside PDF documents as attachments
Intended Audience
This guide describes how to configure Adobe document services. It is aimed at the system administrator and assumes familiarity with the SAP NetWeaver installation and configuration tools.
Configuration Process
The configuration description for Adobe document services covers the following configuration steps: 1. 1. 1. 2. Wizard-based configuration Manual basic configuration Optional additional configuration Configuration of Communication Security
1. Central Monitoring After you have performed the wizard-based steps, you should check the configuration settings.
ADS_AGENT
Service user
SAP_BC_FP_ICF
The ADSUser is required for the communication between the forms application and the Adobe document services. The wizard-based configuration creates this user in the AS Java or in the AS ABAP depending on the installation settings for the SAP User Management Engine (UME). In a double-stack installation ADSUser is stored the AS ABAP when the UME is configured against the AS ABAP backend. In a Java standalone installation ADSUser is stored in the AS Java. The service user ADS_AGENT in the AS ABAP is required for the communication between the Adobe document services and the AS ABAP, only when form designs (also known as form templates) are stored in the standard forms repository in AS ABAP. This is, for example, if you use PDF-based print forms.
Related Documentation
For more information on developing forms, see the SAP Library. Enabling Form-Based Processing of Business Data in
Check the newest printable version of this Configuration Guide in the SAP Service Marketplace, available at http://service.sap.com/adobe Media Library Documentation.
Procedure
...
1. Log on to your SAP NetWeaver AS ABAP central instance host. 2. Call transaction SM59. 3. Choose Create. 4. Enter at least the following: RFC destination: ADS Connection type: G Description: <your description> 5. Choose ENTER 6. Choose the Technical settings tab and enter at least the following: Target Host Enter the host name of the AS Java that runs the Adobe document services or of the SAP Web dispatcher if applicable. Service No Enter the HTTP port number of the Target Host you have specified (The following naming convention applies: 5<J2EE_instance_number>00 (50000, for example, if your J2EE instance is 00). Path Prefix Enter exactly the string /AdobeDocumentServices/Config?style=rpc
A warning is displayed: Query String Not Allowed. Ignore this warning by pressing Enter. 7. 8. 9. Choose the Logon/Security tab, select Basic Authentication. In the User and Password boxes, enter the user name ADSUser and the password. Save your settings. If you choose Test Connection, you receive an error message Returncode 404. You can ignore this message.
Procedure
...
Log on to your ABAP system. Call transaction SM59. Choose Create. Enter at least the following: RFC destination: ADS_SSL Connection type: G Description:<your description> Choose ENTER Choose the Technical settings tab and enter at least the following: Target Host Enter the host name of the Java system that runs the Adobe document services or of the SAP Web dispatcher if applicable. Service No Enter the HTTP port number of the Target Host you have specified (The following naming convention applies: 5<Java_instance_number>01 (50001, for example, if your Java instance is 00). Path Prefix Enter exactly the string /AdobeDocumentServicesSec/Config?style=rpc
A warning is displayed: Query String Not Allowed. Ignore this warning by pressing ENTER. Choose the Logon/Security tab.
In the SSL area, select SSL Client Certificate. 1. Select the certificate. 1. Select Active.
Save your settings. If you choose Test Connection, you receive an error message Returncode 404. You can ignore this message.
Procedure
...
Enter the following URL in your Web browser: http://<server>:<port> where <server> is the name of the AS Java where the Adobe document services are installed, and <port> is the port of the AS Java. Choose Web Services Navigator In the list, choose com.adobe/AdobeDocumentServces_com.adobe_AdobeDocumentServicesVi. Choose rpData. Choose Execute without entering any parameters. Enter the user name ADSUser and the password and press OK.
Result
If the configuration is correct, the system displays the version number of the Adobe document services in the response area.
You can ignore the message Required stream: "PDFDocument" not found.
If the configuration is not correct, the page does not change and Login Information remains on the screen. To further check the configuration, perform the following procedures: PDF-based forms and forms in Web Dynpro for ABAP
Creating a User in the SAP NetWeaver AS ABAP for Basic Authentication Setting Up Basic Authentication in an ABAP Environment - Creating the ABAP Connection
Prerequisites
You have already checked the ABAP connection.
1. Log on to your SAP NetWeaver AS ABAP system. 2. Call transaction SA38. 3. Enter the name of the test report FP_CHECK_DESTINATION_SERVICE. 4. Execute the test without choosing the option With Destination Service. 5. The system renders a test form in the background without using the destination service and displays the size of the created PDF. 6. Execute the test again. Now select the option With Destination Service. 7. If the settings of the destination service are correct, the system displays the same message as before (see step 5).
1. In your Web browser enter the URL http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp where <server> is the server that hosts the AS ABAP and <port> is the http port of the AS ABAP. 2. In the dialog box enter ADS_AGENT as user and the password you have specified for it. 3. If the settings of the ICF service are correct, the system displays the layout information of the form FP_TEST_00 in XML format.
1. Start the SAP NetWeaver Administrator and navigate to Destinations as described in Creating or Changing the Destination Service. 2. Choose the destination and extend the URL you specified in Destination Detail Connection and Transport to http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp
Specify the URL exactly as given, otherwise the connection cannot be tested and you receive the error message Error during Ping operation: Received HTTP response 404.
3. Choose Ping Destination 4. The system sends a call to the ABAP system where the form layout is stored. If the settings are correct, the system displays the message HTTP GET response code 200 Content type text/xml. 5. Change the URL back to http://<server>:<port> for the Destination Service to work properly.
Further Checks
If the settings of the destination service are not correct, you get an error message. You need to perform further checks:
...
1. 2. 3.
Check if the ICF service is active. Check if the system user ADS_AGENT is correctly configured. Check the settings of the Destination Service.