How to build generic RFC Calls using .NET technologies

[Former Member]

The DCOM Connector was generic, but the .NET isn't.

Is there a way to develop generic RFC Calls using .NET Technologies ?

[Former Member]

Hi Marcel,

I disagree. The DCOM Connector is not generic, but also a proxy based solution. Similar to the .NET Connector, you use the Object Builder to generate proxies and program against the generated, specific proxies in your COM client.

The only thing that probably could be called "generic" is the COM4ABAP, a RFC server program that makes COM components callable from within ABAP.

Regards,

Guangwei

[Former Member]

Hey Guangwei,

Sorry for questioning again. But is it possible to use the way Reiner described to get something like the COM4ABAP?

Or do you think, that SAP will send me a copy of the Source Code of the COM4ABAP. I would really need this for my Diploma Thesis. Perhaps you have any contact, where I can write to?

Regards,

Oliver

[reiner_hille-doering]

Oliver,

once again: SAP .NET Connector is NOT made to build infrastructures, but applications. Infrastructures need generic call features, but SAP offers and plans enough technologies and products that should be sufficient for any need. Look into XI (Exchange Infrastructure) and the coming ESA (Enterprise Serivice Architecture).

[Former Member]

Hi,

Although I have the best contact, you have to forget the idea that SAP would send you a copy of the source code of a released product, unless this product some day becomes a open source project.

Because there is no built-in support in the .NET Connector, the complexity and the amount of work required for you to build such a generic RFC invoker is far beyond the time frame of a Diploma Thesis.

Regards,

Guangwei

[Former Member]

Ok, I understand. Sorry for annoying you.

But I think I got a solution at all. And thats enough for me and my company....

Regards

[Former Member]

Li,

Good one...

[reiner_hille-doering]

For WAS 6.20 and higher you can use the Soap-entrance, e.g. you could fetch a WSDL at runtime, interpret it or create temporary Soap proxies and create a correct Soap-Request.

For older you could use LIBRFC32 with PInvoke.

Or you use XI server infrastructure - which is anyway the recommended approach for generic system access.