cancel
Showing results for 
Search instead for 
Did you mean: 

messages not adviced in extern definition after import wsdl-file from WAS

frank_schmitt3
Participant
0 Kudos

Hi friends,

after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...

But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?

Thanks in advance,

Frank

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

first point to do is to clean the wsdl:

- remove tags "sap:useFeature" (and the contents of the tag)

- remove tag "description" if fault pops up.

second point: Reference entry manually:

- three files are generated: main, bindings and ports (look inside the files to see which one is bindings etc.)

- import the three files

- have a look inside the main document. There is an entry "...location=xxx" (near the top, in tag import).

- copy the value of xxx

- goto to external definition Object of the bindings file

- paste the value of xxx in the source field

- have a look at the bindings file

- there is (also) an entry "...location=yyy"

- copy the value of yyy

- goto to external definition Object of the ports file

- paste the value of yyy in the source field

Now you should see the messages, if you create an message interface when trying to assign a message.

Hope thats not too short.

Regards,

Torsten

Former Member
0 Kudos

Okay, I don’t' have exactly the same problem like Frank. I've a WSDL from a non SAP system and it's only one file. I can upload the WSDL and on the "WSDL" tab no error is shown. But I can't see any message on the "Messages" tab. So I can't assign any message to my interface.

Should I start a new thread?

Former Member
0 Kudos

Hi Frank,

can you publish the WSDL in question here?

Then it is probably easier to find out about the problem.

Greetings

Stephan

Former Member
0 Kudos

I've the same problem. Here is my WSDL:

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>

<schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">

<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>

<complexType name="MSOBean">

<sequence>

<element name="installationName" nillable="true" type="xsd:string"/>

<element name="requestId" nillable="true" type="xsd:string"/>

<element name="returnCode" type="xsd:int"/>

<element name="returnMessage" nillable="true" type="xsd:string"/>

</sequence>

</complexType>

<complexType name="MSIBean">

<sequence>

<element name="password" nillable="true" type="xsd:string"/>

<element name="project" nillable="true" type="xsd:string"/>

<element name="requestId" nillable="true" type="xsd:string"/>

<element name="userId" nillable="true" type="xsd:string"/>

</sequence>

</complexType>

</schema>

</wsdl:types>

<wsdl:message name="actualizeRequest">

<wsdl:part name="inData" type="tns1:MSIBean"/>

</wsdl:message>

<wsdl:message name="actualizeResponse">

<wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>

</wsdl:message>

<wsdl:portType name="MSService">

<wsdl:operation name="actualize" parameterOrder="inData">

<wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>

<wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">

<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="actualize">

<wsdlsoap:operation soapAction=""/>

<wsdl:input name="actualizeRequest">

<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>

</wsdl:input>

<wsdl:output name="actualizeResponse">

<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="MSServiceService">

<wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">

<wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

No Idea.