In Message tab message missing while importing wsdl

[Former Member]

My scenario is a file to webservice to Idoc scenario.

1.We first send a request file to XI to start the BPM receive step.

2.the request message goes to a webservice and fetches a response structure and

3.The response structure maps to idoc and finally posts to R/3.

The java team has made the webservice and sent it to me but when I import it as a External definition I donu2019t get any message in the message tab.

So please suggest what I can do in this scenario.

[Former Member · Accepted solution]

Hi,

do you have selected 'From All Available Message Definitions' under Messages?

Regards

Patrick

[Former Member]

resolved.

[Former Member]

Hi all,

Lets get out of this confusion .

I have checked all suggestions, but sorry no problem with those issues and I have even paste the WSDL.

plz look into it and suggest what can be done.

[Former Member]

Hey

Probably you dont have the following tag in your WSDL

<element name="Message">

<complexType>

-

---

-

---

within this you will have all your simple types.

make sure you have closing tag as well </complexType>

Thanx

Aamir

[Former Member]

This message was moderated.

[Former Member]

>>It will be good if you can paste your wsdl here.

I didn't ask the question,someone else did:)

>>reward point if answer helps

I cant reward points:)

[Former Member]

I replied to his thread only I'll be happy to get points from you as well

cheers

amit

[Former Member]

well when you reply to some one,it will say on the top " in response to: <user name> ".

now even if you are replying to the actual post but it says something like "in response to: Aamir Suhail ".it will confuse everybody whether you are replying to the actual question asked or replying to what i said.

Thanx

Aamir

[Former Member]

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

<wsdl:definitions targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:impl="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:intf="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>

<schema targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns="http://www.w3.org/2001/XMLSchema">

<element name="generateInvoiceInformationResponse">

<complexType>

<sequence>

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

</sequence>

</complexType>

</element>

<element name="generateInvoiceInformation">

<complexType>

<sequence>

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

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

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

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

</sequence>

</complexType>

</element>

</schema>

</wsdl:types>

<wsdl:message name="generateInvoiceInformationResponse">

<wsdl:part element="impl:generateInvoiceInformationResponse" name="parameters"/>

</wsdl:message>

<wsdl:message name="generateInvoiceInformationRequest">

<wsdl:part element="impl:generateInvoiceInformation" name="parameters"/>

</wsdl:message>

<wsdl:portType name="GetInvoiceInformation">

<wsdl:operation name="generateInvoiceInformation">

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

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

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="GetInvoiceInformationSoapBinding" type="impl:GetInvoiceInformation">

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

<wsdl:operation name="generateInvoiceInformation">

<wsdlsoap:operation soapAction=""/>

<wsdl:input name="generateInvoiceInformationRequest">

<wsdlsoap:body use="literal"/>

</wsdl:input>

<wsdl:output name="generateInvoiceInformationResponse">

<wsdlsoap:body use="literal"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="GetInvoiceInformationService">

<wsdl:port binding="impl:GetInvoiceInformationSoapBinding" name="GetInvoiceInformation">

<wsdlsoap:address location="http://localhost:9083/EWSCWsAppQA/services/GetInvoiceInformation"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

[Former Member]

Hi,

The problem here is the size/length of the targetnamespace. Please ask your wsdl team to reduce the namespace length and it will work fine at this place.

<wsdl:definitions targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com"

Just try that and let me know. For your testing for time being just reduce the target namespace length from <wsdl:definitions targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" to lets say

<wsdl:definitions targetNamespace="http://bean.getinvoiceinformation" and import it and try.

thanks

amit

reward point if answer is useful

[Former Member]

Hi Amit,

Is there any issue with the length of the namespace while importing wsdl?

I dont know exactly.please elaborately describe before I approach the java team coz u know otherwise I can be in trouble if I have lack of information.

[Former Member]

Hi,

Yes there is restriction on the namespace which you can give in XI and I think the length is 60. So please tell the same to your java team. Hope this helps you out.

thanks

amit

Edited by: Amit Gupta on Jul 10, 2008 5:45 PM

[Former Member]

Hi,

Any luck on the same? Did it worked for you?

thanks

amit

[Former Member]

Hi Amit,

The java people are saying that thats a auto generated namespace and that would cause problem if they change the namespace.

so in that case is there any wayout ?

[Former Member]

Manually reduce the WSDL targetNamespace length it is ok.

This target namespace does not have any importance.

Check this OSS note for more information,

https://service.sap.com/sap/support/notes/901988

BR

Sameer

[Former Member]

Hi Abhishek,

You can try truncating the targetnamespace manually before importing the wsdl and can try. Personally I won't recomend this. If you try to create any namespace under software componnent also greater that 60 characters in XI it won't allow. You need to talk to your java guy and find some workqround from tehre side, it must be possible.I am not sure how targetnamespace is autogenerated.

If not possible you need to truncate explicitly and try, that's the only way left.

thanks

amit

reward point if solution helps

[Former Member]

Hi,

can you please paste your wsdl here.

thanks

amit