The configuration file tsap-rfc-server.properties for
Talend SAP RFC Server is created by the
installer under the $TSAPS_HOME/conf directory (where
$TSAPS_HOME corresponds to the directory where the Talend SAP RFC Server has been installed or
extracted). Before starting Talend SAP RFC Server, you can configure the file to enable some additional features of the server
according to your needs.
- 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.
To enable user authentication, you need to uncomment the following three parameters in the configuration file and set their values.
# File system directory containing jaas authentication configuration rfc.server.jms.login.config=conf/user-authentication/login.config # A jaas username used to authenticate a publisher or sender rfc.server.jms.login.username=talenduser # A jaas password used to authenticate a publisher or sender rfc.server.jms.login.password=talendpassword
Note that the username and password values will be used by the tSAPIDocReceiver component or the tSAPDataSourceReceiver component to connect to the Talend SAP RFC Server and the values must also exist in the $TSAPS_HOME/conf/user-authentication/users.properties file. In this file, each row represents a username and password pair, where the username value is on the left side of the equals sign and the password value is on the right side of the equals sign.
# username=password talenduser=talendpassword
Note that if you don't enable user authentication, the tSAPIDocReceiver component or the tSAPDataSourceReceiver component can also connect to Talend SAP RFC Server without setting the value for their user and password fields.
To enable the SSL transport mechanism, you need to copy the key store file for SSL to the $TSAPS_HOME/conf folder and then uncomment the following two parameters, the path to the key store file and the password for the key store file, in the configuration file and set their values.
# The path to a key store for SSL rfc.server.jms.ssl.keystore.path=conf/mybroker.ks # A password for a key store for SSL rfc.server.jms.ssl.keystore.password=talendkeystore
To set up persistence for SAP IDocs, you need to uncomment the following parameter in the configuration file and set its value to
# Whether JMS messages are persisted or not rfc.server.jms.persistence=true
To store SAP IDocs in durable queues in Talend SAP RFC Server, you need to uncomment the following parameter in the configuration file and set its value to
# Whether JMS messages should be replicated in durable queues rfc.server.jms.replicate.in.durable.queues=true
This way, the Talend SAP RFC Server will keep a copy of all IDocs received in queues named after the IDoc. This is meant to serve the tSAPIDocsReceiver component in batch mode. When the receiver runs, it collects all IDocs stored in the durable queues since the last time it ran.
By default, messages are kept in the queues for up to seven days. You can change the retention period by uncommenting the following parameter in the configuration file and updating its value to meet your own requirement. In this example, the retention period is extended for ten days.
# ISO8601 retention period for JMS messages in durable queues rfc.server.jms.durable.queues.retention.period=P10D
To connect to a remote broker instead of an embedded one, you need to uncomment the following parameter and set the URL of the remote broker.
# when active, connects to a remote broker instead of an embedded one rfc.server.remote.broker.url=tcp://localhost:61616
To expose the broker's services to JMX, you need to uncomment the following parameter and set its value to
# Sets whether or not the Broker's services should be exposed into JMX or not. rfc.server.jms.jmx=true