Setting up Registration on the SAP Gateway  

Use

You are making the settings for using Method B that registers the RFC connection on the SAP gateway.

See also: Setting up an RFC Destination for a RFC Server

Prerequisites

The following information is required for method B:

Information

Description

ProgramID

ID where the RFC server can be identified.
Select and ID for each RFC server (such as converter.All2txt.1)

Procedure

Replace the text between < and > with the values used in your enterprise.

<GATEWAY_HOST> Replace using the name of the computer where your SAP gateway is running.

  1. Edit <RFC_SERVER>.

When using the example programs (RunConvUtil.bat or RunConvUtil) you must include the following information in the file:

set ProgramID=<ProgramID>

set GATEWAY_HOST=<GATEWAY_HOST>

set GATEWAY_SERVICE=<GATEWAY_SERVICE>

(RunConvUtil.bat) or

ProgramID=<ProgramID>

GATEWAY_HOST=<GATEWAY_HOST>

GATEWAY_SERVICE=<GATEWAY_SERVICE>

(RunConvUtil)

Otherwise the RFC server must be called with the following parameters:
-a <ProgramID> -g <GATEWAY_HOST> -x <GATEWAY_SERVICE>

  1. Start <RFC_SERVER>.
  1. Verify the messages on the screen (RunConvUtil.bat) and in the output files (RunConvUtil).

After 30 seconds or more it is unlikely that an error occurs.

Otherwise verify whether <GATEWAY_HOST> and <GATEWAY_SERVICE> are set correctly and whether the gateway server is operational.

  1. Start the transaction SM59 (Display and maintenance of RFC destinations) on your SAP System

Enter <ProgramID> as the value for Program-ID.

Enter <GATEWAY_HOST> as Gateway host and as <GATEWAY_SERVICE> Gateway service. Confirm the entry and save the document.

  1. Select Test connection.

Verify whether <RFC_SERVER> is still running and if the data <ProgramID>, <GATEWAY_HOST> and <GATEWAY_SERVICE> are the same as the data you entered in the <RFC_SERVER>.

Conversion can only be executed when the connection test is successful.