Component family |
Business |
|
Function |
tSAPConnection opens a connection |
|
Purpose |
tSAPConnection allows to commit a |
|
Basic settings |
Property type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-in: No property data is |
|
|
Repository: Select the Repository |
|
SAP JCO Version |
Select an SAP Java Connector version from the drop-down list: Note that the opened SAP connection can be reused by tSAPBapi and tSAPTableInput only if talend |
|
Connection configuration |
Client type: enter your usual SAP Userid : enter user login. Password: enter password.
Language: specify the
Host name: enter the IP address of
System number: enter the system To enter the password, click the […] button next to the |
|
Specify a shared |
Select this check box, and then specify the shared destination in the Shared destination name field. The Shared This option is available only when you select sap jco 3.* Besides specifying the Shared destination name in the WarningIf you use the component’s own connection configuration, your SAP connection will be |
|
SAP Properties |
If you need to use custom configuration for the SAP system being
|
Advanced settings |
ftp and http based |
To invoke from the SAP server a function which requires document If this check box is selected but SAPGUI has not been installed, WarningThis check box will not be available if you select Use an existing connection check box |
tStatCatcher Statistics |
Select this check box to collect log data at the component |
|
Global Variables |
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
This component is more commonly used with other tSAP* components, |
|
Limitation |
n/a |
For a related scenarios, see Scenario 1: Retrieving metadata from the SAP system and Scenario 2: Reading data in the different schemas of the RFC_READ_TABLE
function.