DCA-40012: The Web Service call failed. A connection to the target Web Service could not be created.
(Doc ID 1471810.1)
Last updated on JUNE 12, 2017
Applies to:Oracle WebCenter Portal - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11g]
Information in this document applies to any platform.
This note provides suggestions for the error DCA-40012 in WebCenter Portal 18.104.22.168/22.214.171.124.
The error occurs when trying to display a custom taskflow in a WebCenter Portal page that consume a web service data control.
Steps To Reproduce:
- In JDeveloper, create a new application with a web service data control to any SOAP web service. Then create a simple fragment task flow that displays the results a call to one of the methods.
- Deploy this task flow to WebCenter Space (create a wrapper WAR file and deploy as a shared library to WC_Spaces, then reference the library in DesignWebCenterSpaces application).
- In Spaces runtime, add the new task flow to a resource catalog, then add the task flow to a page in a space. At this point the page will either freeze or an error will occur.
- Looking in the logs for WC_Spaces.out, it seems that there is some problem with the way the connection details have been deployed as the following is shown:
"<Warning> <oracle.adf.adapterDC.webservice> <BEA-000000> <Verify if the connections.xml has valid metadata defined for connection 'spaces'>"
Shortly afterward, the following is then shown:
Testing the task flow locally in the integrated WebLogic works as expected.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document