# tSAPDataSourceReceiver Standard properties

These properties are used to configure tSAPDataSourceReceiver running in the Standard Job framework.

The Standard tSAPDataSourceReceiver component belongs to the Business family.

The component in this framework is available in all Talend products.

## Basic settings

| Failover | Select this option to use the RFC server failover feature. The RFC server failover feature is implemented by deploying brokers using the rfc.server.remote.broker.url parameter in *Remote broker section* of the tsap-rfc-server.properties file. After selecting this option, you need to provide the IP addresses and the port numbers of the brokers in the Host and Port columns in the table that appears. You can find the IP addresses and the port numbers of the brokers by checking the rfc.server.remote.broker.url parameter in *Remote broker section* of the tsap-rfc-server.properties file. See *Configuring the tsap-rfc-server.properties file* for related information.<br><br>Information noteNote: This option is available only if you have installed the R2021-01 Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator. |
| --- | --- |
| Talend SAP RFC Server host | Enter the IP address of the Talend SAP RFC server, or localhost if it is installed on your local machine. |
| Port | Enter the port used by the Talend SAP RFC server. |
| User and Password | Enter the username and password used to connect to the Talend SAP RFC server.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Use SSL Transport | Select this check box to use the SSL transport mechanism. For more information about SSL transport, see [SSL Transport Reference](http://activemq.apache.org/ssl-transport-reference.html). |
| Datasource name | Specify the name of the Data Source system. |
| Mode | Select one of the following modes for using this component from the<br>drop-down list.<br><br><ul> <li> <div> <span>Keep running forever</span>:										Select this mode if you want this component to keep										listening for the coming data requests until you stop the										execution of the Job. With this mode selected, you can also										specify the following two properties:<ul> <li> <p> <span>Maximum duration												(seconds)</span>: Specify the period of time												(in seconds) for which the Job should continue to												consume any data requests on the RFC Server. Once												this time limit is reached, the Job stops												consuming and closes the connection to the RFC												Server.</p> </li> <li> <p> <span>Maximum number of data												to consume</span>: Specify the maximum number												of data requests to be consumed by the Job. Once												this limit is reached, the Job stops consuming and												closes the connection to the RFC Server.</p> </li> </ul> </div> </li> <li> <p> <span>Batch (consume all data available											then terminate)</span>: Select this mode if you want										the Job to stop automatically once all data requests										available on the RFC server are consumed. With this mode										selected, you can also specify in the <span>Sleep time (seconds)</span> field the sleeping										time, in seconds, which corresponds to the time the process										will wait for the first message to be read.</p> </li> </ul> |
| Schema and Edit schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion. If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |

## Advanced settings

| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at the Job level<br>as well as at each component level. |
| --- | --- |

## Global Variables

| Global Variables | ERROR\_MESSAGE: the error message generated by the component when an<br>error occurs. This is an After variable and it returns a string. This variable functions<br>only if the Die on error check box<br>is cleared, if the component has this check<br>box.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a<br>variable, press Ctrl + Space to<br>access the variable list and choose the variable to use from it.<br><br>For further information about variables, see *Talend Studio*<br>*User Guide*. |
| --- | --- |

## Usage

| **Usage rule** | This component is usually used as a start component of a Job or<br>subJob and it always needs an output link. |
| --- | --- |
| Limitation | Specific jar and dll files provided by SAP must be added to your Studio and the workstation hosting your Studio. The exact procedure varies among platforms such as 32-bit or 64-bit Windows or Linux.<br><br><ul> <li> <p>For more information, see <cite>How to install the SAP Java Connector</cite> and the "Centralizing SAP metadata" section in <cite> <span>Talend Studio</span> User Guide</cite>.</p> </li> <li> <p>You can find an example of how to install SAP Java connectors in <span>Talend Help Center</span> (<a href="https://help.talend.com/" target="_blank">https://help.talend.com</a>) and the "Centralizing SAP metadata" section in <span>Talend Studio</span> User Guide.</p> </li> </ul> |