WSDL for PI 7.1 wsdl:service

[Former Member]

Hi ALL,

i have a sender SOAP to receiver ABAP proxy scenario.

i got the WSDl file from sender agreement menu Display WSDL option and gave the WSDL to the to the .Net team..

they are telling me the WSDL file has some <wsdl:service name="XI_c23f13a4efbc3a7fad8fa18b9ad71bcc_Service"> and this is a ramdon number ..is this a issue .. ?

is there any other method better than this to Create WSDL for them ..? is i create WSDL using any other method this random number will not come ..?

thanks

Souz

[Former Member · Accepted solution]

Add following property in exchange profile to switch to the new naming convention:

[IntegrationBuilder]->[IntegrationBuilder.Directory]->

Property name: com.sap.aii.ibdir.wsdl.servicename.bitfield

Property type: Integer

Value: 0

This will change the service name to the name of the service interface ..

[samiullah_qureshi]

It seems problem is not with WSDL.

If you want to generate WSDL from another way (other than from sender agreement), you can get it from ID -> Tools -> Display WSDL

In the URL provide following URL:-

http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

Where

host - server host name/ip

port - Server port number

party - Name of party for sender service(if any)

service - Sender service

channel - soap sender comm channel

Select the appropriate interface and service name in subsequent screens.

Finally you will get WSDL generated for your interface.

[prateek]

This is proper way of generating wsdl and wsdl:service shouldn't be a problem for the .net team. Are they complaining about any issue?

Regards,

Prateek

[Former Member]

yes they are saying..

xi_ + random number prefix rather than proper service name.

thanks

Souz

[prateek]

Try regenerating the wsdl with the Display WSDL option in PI 7.1. Do you have multiple operations attached with this Service Interface?

Regards,

Prateek

[Former Member]

i have only one operation in that WSDL file.

thanks

Souz

[Former Member]

Service name is just a place holder in the WSDL file.

The operation name inside the schema on the other hand is what will give the SOAP Message it's proper designation.

This service name will only affect the .NET stub or Java stub produce. In no other way will it affect the SOAP message.