Adaptive WebService

[Former Member]

When using logical destinations for the adaptive WebService, what kind of response is expected from the logical metadata destination?

Regards

Thomas

[BeGanz · Accepted solution]

Hallo Thomas,

Logical Web Service Destinations are currently only supported for those WS providers supporting WSIL like SAP provider systems. WSIL stands for <i>Web Services Inspection Language</i>.

Best regards, Bertram

[Former Member · Accepted solution]

Hallo Bertram,

I'd read that the WS provider has to support WSIL. But what does it mean? The logical destination has to refer to a WSIL source instead of a WSDL source? I'd done so, the result looks similar to the one I'd posted. Only the content is differs, the error (invalid response) is the same.

That's the reason why I ask: What kind of response is expected.

Regards

Thomas

Message was edited by:

Thomas Paulsen

[Former Member · Accepted solution]

Hi Thomas,

the api for resolving WS destinations supports both wsdl and wsil links, but the problem is different here. The response from the link is code 200 which is http response for ok, but the content-type is not text/xml. So the api fails with reading it.

Regards,

Patric.

[Former Member · Accepted solution]

That's it

But one issue:

If Iit's my web service server, I can set the type for wsil extension to text/xml,

but default it is text/plain for *.wsil and application/xml for *.xml.

Is it possible to force the model creator/loader to read everything as text/xml?

Regards

Thomas

[Former Member · Accepted solution]

Short answer: No.

Afaik the mechanism takes the content-type from the http-response (what else should it do?); so proper configuration on WS provider side is needed.

I've looked into SAP WS providers (ABAP, J2EE) and also non-SAP (http://www.xmethods.net/inspection.wsil): they all return WSIL as text/xml.

Regards,

Patric.

[Former Member · Accepted solution]

Not even all non-SAP providers:

http://dublincore.org/services/inspection.wsil

That's the one I'd used for testing.

And a more specific error mesaage ("Wrong content type. Received: something/wrong Required: text/xml") would be more helpful than "Invalid response".

Regards

Thomas

[Former Member]

Hi Thomas,

you should see the response in form of WSDL (under CompleteAction Operation), after the consuming of Web Service.

You can refer to:

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/44/55a0b999d44de2e10000000a1553f7/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/44/55a0b999d44de2e10000000a1553f7/frameset.htm</a>

Best regards,

Gianluca Barile

[Former Member]

Hi Gianluca

I let it refer to the same wsdl source I'd used to create the model.

But on startup I get a

...discovery.BaseIOExcption: Invalid Response Code 200 while accessing URL http://localhost/test.xml Response message: OK. Content type application/xml Body Content: <?xml ......[the whole wsdl content] >.

at... discovery.DestinationResolver.resolveURL

...

No idea what's going wrong.

Regards

Thomas

[Former Member]

Thomas,

please can you post the entire response?

Regards,

Gianluca Barile

[Former Member]

Gianluca,

here it is:

The initial exception that caused the request to fail, was:

com.sap.engine.services.webservices.espbase.discovery.BaseIOException: Invalid Response Code 200 while accessing URL: http://10.4.17.61/itemSummary.xml. Response Message: OK. Content Type: application/xml. Body Content: <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://www.dublincore.org/axis/services/itemSummary" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://www.dublincore.org/axis/services/itemSummary" xmlns:intf="http://www.dublincore.org/axis/services/itemSummary" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <wsdl:message name="listItemSummaryRequest"> </wsdl:message> <wsdl:message name="listItemSummaryResponse"> <wsdl:part name="listItemSummaryReturn" type="xsd:string"/> </wsdl:message> <wsdl:portType name="Summary"> <wsdl:operation name="listItemSummary"> <wsdl:input message="impl:listItemSummaryRequest" name="listItemSummaryRequest"/> <wsdl:output message="impl:listItemSummaryResponse" name="listItemSummaryResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="itemSummarySoapBinding" type="impl:Summary"> <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="listItemSummary"> <wsdlsoap:operation soapAction=""/> <wsdl:input name="listItemSummaryRequest"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://services" use="encoded"/> </wsdl:input> <wsdl:output name="listItemSummaryResponse"> <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://www.dublincore.org/axis/services/itemSummary" use="encoded"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="SummaryService"> <wsdl:port binding="impl:itemSummarySoapBinding" name="itemSummary"> <wsdlsoap:address location="http://dublincore.org/axis/services/itemSummary"/> </wsdl:port> </wsdl:service> </wsdl:definitions>

at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveURL(DestinationsResolver.java:219)

at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveEntity(DestinationsResolver.java:119)

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:184)

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSInterfaces(WSQueryImpl.java:151)

at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getWSDLUrl(ServiceDiscoveryImpl.java:71)

... 41 more

The original is from www.dublincore.org, I want to test the adaptive WebService with a working example before trying my own

I had to put them on a local webserver because I have troubles connecting to the Internet, the proxy setup in the portal doesn't seem to work.

Regards

Thomas

[Former Member]

Thomas,

you sholud check the row 219 into the DestinationsResolver file.

In addition you can check in this link if your error is listed (I haven't found it):

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/2f2c4142aef623e10000000a155106/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/2f2c4142aef623e10000000a155106/frameset.htm</a>

I think that you must perform some activity on Visual Administrator.

Best regards,

Gianluca Barile

[Former Member]

I would check the source if only I had it.

But I don't believe that SAP will publish the source.

[Former Member]

Enabling the trace will not help at all:

The response from 10.4.17.61 is gzip encoded.

I'd tried wireshark instead, but it only shows a wonderful http request and response.

Without any errors.

The traffic is OK, but SAP dislike the content of the response.

Someone knows an external (non-SAP) webservice which is free and works with SAP?

Regards

Thomas