Skip to Content

How to build generic RFC Calls using .NET technologies

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

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Aug 13, 2004 at 09:43 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 13, 2004 at 03:10 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.