ADS Configuration

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.

Checking the IIOP Service and the Start-up Properties

  1. Start the configuration tool of the AS Java
    Run /usr/sap/<SAPSID>/<instance_name>/j2ee/configtool.bat
  2. Check if the start-up mode of the service IIOP is set to always
    • In the left frame, open the tree Cluster data → Global dispatcher configuration → Services
    • Choose service IIOP
    • The field Start-up mode in the right frame must be set to always. If it is not true, apply the value always
    • Choose Apply changes
    • Repeat above steps for the following path
      Cluster data → Global server configuration → Services
  3. Check if the Java start-up property for Adobe document services is set
    • Select Cluster data → instance_<IDxxxx> → server_<IDxxxx>
    • In the right frame, check if the following line exists in the Java Parameters area of the tab General:
      If the line does not exist, add the line to this section.
  4. Exit the configuration tool
  5. Restart J2EE system if changes are done

Creating a User in the SAP NetWeaver AS ABAP for Basic Authentication

  1. Create user ADSUSER as system user and save it
  2. Create Role ADSCalleres (No authorization required)
  3. Add user ADSUSER to this Role

Assigning the Security Role in Java

  1. Log On to Visual Administrator
  2. On the Cluster tab, choose Server <x> → Services → Security Provider
  3. Under User Management Tab check ADSUSER is present with ADSCalleres group
  4. On the Policy Configurations tab, in the Components area, select com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar
  5. On the Security Roles tab, select ADSCaller from the Security Roles list
  6. In Mapping area add ADSUSER in User

Creating the ABAP Connection

  1. Call transaction SM59
  2. Choose Create
  3. Enter at least the following
    • RFC destination: ADS
    • Connection type: G
    • Description: ADS Connection
  4. Choose ENTER
  5. Choose the Technical settings tab and enter at least the following
    • Target Host : J2EE Engine Host Name
    • Service No: 5<InstanceNo>00
    • Path Prefix: /AdobeDocumentServices/Config?style=rpc
    • A warning is displayed: Query String Not Allowed. Ignore this warning by pressing Enter
  6. Choose the Logon/Security tab, select Basic Authentication
  7. In the User and Password boxes, enter the user name ADSUser and the password
  8. Save your settings
  9. Choose Test Connection
  10. A screen is displayed. The field status_reason: OK indicates that the test was successful

Please Note that above configuration is for Dual stack systems. If you are using standalone JAVA system for Adobe configuration then need to create ADSUser in J2EE system.

Create User ADS_AGENT in ABAP system

Type: Service
Role: SAP_BC_FP_ICF (For dual stack system), SAP_BC_FPADS_ICF (For J2EE only system)

Create Destination Service

  1. Log on to the Visual Administrator
  2. On the Cluster tab, choose Server <x> → Services → Destinations. Under Runtime, select HTTP. The available destinations are displayed.
  3. Choose New in the navigation panel
  4. In the dialog box that follows, enter the name FP_ICF_DATA_<SID>, where <SID> is your ABAP system, for the new destination and choose OK.
  5. Under Connection Settings, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in the URL field:
    <a href=”http://:”>http://<hostname>:<HTTP_port>
    HTTP_Port is port which you can find in SMICM transaction in services (SHIFT+ F1)
  6. Enter the appropriate client number of the system, where the service user ADS_AGENT exists into the client field
  7. Under Logon Data, choose BASIC in the Authentication field
  8. Enter ADS_AGENT in the Username field and enter the same password as given for this service user in the SAP NetWeaver AS ABAP in the Password field
  9. Choose Save
  10. If you choose Save and Test, you can ignore the message Error during ping operation:  Received HTTP response 404

Activating the ICF service

Log On to ABAP system
Transaction SICF
Activate /sap/bc/fp and /sap/bc/fpads

Checking Configuration

Call transaction SA38.
Execute report FP_TEST_00
Enter Name of connection as ADS
Select default printer and select print preview. You should get PDF displayed.

If you get any error or not getting PDF output, please check below reports.


This report checks the configuration of the destination service and the ICF service sap/bc/fp
Execute above report once with w/o destination service and then with destination service

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!