Skip to main content Skip to complementary content

Installing Talend SAP RFC Server using Talend Installer

Before you begin

If you are planning on installing Talend SAP RFC Server on a separate server, add the line sapgw00 3300/tcp to /etc/services.

Procedure

  1. Select the Talend SAP RFC Server check box in the Select Components step of the installation process.
  2. Select the Configure SAP RFC Server check box in the SAP RFC Server parameters step of the installation process.
  3. In the SAP gateway section, enter the host name and other identifiers for the SAP system. Contact the administrator of the SAP system for details if you do not already have all this information to hand.
  4. In the Logon information section, enter the username and password that you use to connect to the SAP system.
  5. In the Language code field, enter a two-letter language code to specify the language used by the SAP system in its communications with your machine, for instance when displaying error messages or metadata.
  6. In the System number field, enter the System Number.
  7. In the JMS broker URL field, enter the host name or IP address of the JMS Broker.
  8. In the Library folder field, click the folder icon and browse to the location on your local machine where the sapjco3.jar file is stored. This proprietary library is required for the Talend SAP RFC Server to operate correctly.
  9. Click Next to proceed to the next step in the installation process.

Results

Once the installation is completed, the Talend SAP RFC Server is installed under the <$INSTALLDIR>/sap-rfc-server directory, where <$INSTALLDIR> is the installer installation directory.

What to do next

Before starting Talend SAP RFC Server, you can configure the configuration files to enable some additional features of the server according to your needs. For more information, see Configuring the tsap-rfc-server.properties file and Configuring an SAP connection configuration file.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here