Adobe Connection Error - Java 

Problem Description

This problem analysis scenario describes the approach in order to investigate and resolve connection errors to the Adobe document services that are accessed from a Java environment.

When a connection error appears, the following message is displayed and simultaneously written to the Web Dynpro log file with a complete error stack trace:

●      Service call exception, PDFObjectRuntimeException

The nested exceptions are:

·        ConnectException

·        MalformedURLException

·        SocketTimeoutException

Scenario Type:	Error analysis
NetWeaver Component:	SAP Web AS, Adobe document services
Validity:	SAP NetWeaver ‘04 >= SP Stack 12 SAP NetWeaver 7.0 >= SP Stack 4

Possible Error Sources

Error Source	Analysis
Faulty connection	...        1.      Check general availiability of document services        2.      Check configuration settings

Decision Roadmap

Prerequisites

You need to have access to the following systems:

·        Web AS Java that hosts the Java Web Dynpro application (HTTP connection)

·        Web AS Java that hosts the Adobe document services (HTTP connection)

·        Web AS ABAP that hosts the Computing Center Management System (CCMS) (SAP GUI connection)

In order to change configuration settings you need the appropriate user rights.

Main Tools

Visual Administrator

Execution

The following figure shows the solution path that should be followed in order to correct connection errors. First of all you should check the general availability of the document services. If this does not solve the connection problem, you have to investigate configuration settings that might be erroneous.

Figure 1: Solution path

Analysis

Check general availability

Heartbeat

First of all you should check the general availability of the document services.

...

       1.      Connect to the CCMS and start transaction RZ20.

       2.      Navigate to the monitor set SAP J2EE Monitor Templates and load the monitor Adobe Document Services. The Heartbeat node contains availability information for all registered servers. For more information, see Configuring GRMG Availability for the Adobe Document Services.

Web Services Navigator

In a second step you should check the document services by calling it within the Web Services Navigator using the following URL:

http://[host]:[port]/AdobeDocumentServices/Config

You have to enter the host name and the port number of the Web AS Java that runs the document services. The default port number is 50000.

Table 1 shows error messages and their probable origins.

Table 1: Error messages

Origin	Error message
Message Server	Cannot find server or DNS Error
Dispatcher node
Server node	503 Service Unavailable // Dispatcher running, but no server connected!
HTTP provider
Web Services Container	503 Service Unavailable // Application stopped!
EJB Container

If necessary restart the appropriate instance, node or service. You can do this by using the Visual Administrator.

Check configuration settings

In order to call the document services from a Java Web Dynpro application a web service client must have been configured properly on the appropriate host.

...

       1.      Start the Visual Administrator and select the node Server <x> / Services / Web Services Security from the Cluster tab.

       2.      Within the tab Web Services in the right frame select Security Configuration / Web Service Clients / sap.com / tc~wd~pdfobject / com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.

The following attributes should have been set accordingly if no SLD is used (tab Transport Security):

○       Destination

■       URL: Default or Custom, http://[host]:[port]/AdobeDocumentServices/Config?style=document (e.g. http://localhost:50000/...) or .. https://[host]:[port]/AdobeDocumentServicesSec/Config?style=document if the connecttion uses SSL.

■       Authentication: select BASIC or X.509 Client Certificate

If BASIC is selected, Basic Authentication / Username and Basic Authentication / Password must refer to the user that has been assigned to the security role ADSCaller within the Web AS Java that hosts the document services.
If X.509 Client Certificate is marked, the fields Client Certificate Authentication / Keystore view and Client Certificate Authentication / Certificate have to be filled in with the appropriate values).

If the connection to the document services uses the SLD, the attributes should be set as follows:

○       Destination / URL: SLD

○       Synchronize with System Landscape

■       System Name: [SID].SystemHome.[host]

■       WS Name: {com.adobe/AdobeDocumentServices}{AdobeDocumentServicesAssembly.jar}
{AdobeDocumentServices}

■       WS Port: {com.adobe/AdobeDocumentServices}{AdobeDocumentServicesAssembly.jar}{Adobe
DocumentServices}{urn:AdobeDocumentServicesWsd}ConfigPort_Document

The PDF Object has to be restarted if any changes have been applied to the web service proxy. Select the node Server <x> / Services / Deploy from the Cluster tab within the Visual Administrator and choose the Application option within the right frame. Mark sap.com/tc~wd~pdfobject and then stop and start this application using the appropriate buttons.

Additional Information

Refer to the document Adobe Document Services Configuration Guide for detailed information regarding the configuration of the Adobe document services.