cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to generate WebService Client with Exported (BAPI) WSDL file from XI

Former Member
0 Kudos

Hi there,

I, trying to setup a simple Web Service environment where I'll be exposing a BAPI as Web Service via XI.

So these are the steps I followed:

<b>1)</b> first I imported the BAPI meta data into my SWC in the repository. <b>2)</b> Second I defined my interrface etc.. <b>3)</b> Third I exported the generated BAPI WSDL file. <b>4)</b> Fourth, I tried to generate a Java proxy/client for my Web Service using a Java IDE (IBM WebSphere Application Developer and XML Spy).

Now the problem is that Im not able to generate the Web Service client using the exported WSDL file, the WSDL seems not to be valid...From the generated errors in the IDE, I can see that the problem has to do somewhere/somehow with the WSDL Binding element, which input parameters do not match the input parameters of the port type.

This is a small part of the WSDL file as generated by XI:

.....

<wsdl:message name="BAPI_AR_ACC_GETOPENITEMS.Input">

<wsdl:part name="parameters" element="s0:BAPI_AR_ACC_GETOPENITEMS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>

</wsdl:message>

<wsdl:message name="BAPI_AR_ACC_GETOPENITEMS.Output">

<wsdl:part name="parameters" element="s0:BAPI_AR_ACC_GETOPENITEMS.Response" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>

</wsdl:message>

<wsdl:portType name="BAPI_AR_ACC_GETOPENITEMS.PortType">

<wsdl:operation name="BAPI_AR_ACC_GETOPENITEMS">

<wsdl:input message="s0:BAPI_AR_ACC_GETOPENITEMS.Input"/>

<wsdl:output message="s0:BAPI_AR_ACC_GETOPENITEMS.Output"/>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="BAPI_AR_ACC_GETOPENITEMS.SAPBinding" type="s0:BAPI_AR_ACC_GETOPENITEMS.PortType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

<s0:binding style="rfc"/>

.........

..............

Has anyone faced a situation like this before? Any clues where to look? I appreciate any feedback, thanks!

Rob.

Message was edited by: rob viana

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi Rob!

I'm facing the same problem - how did you solve your issue then? I'm getting following error during generation on .NET side:

============================================================================================

Error: There was an error processing 'http://server/wsdl/MIAMI_ACCDOCPost.wsdl'.

- The document at the url http://server/wsdl/MIAMI_ACCDOCPost.wsdl

was not recognized as a known document type.

The error message from each known type may help you fix the problem:

- Report from 'DISCO Document' is 'Discovery document at the URL http://server/wsdl/MIAMI_ACCDOCPost.wsdl could not be found.'.

- The document format is not recognized (the content type is 'content/unknown').

- Report from 'WSDL Document' is 'There is an error in XML document (2, 70138).'.

- Value cannot be null.

Parameter name: name

- Report from 'XML Schema' is 'The root element of a W3C XML Schema should be <schema> and its namespace should be 'http://www.w3.org/2001/XMLSchema'.'.

============================================================================================

kr Martin

bhavesh_kantilal
Active Contributor
0 Kudos

Martin,

Not sure if i get the entire requirement here, but if the requirement is to expose a interface as a webservice, then you can follow the steps in this article ( section 3.2.2) to do the same. Select the RFC as you outbound message interface and do the needful,

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a2202...

Regards

Bhavesh