2009 Feb 11 4:11 PM
Hi,
I want to consume a web service in ABAP (on a WAS 7 box) and have read many blogs/posts about using a proxy object.
I've gone to SE80 and selected create a service consumer, enter the URL for the WSDL.
The generation of the proxy fails with the following messages;
Proxy-Generierung: Fehler aufgetreten
Exception occured in the library handler
not implemented
There is no other help or information in these errors.
Does anyone have any ideas on what is causing this and what I can do to successfully generate a proxy to consume the web service ?
Cheers
James
Hi,
I want to consume a web service in ABAP (on a WAS 7 box) and have read many blogs/posts about using a proxy object.
I've gone to SE80 and selected create a service consumer, enter the URL for the WSDL.
The generation of the proxy fails with the following messages;
Proxy-Generierung: Fehler aufgetreten
Exception occured in the library handler
not implemented
There is no other help or information in these errors.
Does anyone have any ideas on what is causing this and what I can do to successfully generate a proxy to consume the web service ?
Cheers
James
2009 Mar 09 3:48 PM
2009 Mar 12 3:02 PM
2009 Apr 01 10:40 AM
Well, the same problem here. Can't figure out the message "not implemented". Ridiculously I can create a proxy for another WebService, that has the same namespaces and is more complex (regarding the elements and methods)
Regards
Torsten
2009 Apr 01 12:15 PM
ok, probably here's the solution. The WebService I tried to use had "non-soap"-Methods. The binding in the WSDL for them looked like this:
<wsdl:binding name="Service1HttpGet" type="tns:Service1HttpGet">
<http:binding verb="GET"/>
<wsdl:operation name="ConvertPDF2PCL">
<http:operation location="/ConvertPDF2PCL"/>
<wsdl:input>
<http:urlEncoded/>
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
Afaik, this allows you to call the WebService directly via http-GET.
I have saved the wsdl locally and deleted the binding, port, message and service elements from the file, that are reffering to these methods. Now, SAP is creating the proxy (I'm very disappointed (once again), that SAP could not handle these wsdl-elements, e.g ignoring them). Surely, you can no longer use the wsdl-URL for the proxy, but the local file.
I still have to test the WebService, but I guess, it will work.
Regards
Torsten
2009 Apr 14 9:28 AM
I can't get any web service to work.
Always get the same error.
2009 Apr 16 1:13 PM
Hello Torsten,
It seems that the Web Service You are going to consume is a SOAP 1.2 one.
It is apparently making use of the so-called "SOAP Web Method Feature" which is part of the SOAP 1.2 specification (see [Web Method Feature (W3C)|http://www.w3.org/TR/soap12-part2/#WebMethodFeature]).
Unfortunately, SOAP 1.2 is, to the best of my knowledge, not supported as yet by the SOAP Adapter in SAP NW 7.0 / 7.1. That leaves You, in theory, with one of the following options:
- It might be possible to consume that service with the help of Axis framework (see [Using the Axis Framework in the SOAP Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm]). SAP Help states that with the help of the Axis framework SOAP 1.2 can be used. However, there are no further details on that subject, especially whether Web Method feature can be utilised (btw - has anyone tried this?).
- Ask service provider for a SOAP 1.1-compatible WSDL.
- Attempt to reverse engineer the SAP SOAP proxy so that it is capable of consuming a SOAP 1.2 Web Method-based web service (has anyone done this before?).
Would You be so kind to post whether, and how, You were able to consume this web service?
Kind regards
Wiktor Nyckowski
2009 Apr 16 1:23 PM
Hi,
as I stated above, I simply deleted the wsdl 1.2 related parts from my wsdl-file. That is working at last for the WebService I am using.
How to use Axis inside the SAP Framework, I've no idea, although I've already worked with Axis (1&2) for pure Java Applications.
Regards
Torsten