RFC Server permanent registration

[Former Member]

Hi all,

I have a RFC server application used to handle the communication between our SAP and another external system. This application is written in C# and runs on a Windows Server 2008 box.

When starting the application it registers itself at the SAP Gateway. However, after a few day's that the application has not been used it disconnects from the gateway and RFC call made to the application get a dump error.

Now my question is this:

What is the most effective method of ensuring that the RFC Server application never disconnects from the sap system?

Additionally:

What is the timeout for registered programs before they disconnect?

I have considered altering the server to self restart once a day or week.

Perhaps for SAP to start the application remotely (Don't even know if this is possible)

Even writing the RFC server as an windows service.

Has anyone encountered a similar situation and could suggest a permanent fix?

Thanks for your time!

Ado

[former_member197445 · Accepted solution]

Ado,

Your last consideration is absolutely the best one -- the .NET program should be a Windows Service if you want it to be available at all times.

To answer your other question, there is no set timeout, I don't believe.  It's probably the .NET program terminating or running out of memory on the server or something like that.

It sounds like you are using this as an interface.  Is it data that can be transferred as a flat file?  If so there might be other options available.

In any case, Windows Service is the way to go for long-running processes in .NET.

More info here:
http://msdn.microsoft.com/en-us/library/y817hyb6

[Former Member · Accepted solution]

Hi Case,

The program does act as interface between two systems by relaying a bit stream. So it's not too complex.

I'm only afraid that issues might arise when writing the program as a service. Does SAP support this?

Thank you for your reply.

Ado

[former_member197445 · Accepted solution]

No need to worry.  SAP definitely supports this.  See SAP Help document for examples.  Particularly the .NET Program as Server section.