Setting up an RFC Destination for a RFC Server

There are two methods for setting up RFC destinations:

Below are the methods with a comparison of their advantages and disadvantages:

	Method A	Method B:
Advantages	The program only runs when it is actually needed. The system is more stable. You can usually continue working even if the conversion server is restarted.	Works on all operating systems. Simple installation.
Disadvantages	Only works when the conversion server is running on UNIX. Installation is very complex.	Program always runs in the background. If the program is halted, for example, because the conversion server has been restarted, it must be restarted.
Use	This method is highly recommended if you have a conversion server running UNIX.	This method is best for conversion servers using Microsoft Windows NT.

Method A

Method B:

Advantages

The program only runs when it is actually needed.
The system is more stable.
You can usually continue working even if the conversion server is restarted.

Disadvantages

Program always runs in the background.

If the program is halted, for example, because the conversion server has been restarted, it must be restarted.

Use

This method is highly recommended if you have a conversion server running UNIX.

This method is best for conversion servers using Microsoft Windows NT.

The following information is required for both methods:

Information	Meaning
GATEWAY_HOST	Name of the computer where the SAP Gateway is running (for example hs0009)
GATEWAY_SERVICE	Gateway Service you are using (such as sapgw01)
RFC_SERVER	Complete path name of the program on the conversion server where you want to set up the RFC destination (for example /usr/converter/All2txt/StartConvUtil)