Hi Stephen, I've just read the guide you sent me and I notice that the author uses the WSDL generated by the SAP WebService to create the .NET proxy classes. The problem I'm facing is exactly that: when I access the address they sent, I see the message about "Message Servlet" that I sent before instead of the WSDL.
Maybe the problem is in the webservice they published. I'm checking it out now. Thanks, Guilherme On 8 April 2010 16:24, Stephen Russell <[email protected]> wrote: > On Thu, Apr 8, 2010 at 2:09 PM, Guilherme Utrabo <[email protected]> wrote: > > Hello there, > > > > My .NET application will need to consume a WebService published at SAP > XI. > > I've consumed .NET WebServices several times, but it's my first time with > > SAP. > > > > In order to consume a .NET WebService I follow these steps: > > 1. Find the service address (http://server:port/Service.asmx?WSDL) > > 2. Add as "Service Reference" and that's it: the VS generates the proxy > > classes, etc. > > > > This time I've received an address that follows this pattern: > > http://server:port > /XISOAPAdapter/MessageServlet?channel=:BS_SYSTEM:CC_SOAP_SYSTEM_METHOD_Sender > > > > I've tried to add as a "Service Reference" but it didn't works. > > How do I do to consume this WebService from my .NET application? > --------- > > Good start on SAP & .NET > > <http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2131> > > -- > Stephen Russell > > Sr. Production Systems Programmer > CIMSgts > > 901.246-0159 cell > > > -- > To unsubscribe, reply using "remove me" as the subject. > -- Guilherme Utrabo
