ADS Configuration Tips

Resources.

Please use the ADS Configuration Guides to configure your system the Tips below are intended as a rough guide to the process only.

NW 7.0 ADS Documentation: Adobe Document Services Configuration Guide.

NW 7.31 ADS Documentation: Adobe Document Services for Form Processing

Check SAP Note 925741 - Adobe document services (ADS) with non-supported platforms

Check SAP Note 944221 - Troubleshooting if problems occur in forms processing

ADS Trouble shooting tips from Hints and Tips section: ADS Problem Analysis

 

Add Adobe Rights Credentials.

Get your Credential by following SAP Note 736902 - Adobe Credentials.

Once recieved copy the Credential to:

c:\usr\sap\SYS\global\AdobeDocumentServices\TurstManagagementService\trust\credentials

Make sure it has sufficent permissions.

Open Visual Admin -> Server -> Services -> Document Services Configuration

Alias: ReaderRights

Enter passwd

Browse for Credential file.

Add - Date should be 2023.

Restart Java Stack.

 

Configure ADS

ADS must be on at least NW700 SP 11 Patch 1 for Windows 64-bit see SAP Notes: 886572 and 848539

The Java and ABAP stacks should be at the same Support Package level!

General Configuation:

Make sure Java Stack points at correct ABAP Client.

  • open ConfigTool
  • instance -> server -> services -> com.sap.security.core.ume.service
  • set ume.r3.connection.master.client to your Master client
  • restart the Java Stack

ADSUSER and ADS_AGENT must be in Java Master Client and Default Client. You can also set the Client  in the HTTP FP_ICF_DATA_<SID> Destination Client attribute if the Java Master Client is not the same as the Default Client. When setting up a new the Master Client  to use with FLM use Client Copy to copy Users from Client 001 (deault Java Client) to the Master Client to transfer the neccessary users and authorizations. - This will overwrite the currently configured users!

Ensure user ADS_AGENT has role: SAP_BC_FP_ICF

In SICF make sure sap -> bc -> fp is Activated.

 

Connection to ADS:

In SM59  make sure the ADS rfc is working properly and the ADSUSER passwd is correct. Test.

Note 1177315 - ADS RFC destination test return 403 / 404 code

 

Connection from ADS to ABAP:

In VA create FP_ICF_DATA_<SID> destination - remember Java is case sensitive.

    Tip: make sure user names are in ALL CAPs.

           server -> services -> destinations -> Runtime Tab -> Select HTTP and "NEW"

http://<server>:<abap port>     example abap port: 8000

Basic Auth / ADS_AGENT and password

Save and Test: Success with response code 200.

    Errors with the test about missing web services could mean your Java Stack isn't registered with or in the same SLD.

The Java Destination may also need to be created under Web Services.

    same as above except the port will be the Java port     example: 50000

 

Test configuration:

In SE38 check the following ADS test programs.

FP_PDF_TEST_00

    This will return the ADS Version if configured properly.

    If it fails check your ADS rfc and ADSUSER password.

FP_CHECK_DESTINATION_SERVICE

    Run twice with and without "With Destination Service" checked.

    This will return a file size if configured properly.

    If it fails:

    Make sure ADS_AGENT passwords are correct on ABAP/JAVA.    

    Test the Destinations are correct and the SLD is configured on your ABAP stack.

ADSUSER should also be set as a technical user.

If ADS isn't working consult the Adobe Document Services Configuration guide.