Error Importing Functions for Web Service

We have followed the directions on the SAP website to configure the WebServices Adapter on the DI Web Admin Console and it’s started successfully.

Upon creating a datastore of type Adapter, using the WebServices Adapter within the designer, I get the attached / below error.

The client is using DI 11.7.2.0.0.
Trace Log:
3/16/10 4:10:22 PM Thread[main,5,main] Create broker client for life-cycle management. Host:port = PSC-BOE-1:4001
3/16/10 4:10:22 PM Thread[main,5,main] Create broker client for data exchange with ASP. Host:port = PSC-BOE-1:4001. Client ID = com.acta.adapter.webservice.adapter.WebServiceAdapter.data_1
3/16/10 4:10:23 PM Thread[Thread-11,5,main] Host and port for the Access Server are not defined in startup configuration. Real-time services are not available.
3/16/10 4:10:23 PM Thread[Thread-11,5,main] Start instance [WS_Adapter] of adapter [com.acta.adapter.webservice.adapter.WebServiceAdapter].
3/16/10 4:10:23 PM Thread[Thread-11,5,main] Register the client ID [com.acta.adapter.webservice.adapter.WebServiceAdapter.data_1] and adapter destination [PSC-BOE-1:4001] with the adapter manager.
3/16/10 4:10:23 PM Thread[Thread-11,5,main] Registration complete.
3/16/10 4:16:09 PM Thread[Thread-10,5,main] Unable to parse WSDL from Web Service. Error: The root element is required in a well-formed document.
3/16/10 4:16:09 PM Thread[Thread-10,5,main] Error browsing root nodes. Xml generated so far: . com.acta.adapter.sdk.AdapterException: Unable to parse WSDL from Web Service. Error: The root element is required in a well-formed document.
at com.acta.adapter.webservice.adapter.WebServiceBrowse.getRootNodes(WebServiceBrowse.java:104)
at com.acta.adapter.sdk.AdapterRunnerImpl.processBrowseRoot(AdapterRunnerImpl.java:2254)
at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:101)
at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:424)
at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:51)
at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1575)
at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:97)

Error Log:
3/16/10 4:16:09 PM Unable to parse WSDL from Web Service. Error: The root element is required in a well-formed document.
3/16/10 4:16:09 PM Error browsing root nodes. Xml generated so far: . com.acta.adapter.sdk.AdapterException: Unable to parse WSDL from Web Service. Error: The root element is required in a well-formed document.
at com.acta.adapter.webservice.adapter.WebServiceBrowse.getRootNodes(WebServiceBrowse.java:104)
at com.acta.adapter.sdk.AdapterRunnerImpl.processBrowseRoot(AdapterRunnerImpl.java:2254)
at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:101)
at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:424)
at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:51)
at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1575)
at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:97)
adapter.JPG


nhohman (BOB member since 2008-11-19)

the error is generic, there is some problem parsing the WSDL
check if WSDL is valid, try to open the WSDL in SoapUI and see if you are able to see the operations, input and output


manoj_d (BOB member since 2009-01-02)

Well one thing we tried was several different different WSDLs, one even being the Data Integrator one (11.7.2) and the SAME message was output.


nhohman (BOB member since 2008-11-19)

Hi

did you find the problem with this and did you get a solution. I seem to have the same issue with my WSDL.


Piet K :south_africa: (BOB member since 2008-01-21)

If I remember correctly, it was a problem with the actual WSDL. We used a third party tool to parse the WSDL and it turned up with errors.

What version are you running?


nhohman (BOB member since 2008-11-19)

we are on versaion 11.7


Piet K :south_africa: (BOB member since 2008-01-21)

Validate your WSDL using a third party tool, or send it to me, and I’ll have a look at it.


nhohman (BOB member since 2008-11-19)

Hi thank you for your help.


Piet K :south_africa: (BOB member since 2008-01-21)

I can’t access that machine. Is this site available on the Internet? Can you download and save and attach a copy of the WSDL?


nhohman (BOB member since 2008-11-19)

I have saved the data in a text file
my_wsdl.txt (4.0 KB)


Piet K :south_africa: (BOB member since 2008-01-21)

Did you attach it?


nhohman (BOB member since 2008-11-19)

Could anyone tell me if it matters if you have a namespace between your message and response.

in other words two name spaces.
attached the WSDL
DI_WSDL.txt (67.0 KB)


Piet K :south_africa: (BOB member since 2008-01-21)

How are you specifying the target URL ? complete URL as http://… or you are using the file that you have attached ?

the file you have attached is formated XML copied from the browser, it will fail, if you want to save WSDL to file by opening it in Browser then do the following
Open the WSDL in browser
right click and select view source
this will open the WSDL in notepad
save the file to disk

I am able to import the WSDL using Adapter Datastore in 11.7.3.12, also in 12.2 what is the complete version of 11.7 that you are using ?


manoj_d (BOB member since 2009-01-02)

Hi minoJ-D

I am using 11.7.3.0 and I am using the full URL http://eudbl01:1009/wsbns/dise3g/services/bnsReceiverPort?wsdl
I will attached the test file as specified by you.

the URl failed to import but as a file it also failing. could it be because of the tags that are missing this <xs:element where they are absent in the URL and source code test file.
system_WSDL.txt (5.0 KB)


Piet K :south_africa: (BOB member since 2008-01-21)

can you check the Adapter error and trace log ? is Adpater failing with StackOverFlow error ? this is the error I am getting DI 11.7.3.12

I am able to import the WSDL without any problems in 12.2

I think its a bug in 11.7 and its fixed in 12.2, let me check if there is workaround for this


manoj_d (BOB member since 2009-01-02)

yes that is exactly wthat i am getting and we are in the process of upgrading to 12.2…

thanks for your help


Piet K :south_africa: (BOB member since 2008-01-21)

yes that is exactly wthat i am getting and we are in the process of upgrading to 12.2…

thanks for your help


Piet K :south_africa: (BOB member since 2008-01-21)