You are on page 1of 17

Configuring Adobe Document Services for Form Processing

(ABAP)
PDF download from SAP Help Portal:
http://help.sap.com/saphelp_nw74/helpdata/en/3a/62c0dbf6da426790ecf3186b37f512/content.htm

Created on June 13, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Table of content
1 Configuring Adobe Document Services for Form Processing (ABAP)
1.1 Performing Basic ADS Configuration in an ABAP Environment
1.1.1 Creating a User for Authentication to ADS in an ABAP Environment
1.1.2 Setting Up Basic Authentication to ADS in an ABAP Environment
1.1.3 Creating the Service User for Communication with ADS
1.1.4 Creating the Destination Service for Communication with ADS
1.1.5 Activating the ICF Service
1.1.6 Applying a Reader Rights Credential to PDF Forms
1.2 Adapting ADS Configuration in an ABAP Environment
1.2.1 Installing Trusted Anchors and Certificate Revocation Lists
1.2.2 Configuring Parallelization for Large Print Jobs
1.2.2.1 Configuring the Logical Port for Using Parallelization
1.2.2.2 Configuring the RFC Destination for Using Parallelization
1.2.2.3 Monitoring Report for Parallelized Print Jobs
1.2.3 Configuring the System for Large Form Generation by Stitching
1.2.4 Mapping Fonts
1.3 Configuring the SSL Connection to ADS in an ABAP Environment
1.3.1 Changing the existing ABAP connection for SSL
1.3.2 Creating a new ABAP connection for SSL
1.4 Checking ADS Configuration in an ABAP Environment
1.4.1 Checking the ABAP Connection to ADS
1.4.2 Checking the User and Password (ABAP)
1.4.3 Checking the Destination Service and the ICF Service
1.5 Monitoring Adobe Document Services (ADS)
1.5.1 Monitoring the License Status of Form Layouts
1.6 Analyzing ADS Errors in an ABAP Environment
1.6.1 Information on ADS Errors Contained in a Returned PDF File

PUBLIC Page 2 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
1 Configuring Adobe Document Services for Form Processing
(ABAP)

Use
Adobe Document Services (ADS) are an SAP NetWeaver solution extension included in the SAP NetWeaver usage type Application Server (AS) Java. To
process forms in an ABAP environment , the ABAP transaction dynpros or Web Dynpro ABAP applications call the ADS. The generation of forms is based on
form templates designed with Adobe LiveCycle Designer and business data provided by the applications.
Once installed on the AS Java, the ADS need to be configured in order to be available for form processing.
Communication Between AS ABAP and ADS
The ADS can run either on the same server as the ABAP applications or on a separate server. The ADS can also be installed on the AS Java as a central
component - an ADS hub - which can operate with different ABAP systems. The graphic below shows the communication paths between the components on the
AS ABAP and the ADS installed on the AS Java.

The form processing framework (ABAP) sends the runtime data (business data provided by an application and a link to the form template) to the ADS by using
the RFC destination. The system user ADSUser is required to access the ADS.

Before processing the form and creating a PDF or PCL file, the ADS call the form template. To establish the required connection to the AS ABAP where the form
template is stored, the destination service used by the ADS communicates with an Internet Communication Framework (ICF) service. The service user required to
access the template repository is ADS_AGENT.

If forms bundling is used, two separate ICF services are used to retrieve the form template and the business data and to return the result.
The protocol for the communication paths is HTTP, using the default HTTP port. For SSL, the protocol is HTTPS or HTTPS-Port.

Prerequisites
The AS Java where the ADS are running should have at least the same release as the AS ABAP.

Caution
The following functions for PDF forms require at least the ADS version on AS Java 7.20:
Parallelization of large print jobs
Stitching of PDF forms

Procedure
1. Perform the basic ADS configuration automatically (using the configuration tool) or change the settings manually.
More information: Performing Basic ADS Configuration
2. Perform optional ADS configuration steps to adapt specific settings as needed.
More information: Adapting ADS Configuration in an ABAP Environment
3. Configure the ADS settings for communication security .
More information: Configuring the SSL Connection to the ADS in an ABAP Environment
4. Use the monitoring functions to check the status of configuration tasks.
More information: Monitoring Adobe Document Services Configuration
5. Make sure that all the ADS-relevant services are running.

PUBLIC Page 3 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
More information: Starting or Stopping an ADS-Relevant Service
6. In the event of ADS connection errors, analyze and resolve the respective errors.
More information: Analyzing ADS Errors in an ABAP Environment
Relevant SAP Notes

SAP Note Number SAP Note Title

736902 Adobe Credentials

750784 Adobe document services: Licenses

752153 PDF Manipulation Module High Encryption

766410 Interactive Forms: XDC-Scenarios

685571 Information about printing PDF based Forms

834573 SAP Interactive Forms by Adobe: Acrobat/Reader version

More Information
Enabling Form-Based Processing of Business Data (form template creation and forms generation in an ABAP environment)

1.1 Performing Basic ADS Configuration in an ABAP Environment

Use
You can perform the basic configuration of Adobe Document Services ( ADS ) automatically using the configuration tool. To adapt specific configuration
settings or in case the automatic configuration failed, you can perform each configuration step manually .

Procedure
1. If no ADS configuration steps have been performed yet after installation, perform the basic ADS configuration automatically
1. Call the functional unit configuration tool.
More information: Java Functional Unit Configuration
2. In the list of functional units, choose Adobe Document Services .
3. Choose Enable Manually .
4. Check the status of the ADS configuration and, if necessary, perform the respective steps manually.
More information: Checking ADS Configuration in an ABAP Environment
2. To change or correct specific settings, perform the basic ADS configuration manually
Create the system user required for the secure communication between the Forms Processing Framework ABAP and the ADS running on an AS Java.
More information: Creating a User for Authentication to ADS in an ABAP Environment
Create a connection from the ABAP environment to the ADS.
More information: Setting Up Basic Authentication to ADS in an ABAP Environment
If form templates are stored in the standard forms repository on the AS ABAP, create the service user required for the communication between the ADS and
the AS ABAP (via the Internet Communication Framework ICF).
More information: Creating the Service User for Communication with ADS
Create or adapt the Destination service (in the AS Java), that facilitates communication and data transmission between the ADS and the ABAP
environment.
More information: Creating the Destination Service for Communication with ADS
Make sure that the Internet Communication Framework (ICF) service needed for the communication between the Destination service (on the AS Java) and
the AS ABAP, is avctivated.
More information: Activating the ICF Service
3. For interactive use and security of PDF forms, apply a Reader Rights Credential
To make advanced usage rights - like filling in interactive PDF forms and saving them, adding comments to forms or signing forms - available to users of the free
Adobe Reader software, apply a company-specific Reader Rights Credential to forms.
More information: Applying a Reader Rights Credential to PDF Forms

1.1.1 Creating a User for Authentication to ADS in an ABAP


Environment

Use
The secure communication between the Forms Processing Framework (ABAP) and the Adobe Document Services (ADS) running on AS Java, requires the
system user ADSuser with a special UME role delivered by SAP. If the user has not been created automatically by the configuration tool, you can create it
manually.

Procedure
Creating the User ADSUser
1. On the AS ABAP, log on to the client used for the UME authentication.
2. Start the transaction SU01 or choose Tools Administration User Maintenance User .
3. Enter ADSuser as user name and choose Create .

PUBLIC Page 4 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
4. Choose the user type system user .
5. Enter a password and save your settings.
Creating the Role ADSCALLERS
1. Start the transaction PFCG or choose Tools Administration User Maintenance Role Administration Roles .
2. Create a role ADSCALLERS (no authorizations required).

Note
The ADSCALLERS role in SAP NetWeaver AS ABAP appears automatically as the ADSCALLERS group in the NetWeaver Administrator.

3. Activate the role.


4. Assign the user ADSUser to this role.
Assigning UME Role and Actions to the ADSUser
1. To start the User Management, enter the Web address http://<server>:<port>/useradmin .
2. Choose Role and search the role named SAP_ADSCALLER .

Note
This UME role was created during installation.

3. Go to the Assigned Users tab. Under Available Users , search for the user ADSUSER and press Add to assign this user to the role SAP_ADSCALLER.
4. Save your changes.

1.1.2 Setting Up Basic Authentication to ADS in an ABAP


Environment

Context
If forms processing is triggered by ABAP-based applications, you need to establish a connection between the Forms Processing Framework (ABAP) and the
ADS running on AS Java. You also need to set up Basic Authentication for this connection .

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
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 ADS 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 (5
00 00, for example, if your J2EE instance is 00 ).
Path Prefix
Enter the string /AdobeDocumentServices/Config?style=rpc .
Ignore the warning Query String Not Allowed by pressing Enter .
7. Choose the Logon/Security tab and select Basic Authentication .
8. In the User and Password boxes, enter the user name ADSUser and the password.
9. Save.

Note
If you choose Test Connection , you receive an error message ...Returncode 404... . You can ignore this message.

1.1.3 Creating the Service User for Communication with ADS

Context
For the communication between the AS ABAP and the ADS running on AS Java the service user ADS_AGENT is required.
You need to specify this service user in the authentication parameters of the Destination service in the AS Java that hosts the Adobe Document Services (ADS).

PUBLIC Page 5 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Procedure
1. Log on to the AS ABAP and start the transaction SU01 (User Management).

Note
You must specify this client in the Destination service.

2. In the User field, enter ADS_AGENT and choose User Create .


3. Choose the Logon data tab and assign a password.

Note
You must specify this password in the Destination service.

4. Choose the user type Service .


5. Choose the Role tab and assign a role to the user ADS_AGENT as follows:
If AS ABAP and AS Java (with ADS) are installed on the same server (double-stack installation or AS ABAP with Java hub), assign the role
SAP_BC_FP_ICF.
.
If AS ABAP and AS Java (with ADS) are installed on different servers, assign the role SAP_BC_FPADS_ICF.

Note
This distinction is for performance reasons. You may copy the required role first.
More information: Changing Standard Roles in the SAP Library

6. Save.
7. Create the Destination service or adapt an existing one.
More information: Creating or Changing the Destination Service

1.1.4 Creating the Destination Service for Communication with


ADS

Prerequisites
The ICF service on the AS ABAP is active.
More information: Activating the ICF Service
The service user ADS_AGENT exists and is assigned to the appropriate role.
More information: Creating the User ADS_AGENT

Context
This procedure applies to forms processing in an ABAP environment. The Destination service runs on the AS Java, where the Adobe Document Services (ADS)
are installed and serves to facilitate communication and data transmission between the ABAP and the Java environment. The communication between the
Destination service and the AS ABAP is enabled by the Internet Communication Framework (ICF).
In a double-stack system (ABAP and Java installed on the same system), the Destination service is configured for basic authentication, when you execute the
configuration tool. You need to change or create these settings in the following cases:
AS ABAP and AS Java are installed on separate servers.
You want to use SSL.
The service user ADS_AGENT in the AS ABAP is not in the default client.

Procedure

1. Start the SAP NetWeaver Administrator via the address http://<server>:<port>/nwa .


2. Choose Configuration Management Security Management Destinations .
3. Choose Create .
4. Enter the Destination name FP_ICF_DATA_<SID> , where <SID> is your ABAP system, and choose HTTP for the Destination Type. Press Next .
5. Under Connection , enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in the URL field:
http://<hostname>:<HTTP_port>
and in case of SSL,
https://<hostname>:<HTTPS_port>

Note
To display the host name of your AS ABAP, log on to AS ABAP and call transaction SICF. In the main menu, choose Goto Port Information .
The information is displayed on a screen; where the HTTP_port is specified under Services .

6. Enter the appropriate client number of the system, where the service user ADS_AGENT exists into the Client field. Keep the fields SystemID and
Language empty.
7. Under SSL Server Certificates , choose Ignore server certificates and press Next .

PUBLIC Page 6 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
8. Under Logon Data Authentication, choose Basic .
9. In the Username field, enter ADS_AGENT , and enter the same password as given for this user in the AS ABAP in the Password field.
10. Choose Finish .
11. Check the settings of the Destination service.
More information: Checking the Destination Service and the ICF Service .

1.1.5 Activating the ICF Service

Context
The communication between the Destination service of the AS Java and the AS ABAP uses the Internet Communication Framework (ICF). If the ICF service has
not been activated automatically by the configuration tool, you can activate it manually.

Procedure

1. Log on to the AS ABAP.


2. Start the transaction SICF.
3. Choose default_host sap bc fp .
4. Choose Service/Virt.Host Activate .
5. If AS ABAP and AS Java (with ADS) are installed in different servers and you want to bundle your forms to improve performance, also activate the fpads
ICF service.

1.1.6 Applying a Reader Rights Credential to PDF Forms

Context
Specific tasks like filling in interactive PDF forms and saving them, adding comments to forms or signing forms, require the licenced Adobe software Acrobat
Standard or Acrobat Professional . The Adobe Reader software available for free to all users, only allows viewing of PDF forms. To make the advanced usage
rights mentioned above available to Adobe Reader users, you can apply a Reader Rights Credential to forms. Such a credential is unique to each company.

Note
The Reader Rights Credential adds usage rights to PDF forms, but it does not certify or sign them. Therefore recipients do not need a public key to validate the
forms.

Procedure
1. Obtain the Reader Rights Credential - a PKCS #12 (.pfx) file.
More information: SAP Note 736902
2. Install the Reader Rights Credential.
More information: Installing a PKCS #12 Credential
3. Configure the Reader Rights Credential.
More information: Configuring Credential Attributes
4. Optional: To see in the server log, whether the credential is about to expire, configure the credential expiry logging.
More information: Configuring Credential Expiry Logging

1.2 Adapting ADS Configuration in an ABAP Environment

Context
After having performed the basic configuration of Adobe Document Services (ADS), you can adapt specific settings optionally.

Procedure
If you require additional document security such as certification or digital signatures, you can obtain credentials from a Certificate Authority (CA) and install
them the same way you installed the Reader Rights certificate.
More information: Installing and Configuring Credentials
In case of mass printing of PDF forms in an ABAP environment, you can reduce the runtime of a print job by parallelizing Adobe Document Services
(ADS) requests.
More information: Configuring Parallization for Large Print Jobs
To generate large PDF forms, make sure that the Destination service is connected to the server where the print jobs are running and bundle the forms for
being stitched together by the ADS.
More information: Generating Large PDF Forms by Stitching their Parts
To make fonts obtained from third-party vendors available for the Adobe Document Services, copy them to a special subdirectory of the Font Manager.
More information: Adding Fonts

PUBLIC Page 7 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
To make sure, that language versions are always displayed in an appropriate font, that can show all the characters, specify the mapping between the
source font and the required language version font.
More information: Mapping Fonts
If the features implemented in your PDF forms require a higher PDF version than the default one, specify the PDF version in which forms are to be
rendered.
More information: Changing the Default PDF Version
In case of specific printing workflows, adapt your printer or print job settings accordingly.
More information: Managing XDC Files and Job Profiles
To obtain the optimal information for analyzing form rendering errors, adapt the layout of the ERROR.PDF file according to your requirements.
More information: Changing the Design of the ERROR.PDF File
To make sure that the directory, in which the system stores ADS error files, does not overflow, define a maximum storage size. In order not to exceed the
maximum storage size, the system will delete the eldest error files in favor of new ones. Changing the Maximum Size for the Storage of the ERROR.PDF
File
To increase the overall performance of the Adobe Document Services, enable parallel processing on several processors.
More information: Configuring Multi-Processing

1.2.1 Installing Trusted Anchors and Certificate Revocation Lists

Context
If you are using Certification and Digital Signatures credentials you will also need to install and configure the following elements in Adobe Document Services
(ADS):
Trusted Anchors
Trusted Anchors enable the server to verify the certification or signature of a form. They may be Certification authority (CA) certificates or individual user's
certificates. There are two cases:
You need a Trusted Anchor - an additional certificate containing the CA's public key - to provide it to anyone, to whom you will send forms certified or
signed using the corresponding private key (saved within your system). (A credential received from a CA contains a private and a public key.)
You need a Trusted Anchor in order to trust signatures or certifications that other people applied to documents using their own credentials.
Certificate Revocation Lists (CRLs)
CRLs identify credentials that can no longer be trusted. CRLs also prevent you from applying a digital signature that is no longer valid, and it lets you know
when digital signatures on incoming documents are invalid.
CRLs should be updated on a regular basis (for example, daily or weekly).

Procedure
1. In case your PDF forms are certified or signed by the server or submitted by users, install the corresponding Trusted Anchor to enable the server to verify
the certification or signature of a form.
More information: Installing Trusted Anchors
2. To identify credentials that can no longer be trusted or to avoid applying a digital signature that is no longer valid, install Certificate Revocation List files
(CRLs).
More information: Installing Certificate Revocation Lists

1.2.2 Configuring Parallelization for Large Print Jobs

Use
In case of mass printing of PDF forms in an ABAP environment, you can reduce the runtime of a print job by parallelizing Adobe Document Services (ADS)
requests. Parallelization must be explicitly activated through optional API parameters and configuration steps (both by the administrator and the developer).

Prerequisites
Parallization of print jobs requires Adobe Document Services (ADS) installed on AS Java 7.20 or higher.

Procedure
Configuring parallelization
1. To enable an application to parallelize ADS requests, in the functional unit FP_JOB_OPEN, set the optional parameter IE_OUTPUTPARAMS FIELD to
'PARALLEL'.
2. In the SOA Manager, configure the logical port for the Web services relevant for parallelization.
More information: Configuring the Logical Port for Using Parallelization
3. For the RFC destination ADS in the database table FPCONNECT, set the logical port of the Web services.
More information: Configuring the RFC Destination for Using Parallelization
Monitoring parallelized print jobs
As large print jobs are normally running several hours, you can monitor the current status of the print jobs.
More information:
Monitoring Report for Parallelized Print Jobs

1.2.2.1 Configuring the Logical Port for Using Parallelization


PUBLIC Page 8 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Use
Parallelization of ADS requests must be explicitly activated through optional API parameter and configuration steps. Parallelization will not be activated
automatically via an upgrade. This will ensure compatibility to existing customer implementations.
You (the administrator) have to configure the logical port for the following Web Services in the SOA Manager:
FpPrintRequest (WebService for ADS Parallelization)
FpQueueAdmin (WebService for the Monitoring UI)

Activities
To configure the logical port for the Web Services you have to perform the following steps:
1. Call the transaction SOAMANAGER .
2. Navigate to Service Configuration.
3. Select Single Service Administration.
4. Select Consumer Proxy in the field Search By.
5. Enter FpPrintRequest in the field Search Pattern.
6. Press the button Go.
7. The WebService FpPrintRequest will be displayed in the Search Result List.
8. Select the WebService FpPrintRequest and press button Apply Selection.
9. Select the tab Configuration in the Details of Proxy Definition CO_FP_PRINT_REQUEST area.
10. Press the button Create Logical Port.
11. In the Creation Dialog enter the Logical Port Name for the Web Service.
12. Enter the URL for WSDL Access: http://<host>:<port>/FpPrintRequestService/FpPrintRequest?wsdl&mode=ws_policy
<host> - Hostname of the J2EE Engine where the ADS is running
<port> - Port of the J2EE Engine where the ADS is running
13. Press the button Apply Settings.
14. Select the tab Consumer Security and enter user Name and Password for the ADS service user.
15. Press the save button.
Repeat all steps for the Web Service FpQueueAdmin.

Caution
The logical port names of both Web Services must be identical!

1.2.2.2 Configuring the RFC Destination for Using Parallelization

Use

Activities
You (the administrator) have to set in the database table FPCONNECT for the RFC destination ADS the logical port for the web services.
To configure the the RFC Destination you have to perform the following steps:
1. Start Transaction SM30.
2. In the field Table/View enter the database table name FPCONNECT .
3. Press the button Maintain.
4. Select the RFC Destination 'ADS' and scroll to the column header Logical PortName .
5. Enter the name of the logical port of your configured Webservices.
6. Press the button save .
The System must be configured for Bundling of Forms

1.2.2.3 Monitoring Report for Parallelized Print Jobs

Use
Monitoring Report
The monitoring report provides you detailed information which parallelized print jobs are currently running. The monitoring report provides you also the possibility to
stop running or delete finished print jobs.
The permission handling is related to the spool permissions (the user will see in the monitoring UI dependent on the spool permissions only his parallelized print
jobs or all parallelized print jobs).
You can start the monitoring report with the transaction SA38 FP_MONITOR_PARALLEL_PROCESSING
Three hierarchical levels provide you the information on different levels of granularity:
Monitoring report - job view
Monitoring report - request view
Monitoring report - request details view
Monitoring Report - Job View
With the view Job Level you see a list of parameters for each print job. If you select the parameter Job-ID you will see the next detail level ( Request

PUBLIC Page 9 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
View ). For successful jobs no detail information is available. You can stop running jobs by selecting the stop icon in the Action column. You can remove
finished jobs by selecting the delete icon in the column Action
Monitoring Report - Request View
With the Request View you see details of each of the requests of the selected print job. If you select the Request Id you will see the next detail level (
View Request Details )
Monitoring Report - Request Details View
With the Request Details View you see all requests parameters passed to the Adobe Document Services and the complete response. If you select the
parameter TraceString you see the whole trace of the Adobe Document Services. If you select the parameter Error.pdf you download the PDF with
additional information to the local front end.
The Error.pdf is only available, if an error has occurred in the Adobe Document Services.

1.2.3 Configuring the System for Large Form Generation by


Stitching

Prerequisites
The Adobe Document Services are installed on AS Java 7.20 or higher.
The ADS version is 8.20... or higher (for example 820.2009x).
Form bundling is enabled.

Context
In special cases, business applications require the creation of large PDF forms containing more than 1.000 (up to 20.000) pages, for example printing of the
General Ledger. Depending on the operating system, Adobe Document Services (ADS) have a technical limitation regarding the form size.
When creating large documents using ADS there are limitations with regard to the maximum number of pages (see SAP Notes 1009567 and 894389 ).
To be able to create large PDF documents, you need to implement an application-side workaround.
Workaround: Stitching bundled forms to one PDF form
The creation of large forms can be achieved through a workaround: Applications split large forms into smaller ones and bundle them, so that the Forms Processing
Framework can invoke the ADS with a bundle of forms. The ADS render the single forms from the bundle and stitch them together to one large PDF file.
To avoid timeouts when generating large forms, you need to set up the system to allow a long processing time .

Procedure
1. On the AS ABAP, in transaction SM59, create a special ADS connection with an increased timeout.
2. On the AS Java, increase the timeout of the Internet Communication Manager(ICM) in the profile icm/server_port_0 = PROT=HTTP,
PORT=5$(SAPSYSTEM)00, TIMEOUT=<seconds>.
3. On the AS ABAP, adjust the profile parameter icm/HTTP/max_request_size_KB to enable the transfer of a huge amount of data.

Results
The system now supports the generation of large PDF forms "stitched" together from several smaller forms. To enable stitching in the application program , do
the following:
When calling the function module FP_JOB_OPEN, set the parameter ASSEMBLE to the value 'S'.
For more information, see Form Interface Parameters of the Application .
Select the output mode Print and (or) Archive or PDF return .
The ADS are called when the application closes the job (function module FP_JOB_OPEN). The ADS provides the final "stitched" form according to the scenario:
The PDF file is retrieved by the application or handed over to the ArchiveLink.
Restrictions
It is not possible to assemble single PDF documents via this interface.

Example
Test report FP_CHECK_BATCH_PDF_RETURN in the ABAP system

Note
In the test program, you have the following options:
You can choose to have all forms bundled in a single PDF.
If you have chosen to have all forms bundled in a single PDF, you can also choose the stitching for large PDFs. This option is available only if the ADS
support it.

1.2.4 Mapping Fonts

Use
Font mapping defines which fonts are used in a form if a specified font is not available. That is, you can specify which font to substitute for an unavailable font.

PUBLIC Page 10 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Font mapping information on the server is specified within XML tags in the custom_xfa.xci file. You must specify the font mapping for whichever destination it
applies to (for example, PDF, PCL, PostScript, or Zebra).
Example: Font mapping tags located in an XCI file
This sample code shows font mapping tags located in an XCI file.
<map>
<!-- [0..n] Attributes: from='', to='' [0..n] -->

<equate from="Courier_*_*" to="Courier New_*_*" force="0" />

<equate from="CourierNew_*_*" to="Courier New_*_*" force="0" />

<equate from="Courier-New_*_*" to="Courier New_*_*" force="0" />


<equate from="MyriadPro_*_*" to="Myriad Pro_*_*" force="0" />

The map element contains font mapping information. Each font map is defined within an equate tag. The XML syntax for a font map is as follows:
<equate from="[ ]" to="[ original font_weight_posture ]"/> substitute font_weight_posture

The font information for the original font and substitute font is defined as follows:
<Fontname_weight_posture>
Fontname is the name of the font as it appears in the font list in LiveCycle Designer, weight determines whether the font is bold. Valid values are bold, normal,
or * (wildcard), posture determines whether the font is italic. Valid values are italic, normal, or * (wildcard).

Procedure
To map fonts on the server:
1. Navigate to the /<DIR_GLOBAL>/AdobeDocumentServices/lib directory.
2. Map the fonts in the custom_xfa.xci file.
If the custom_xfa.xci file does not exist, copy the xfa.xci file and rename it to custom_xfa.xci.

Example
The following XML code shows an example of an XCI file that contains font mapping information.
<zpl>

<fontInfo>
<defaultTypeface writingScript="Roman">CG Triumvirate</defaultTypeface>

<defaultTypeface writingScript="Japanese">Kozuka Mincho Pro-VI R</defaultTypeface>

<defaultTypeface writingScript="SimplifiedChinese">Adobe Song Std L</defaultTypeface>

<defaultTypeface writingScript="TraditionalChinese">Adobe Ming Std L</defaultTypeface>


<defaultTypeface writingScript="Korean">Adobe Myungjo Std M</defaultTypeface>

<map>

<equate from='MS Gothic_*_*' to='Kozuka Gothic Pro M_*_*' force="1"/>


</map>

</fontInfo>

</zpl>

1.3 Configuring the SSL Connection to ADS in an ABAP


Environment

Context
The automatic configuration of Adobe Document Services (ADS) covers basic authentication. If you want to use security-related functions such as digital
signatures for PDF forms created in an ABAP environment, you must set up an SSL connection for the secure communication with the ADS Web service
(running on the AS Java).

Procedure
1. Set up SSL on the AS ABAP.
More information: Configuring the AS ABAP for Supporting SSL (in the SAP Library)
2. Set up SSL on the AS Java.
More information: Configuring the Use of SSL on the AS Java (in the SAP Library)
3. To set up the SSL connection between the ABAP environment and the ADS, proceed as follows:
1. Import the client certificates into the AS Java (where the ADS are installed) and configure them.
More information: Configuring the Use of Client Certificates for Authentication (in the SAP Library)
2. To enable a secure communication with the ADS, change the settings of the system user ADSUser (created within basic ADS configuration) from
basic authentication to SSL.
More information: Maintaining the User's Certificate Information (in the SAP Library)
3. To provide an SSL connection to the ADS, choose one of the following possibilities:

PUBLIC Page 11 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
To provide an SSL connection to the ADS used by the system only in case of security-relevant runtime activities, like applying and verifying
digital signatures, create a new SSL connection. The targeted use of SSL has a positive impact on the system performance.
Note that the user ADSUser must have an own password.
More information: Creating a new ABAP connection for SSL
To provide an SSL connection to the ADS used by the system during all runtime activities, adapt an existing SSL connection.
More information: Changing the existing ABAP connection for SSL

1.3.1 Changing the existing ABAP connection for SSL

Prerequisites
The ABAP connection ADS already exists. If the ABAP Connection that uses Basic Authentication to the Adobe document services does not yet exist, see
Setting Up Basic Authentication - Creating the ABAP Connection .

Context
The purpose of this procedure is to create a connection in the ABAP environment to use when connecting to Adobe document services and to set up to SSL.

Procedure

1. Log on to your ABAP system and go to transaction SM59.


2. In the RFC Destinations tree, select HTTP Connections to Ext. Server .
3. Select ADS , then choose Change .
4. Choose the Technical settings tab and change specified port number in the field Service No to HTTPS port. (The following naming convention applies:
5<Java_instance_number>01 (5 00 01, for example, if your Java instance is 00).
5. Choose the Logon/Security tab.
In the SSL area, select SSL Client Certificate .
Select the certificate.
Select Active .
6. On the Technical Settings tab, in the PathPrefix box, enter exactly the string /AdobeDocumentServicesSec/Config?style=rpc

Note
A warning is displayed: Query String Not Allowed . Ignore this warning by pressing Enter .

7. Choose Save .

Note
If you choose Test Connection , you receive an error message ... Returncode 404 ....

You can ignore this message.

1.3.2 Creating a new ABAP connection for SSL

Context
The purpose of this procedure is to create a connection in the ABAP environment to use when connecting to Adobe document services and to set up SSL.

Procedure

1. Log on to your ABAP system.


2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination : ADS _SSL
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 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<J ava _in stance_number>01 (5 00
01, for example, if your Java instance is 00 ).
Path Prefix
Enter exactly the string /AdobeDocumentServicesSec/Config?style=rpc

PUBLIC Page 12 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Enter exactly the string /AdobeDocumentServicesSec/Config?style=rpc

Note
A warning is displayed: Query String Not Allowed. Ignore this warning by pressing ENTER .

7. Choose the Logon/Security tab.


In the SSL area, select SSL Client Certificate .
Select the certificate.
Select Active .
8. Save your settings.

Note
If you choose Test Connection , you receive an error message ... Returncode 404....

You can ignore this message.

1.4 Checking ADS Configuration in an ABAP Environment

Use
In specific cases, the configuration tool might not be able to perform all the basic ADS configuration steps. Use the test program to make sure that the
configuration steps are complete and to verify, which ones you need to perform manually.

Prerequisites
An output device for printing PDF-based forms is configured.
More information: SAP Printing Guide (BC-CCM-PRN)

Procedure
1. Use the ADS configuration test program
1. Log on to the AS ABAP system.
2. Start the transaction SA38.
3. Enter the program name FP_TEST_00 .
4. Choose Program Execute (F8) .
5. Make sure, that the following default values are entered in the respective fields:
Form: FP_TEST_00
ADS Connection: ADS or the RFC Destination name specified in your system (if it does not correspond to the default entry)
6. Choose Program Execute (F8) .
7. Enter the Output Device .
8. Choose Print Preview .
9. If the system displays a form containing several lines on two pages, the ADS configuration is correct. Otherwise, perform the tests described below.
2. In case the ADS configuration is not correct, perform the following test manually:
Check the RFC Destination needed to establish the connection between the Forms Processing Framework on the AS ABAP and the ADS on the AS Java.
More information: Checking the ABAP Connection to ADS
Check whether the user, the security role and passwords are correct and basic authentication is possible.
More information: Checking the User and the Password
Check the settings of the destination service.
More information: Checking the Destination Service

More Information
SAP note 944221 (Trobleshooting)

1.4.1 Checking the ABAP Connection to ADS

Context
This is a test for checking the RFC destination used to establish a connection between the ABAP environment and the ADS for form processing.
This test applies to both the connections using Basic Authentication and SSL connections.

Procedure

1. Log on to your SAP system.


2. Start the transaction SA38.
3. Enter the name of the test report FP_PDF_TEST_00 .

PUBLIC Page 13 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
4. Enter the name of the connection. Enter the default name ADS , or, if you have specified another name, the one you are using in your system.
5. Choose Execute (F8) .

Results
If the configuration is correct, the system displays the version number of the Adobe Document Services.
If the configuration is not correct, the system displays a corresponding message. Check the respective configuration.
More information:
Setting Up Basic Authentication to ADS in an ABAP Environment
Configuring the SSL Connection to ADS in an ABAP Environment

1.4.2 Checking the User and Password (ABAP)

Context
If forms processing is performed in an ABAP environment , you can test whether the entries for user, security role, and passwords needed for Basic
Authentication are correct.

Procedure

1. In your Internet browser, enter the Web address http://<server>:<port>


<server> : name of the AS Java where the Adobe Document Services (ADS) are installed
<port> : port of the AS Java
2. Enter the WS Navigator user and password.
3. As Search Type , select Provider System .
4. Search for * adobe *.
5. In the list, choose AdobeDocumentServicesVi .
6. Choose Next .
7. Choose rpData .
8. Choose Next .
The parameters are displayed.
9. Choose Next without entering any parameters.
10. Enter the user name ADSUser and the respective password and choose OK .

Results
If the configuration is correct, the system displays the version number of the Adobe Document Services in the response area.

Note
Ignore the message Required stream: "PDFDocument" not found.

If the configuration is not correct, the page does not change ( Login Information remains on the screen). Check the configuration as described in the following
procedures:
Creating a User for Authentication to ADS in an ABAP Environment
Setting Up Basic Authentication to ADS in an ABAP Environment

1.4.3 Checking the Destination Service and the ICF Service

Use
Use the first of the following tests for checking the settings of the destination service. If you receive any error messages, continue with the further tests listed below.

Prerequisites
You have already checked the ABAP connection .
Checking the Destination Service using a test report in AS ABAP
Using this test you can check if the complete configuration of the destination service and the ICF service is correct.
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).

PUBLIC Page 14 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Checking the ICF Service using the Web Browser
1. In your Web browser enter the URL
http://<server>:<po rt>/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.
Checking the Destination Service using the SAP NetWeaver Administrator
Using this test you can check if the settings for the destination service are correct.
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

Caution
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. Check if the ICF service is active.
2. Check if the system user ADS_AGENT is correctly configured.
3. Check the settings of the Destination Service .

Procedure

1.5 Monitoring Adobe Document Services (ADS)

Context
You can monitor the Adobe Document Services and perform specific administrative tasks.

Procedure
Monitoring the License Status
Monitoring the Adobe Document Services EJB
Viewing the Logs
Activating the Trace for Adobe Document Services

Next Steps
Starting or Stopping an ADS-relevant Service

1.5.1 Monitoring the License Status of Form Layouts

Use
Use this function for viewing the license status of your form designs in your SAP system. The license for SAP Interactive Forms is an official SAP license. For
more information, consult your contact person in your local SAP sales office and see SAP Note 750784 .

Note
Adobe Designer enables form authors to create new form designs or customize previously developed form designs. The form design provides the presentation
or layout for the data, including formatting information such as font size, alignment, field logic, and graphics. The data from your SAP system populates the
form design and determines what the final output will contain when Adobe document services processes the form design and data. The output can be either
interactive forms or print forms.

Features
The Document Services License Service checks the license status of interactive form designs in your SAP system on a daily basis.

Note
The check of the license status of interactive form designs in your SAP system is done by the Customer measurement program (transaction USMM).

PUBLIC Page 15 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
Forms are classified and displayed as:
Customer Forms , the total number of your forms.
SAP Forms, the total number of original SAP forms.
Draft Forms , the total number of forms in a draft state. Draft forms are forms that are not currently in production and therefore do not count as a
licensed/unlicensed form.

Procedure
1. Navigate to http://<server>:<port>/nwa to start the SAP NetWeaver Administrator.

Note
<server> is the AS Java where the Adobe document services are installed and <port> is the HTTP port of the AS Java.

2. Choose Configuration Management Infrastructure Management Adobe Document Services


3. Choose Licensing in the left pane. You can then do following.
License Adobe document services
1. Choose the button Set System Status . The dialog box System Status appears.
2. If your system is licensed for the use of Adobe document services, set the appropriate indicator.
3. Save .
Configure License Status Calculation
1. Enter the time of day (24-hour clock) at which the system should update the license status of all interactive form designs processed to date.
2. Save .
Run License Status Calculation
Choose Run License Status Calculation, to immediately verify the license status of all interactive form designs processed to date. The system queries your SAP
system, modifies the total number of licensed and unlicensed interactive form designs, and updates the list of unlicensed interactive form designs accordingly.

1.6 Analyzing ADS Errors in an ABAP Environment

Prerequisites
Yo have access to the AS ABAP that host the applications, which trigger form processing and to the AS Java, where the ADS are running.
On AS ABAP you have the debugging authorization.
You have the permissions to use the ABAP transactions SFP, SE38, SM59 and the SAP NetWeaver Administrator.

Context
When processing forms in an ABAP environment using Adobe Document Services (ADS) running on AS Java, you might need to analyze the following types of
errors issued by the ADS:
Connection errors
The AS ABAP could not establish the connection to the ADS.
Rendering errors
Errors that occured during or after form rendering (e.g. PDF form cannot be created or form cannot be displayed properly).
Configuration errors
The ADS configuration - especially the installation and configuration of the Reader Rights Credential - is not correct.

Procedure
1. If the ADS report a connection error , check the connection from the AS ABAP to the ADS.
ADS messages: Invalid HTTP connection, SOAP Runtime Exception, no message in case of time-out
SAP notes: 944221 , 944221
ADS configuration:
Performing Basic ADS Configuration in an ABAP Environment
Configuring the SSL Connection to ADS in an ABAP Environment
2. If the ADS report a rendering error , proceed as follows:
1. Set the system to save runtime information and generated PDF files locally
More information: Saving Runtime Information About Form Generation Locally
2. Analyze the returned PDF file and its additional information, to find out the reason for errors and warnings.
If you have further questions to be solved by the support team, create a message under BC-SRV-FP and attach the PDF with additional information
More information: Information on ADS Errors Contained in a Returned PDF File
3. If the ADS report a configuration error , that points to problems regarding he installation and configuration of the reader Rights Credential, analyze the
respective ADS configuration settings.
ADS message: Error during call to AdobeDocumentServer, WDRuntimeException
1. Check the existence of the Reader Rights Credential file in the folder
<DIR_GLOBAL>/AdobeDocumentServices/TrustManagerService/trust/credentials
2. Check the password registration as follows:
1. Start the SAP NetWeaver Administrator.
2. Choose Configuration Management Infrastructure Management Adobe Document Services
3. Check for the existence of an entry under Credentials with the Alias ReaderRights .

PUBLIC Page 16 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.
1.6.1 Information on ADS Errors Contained in a Returned PDF
File

Use
If the trace level is set to a the value 4, or if an error occurred during form rendering, Adobe Document Services (ADS) provide you with a PDF and several files
embedded in its attachment.
These files contain all input that is needed for rendering of the form. For performance reasons, it is an untagged PDF and therefore not accessible. The
appearance of the returned PDF depends on the setting for the trace level and on the type of error (error or warning). In some cases, the called PDF form is
returned. There may also be cases when only a PDF containing error messages is returned.
The following tables give you an overview on the returned rendering results and attached files depending on settings and errors.
Rendering results returned by the Adobe Document Services

Rendering error Trace level = 4 PDF requested Returned rendering results

Yes Not relevant Not relevant No PDF form is returned. Instead a file ERROR.PDF with attachments is created and displayed. It
is stored on the ADS server in
<DIR_GLOBAL>\AdobeDocumentServices\renderErrorLog\ErrorFiles, under file
name Date+Time+ApplicationName+Username.pdf, exactly specified in TRACE.TXT.

No Yes Yes The PDF form is returned with additional information in its attachments. If warnings exist, they are
listed in a file ERROR.PDF , which is also included in the attachments.

No No PDF form is returned. Instead a file ERROR.PDF with attachments is created and displayed,
which may contain warnings or even be empty.

No Yes The PDF form is returned without any additional information (interactive form or PDF form in print
preview).

No No PDF form is returned. A PDL may be created for printing.

Files attached to ADS rendering results

File Description in PDF Further description

Error.pdf Render Error report Errors and warnings, that occurred during rendering.

Data.xml Document Services Data Runtime data

pdfDocument.xml Document Services Control Stream Control file for rendering

<formname>.xdp Document Services Template Layout of the form, can be displayed in Adobe LiveCycle
Designer. Note that it does not contain any separate
schema or context information.

trace.txt Document Services Trace Trace information provided by Adobe document services.

xfa.xci Document Services Config Control file for rendering

<name1>.xdc Document Services XDC Control file for printer or Adobe Reader

<name2>.xdc Document Services XDC 2 (if there is a dual render) Control file for printer or Adobe Reader

PUBLIC Page 17 of 17
2014 SAP AG or an SAP affiliate company. All rights reserved.