Skip to main content Skip to complementary content

Configuring an SAP connection configuration file

You can connect to multiple SAP systems through a Talend SAP RFC Server by creating an SAP connection configuration file under the $TSAPS_HOME/conf/named-connectiond directory for each of the connections (where $TSAPS_HOME corresponds to the directory where the Talend SAP RFC Server has been installed). An SAP connection configuration file consists of three sections. Before starting Talend SAP RFC Server, you can configure SAP connection configuration files to enable some additional features of the server according to your needs.

Information noteNote:
  • Talend SAP RFC Server doesn't support the SAP cluster configuration.
  • Any change of the configuration file requires a restart of the Talend SAP RFC Server.
  • You can customize the path to the $TSAPS_HOME/conf/named-connectiond directory by setting the named.connections parameter in the tsap-rfc-server.properties file.

Feature section

The Feature section details the connection information to enable features involving the Talend SAP RFC Server.

  • feature.idoc.enabled: Enables the IDoc feature.
  • feature.idoc.transactional: Enables the transactional management feature.
    • Reports the entire transaction as a failure to SAP when a message does not get delivered to the JMS broker.
    • Automatically reconnects to the remote JMS broker.
  • feature.idoc.transactionAbortTimeOut: Refers to the IDoc package processing timeout value in milliseconds.
  • feature.idoc.mock.enabled: Replaces the IDoc receiver with a mock, which produces an IDoc package every 5 seconds. Not used for SAP servers.
  • feature.bw_source_system.enabled: Enables the BW source system feature.
  • feature.bw_source_system.mock.enabled: Replaces the BW source with a mock, which produces a BW data request every 5 seconds. Not used for SAP servers.
  • feature.streaming.enabled: Enables the streaming mode features (requires a remote connection to a Kafka cluster).
    Information noteImportant: Install a Kafka server version 2.1 onwards prior to using the streaming mode feature. For more information, see the Apache Quick Start Guide.
  • feature.streaming.timeout: Refers to the timeout value for the streaming to start.
  • feature.streaming.limit.parallel: Maximum number of data streams that can be extracted in parallel. A value of -1 does not limit the number of data streams.
  • feature.streaming.threadCount: The number of threads for data extraction. The default is 2.
  • feature.streaming.topic.partitionCount: Kafka topic partition count. The default is 2.
  • feature.streaming.topic.replicationFactor: Kafka topic replication factor. The default is 1.

SAP JCO server section

The SAP JCO Server section details the SAP information the RFC server needs to connect through RFC calls to SAP.

  • jco.server.gwhost: SAP gateway host on which the RFC server should be registered (mandatory).
  • jco.server.gwserv: SAP gateway service, which is the port used for the registration (mandatory).
  • jco.server.progid: Identifier for IDoc on the gateway and as the destination in the SAP system (mandatory).
  • jco.server.connection_count: Number of connections registered at the gateway (mandatory).
  • jco.server.worker_thread_count: Number of threads that can be used by the JCOServer instance.
  • jco.server.worker_thread_min_count: Number of threads that are kept running by the JCOServer instance.
  • jco.server.trace: Enables or disables the RFC trace, this is useful for debugging.
  • destination_name=RFC destination : Sets the RFC destination. You need to set this parameter when the RFC destination differs from its program ID. With this parameter enabled, the value of this parameter is used as the import parameter IV_RFC_DESTINATION of BAPI /CMT/TLND_TABLE_JOIN_STREAM. Otherwise, the program ID (jco.server.progid) is used as the import parameter.

SAP JCO client section

The SAP JCO client section includes the connection information to the SAP ABAP server. You need all the options provided and you can use the credentials of the user with RFC call rights.

Set the password in clear text, which is then overwritten with the # number sign value when the Talend SAP RFC Server starts.

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