Consuming SAP XI WebService

1,318 views
Skip to first unread message

Guilherme Utrabo

unread,
Apr 8, 2010, 3:09:02 PM4/8/10
to dotnetde...@googlegroups.com
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?

Thanks,
Guilherme Utrabo

Guilherme Utrabo

unread,
Apr 8, 2010, 3:48:48 PM4/8/10
to dotnetde...@googlegroups.com
Additional information:

They told me that this address refers to WSDL, but when I open it from the browser I receive the following message:


Message Servlet is in Status OK

Status information:

Servlet com.sap.aii.af.mp.soap.web.
MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#16 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0
ModuleProcessorRemote not instantiated
--
Guilherme Utrabo

Stephen Russell

unread,
Apr 8, 2010, 3:24:26 PM4/8/10
to dotnetde...@googlegroups.com
---------

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

Guilherme Utrabo

unread,
Apr 9, 2010, 7:29:28 AM4/9/10
to dotnetde...@googlegroups.com
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





--
To unsubscribe, reply using "remove me" as the subject.



--
Guilherme Utrabo

Stephen Russell

unread,
Apr 9, 2010, 9:22:00 AM4/9/10
to dotnetde...@googlegroups.com
On Fri, Apr 9, 2010 at 6:29 AM, Guilherme Utrabo <utr...@gmail.com> wrote:
> 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.
-----------------

Good luck.

Reply all
Reply to author
Forward
0 new messages