Show TOC

 Setting Up the Program Start Using SAP Gateway

Use

Making the settings for using method A to make SAP Gateway start a program that opens the RFC connection.

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

Prerequisites

The following information is required for method A :

Information

Description

GATEWAY_USER

Name of the user who started SAP Gateway on GATEWAY_HOST

CONVERTER_HOST

Name of conversion server (such as hs100)

Procedure

In the following procedure, you replace the expression between < and > with the values used in your enterprise.

Example Example

<GATEWAY_HOST> Replace with the name of the computer where your SAP Gateway is running.

End of the example.

  1. Create a user with the name <GATEWAY_USER> on the conversion server.

  1. Log on to the conversion server with the user <GATEWAY_USER>.

  1. Create or modify the file $HOME/.rhosts .

  1. Add the line <GATEWAY_HOST> to the file $HOME/.rhosts .

  1. Set the access authorization for the file using the following values: -rw-r--r--

    (for example, with chmod 644 $HOME/.rhosts).

If problems occur, read the main page for the command remote login . Use the command man remsh or man rsh , depending on the computer. Or contact a UNIX specialist.

In some cases the Gateway computer must entered twice (in two lines) in the file $HOME/.rhosts ; once with and once without the domain name.

Example Example

hs0009

hs0009.sap-ag.de

End of the example.

  1. Set the access authorization for <RFC_SERVER> so that <GATEWAY_USER> is authorized for at least r- and x- .

Example Example

chmod 755 <RFC_SERVER>

End of the example.

  1. Give the user <GATEWAY_USER> authorization to write to the files and directories on which the <RFC_SERVER> writes.

If you are using the SAP template program, you must give authorization to the <GATEWAY_USER> to write to the directories where <RFC_SERVER> is located.

  1. Start the transaction SM59 ( Display and maintain RFC destinations ) on your system

  • Choose Create and enter any name in the RFC destination field, for example CONVERTER_ALL2TXT.

  • Enter T as the value for Connection type .

  • Enter a description and confirm your entries.

  1. Choose the value Start on Explicit Host as Activation type .

  • Enter the value <RFC_SERVER> for Program and <CONVERTER_HOST> for Target machine .

  • Enter <GATEWAY_HOST> for Gateway host and <GATEWAY_SERVICE> for Gateway service . Confirm the entry and save the data.

  1. Choose Test connection .

  • Everything is in order if you see the connection data with the transfer times.

  • If, after a while, you see an error message marked in red , you need to find the error.

Note Note

There are the two following causes for errors:

End of the note.

  • Error A:

    The program <RFC_SERVER> could not be started.

  • Error B:

    No link for the started program.

To determine the cause of the error, insert in program <RFC_SERVER> the command to create files, such as touch $HOME/ConvUtilstartet. If the program could be started, the problem is caused by error B. In this case, check the RFC destination (transaction sm59, entries <GATEWAY_HOST> and <GATEWAY_SERVICES>).

No files exist when:

  • The user <GATEWAY_USER> does not have authorization to write to the files.

  • Start using remsh or rsh was unsuccessful (error A).

Recommendation Recommendation

Check the procedure. You can find information in the UNIX help ( man remsh or man rsh ).

Conversion can only occur if the connection test is free of errors.

End of the recommendation.