Analyzing ADS Errors in a Java Environment

When processing forms in a Java environment using Adobe Document Services (ADS), you might need to analyze the following types of errors issued by the ADS:

Connection errors
The AS Java runtime could not establish the connection to the ADS.
Rendering errors
Errors that occur 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.

Prerequisites

Yo have access to the AS Java that host the applications, which trigger form processing, and the Java, on which the ADS are running.
On AS Java you need to have the appropiate administrative permissions.
You have the permissions to use the SAP NetWeaver Administrator.

Procedure

If the ADS report a connection error, check the connection to the ADS.
ADS message: Service call exception, PDFObjectRuntimeException with the nested exceptions ConnectException, MalformedURLException and SocketTimeoutException
1. To check the general availability of the ADS, proceed as follows:
  1. Start the Web Services Navigator via the address http://<host>:<port>. (Enter the host name and the port number of the AS Java, that runs the ADS.)
  2. Choose Web Services Navigator
  3. In the list, choose com.adobe/AdobeDocumentServces_com.adobe_AdobeDocumentServicesVi
  4. Choose rpData.
  5. Choose Execute without entering any parameters.
  6. Enter the user name ADSUser and the password and press OK.
  7. 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.)
2. If the ADS availability check does not solve the connection problem, analyze the configuration settings as follows:
  1. Open the file inspections.wsil via the URL http://<host>:<port>>/inspection.wsil
  2. In the dialog box, enter ADSUser and the appropriate password.
  3. The system displays an XML file listing all available services.
  4. Search for the string Adobe to see, if ADS are available.
  5. If you do not find any information related to Adobe, check the configuration settings.
    More information:
    
    Creating a User for Authentication to ADS in a Java Environment
    
    Setting Up Basic Authentication to ADS in a Java Environment
If the ADS report a rendering error, proceed as follows:
1. Set the Web Dynpro Trace level to ALL to get the PDF with attachments, respectively in case of a rendering error a file ERROR.PDF, which is stored on the ADS server.
  More information: Viewing the Logs
2. Analyze the returned PDF file and its additional information, to find out the reason for errors and warnings.
  More information: Information on ADS Errors Contained in a Returned PDF File
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
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.