cancel
Showing results for 
Search instead for 
Did you mean: 

How to consume XI web service from .net

Former Member
0 Kudos

Experts,

I created web service in XI and generated WSDL file through integratin directory. I sent WSDL file to legacy system consultants who is using .net to consume our services.

In .net side they have uploaded our WSDL file(which is stored locally in their machine). But when they trying to call our webservice they are getting the error like "Unable to find the reference". So anybody have idea to call webservice created in XI from .net. If you share some document for calling web services from .net created in XI(scenario will be .net-> xi -> sap) , will be of great help.

Regards,

Santhosh

Accepted Solutions (1)

Accepted Solutions (1)

former_member200962
Active Contributor
0 Kudos

check if the below helps you in any way:

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]

scenario will be .net-> xi -> sap

just make a search in this forum with .net and you will get lots of threads with .net xisap integration.

As an XI developer things you should take care of:

the wsdl that you have provided to .net developer should be pointing to the accurate location....

this is entirely dependent on the URL that you give while generating the wsdl (from ID)....

Do not use Propose URL option in the wizard; also do not use the default URL present there....

Below URL format needs to be used:

http://hostname:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>

party is optional, instead of hostname you can also give the IP address of XI server

Regards,

Abhishek.

Edited by: abhishek salvi on May 9, 2009 7:33 PM

Former Member
0 Kudos

Ask the .net consultants to check the configuration file for this URL format...

<Url>host:port/XISOAPAdapter/MessageServlet?senderParty=_optional_ senderService=_ServiceName_ interface=_Interface_name_ receiverParty=_optional_receiverService=_Optional_;interfaceNamespace=_InterfanceNameSpace_</Url>

And most of the times the problem occures with User ID and Password...

Answers (1)

Answers (1)

phanikumar_akella
Participant
0 Kudos

Hi Santosh,

Most of the time the issue is with the creation of WSDL. please check once carefully and follow the below procedure to create WSDL use this URL format. (remember...if you not using "party" ensure that you use colon as shown ":service:channel".)

http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel while defining web service.