Create a connection

1In Administrator, select Connections.

2Click Add Connection.

3Select SAP Bapi and click Next.

4Enter the connection properties.

The following table describes the basic SAP Bapi connection properties:

Property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Runtime Environment	The name of the runtime environment where you want to run tasks. Select a Secure Agent, serverless, or elastic runtime environment.
Authentication	The authentication type to access the SAP system and process data through the SAP BAPI functions. Select the BAPI Connection authentication type and then configure the authentication-specific parameters.
Username	The user name with the appropriate user authorization to connect to the SAP account.
Password	The password to connect to the SAP account.
Host Name	The host name or IP address of the SAP server to which you want to connect.
Client	The client number of the SAP server. Get the required client number from the SAP system to which you want to connect.
Language	Language code that corresponds to the SAP language. Get the required language code from the SAP system to which you want to connect.
System Number	The system number of the SAP server. Get the required system number from the SAP system to which you want to connect.

The following table describes the advanced SAP Bapi connection properties:

Property	Description
SAP Additional Parameters	Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. See the following examples where you can use this field to configure additional parameters for the connection: - To create a load balancing connection, define the additional arguments listed in the following sample: GROUP=interfaces MSHOST=<Message server hostname> R3NAME=<System ID or name of SAP system> SAP infers the connection type based on the parameters that you specify. For example, if you define the GROUP, MSHOST, and R3NAME parameters, SAP infers the connection type as a load balancing connection. The GROUP parameter defines the group name of the SAP application server. The MSHOST parameter defines the host name of the SAP message server. The R3NAME parameter defines the system ID or name of the SAP system. - To commit data to the SAP system with each BAPI/RFC call, define the DOCOMMIT=true parameter. - To create a connection with the Secure Network Communication (SNC) protocol, define the required additional parameters. For more information, see How to configure the SAP Secure Network Communication protocol Informatica How-To Library article. If you specify a property both in the dedicated connection field and in the SAP Additional Parameters field, the value specified in the SAP Additional Parameters field takes precedence. For more information about SAP parameters, see the SAP documentation.
Jco Trace	Determines whether to track the JCo calls that the SAP system makes. Default is disable. By default, SAP doesn't store information about the JCo calls in a trace file. If you enable JCo trace, you can access the JCo trace file from the following directory: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<latest_version>\ICS\main\bin\rdtm

Property

Description

SAP Additional Parameters

Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client.

See the following examples where you can use this field to configure additional parameters for the connection:

- To create a load balancing connection, define the additional arguments listed in the following sample:

GROUP=interfaces
MSHOST=<Message server hostname>
R3NAME=<System ID or name of SAP system>

SAP infers the connection type based on the parameters that you specify. For example, if you define the GROUP, MSHOST, and R3NAME parameters, SAP infers the connection type as a load balancing connection. The GROUP parameter defines the group name of the SAP application server. The MSHOST parameter defines the host name of the SAP message server. The R3NAME parameter defines the system ID or name of the SAP system.

- To commit data to the SAP system with each BAPI/RFC call, define the DOCOMMIT=true parameter.
- To create a connection with the Secure Network Communication (SNC) protocol, define the required additional parameters.

For more information, see How to configure the SAP Secure Network Communication protocol Informatica How-To Library article.

If you specify a property both in the dedicated connection field and in the SAP Additional Parameters field, the value specified in the SAP Additional Parameters field takes precedence.

For more information about SAP parameters, see the SAP documentation.

Jco Trace

Determines whether to track the JCo calls that the SAP system makes.

Default is disable. By default, SAP doesn't store information about the JCo calls in a trace file.

If you enable JCo trace, you can access the JCo trace file from the following directory:

<Informatica Secure Agent installation directory>\apps\Data_Integration_Server\<latest_version>\ICS\main\bin\rdtm

The following table describes the basic SAP Table connection properties:

Property	Description
Runtime Environment	The name of the runtime environment where you want to run tasks. Select a Secure Agent, serverless, or elastic runtime environment.
Username	The user name with the appropriate user authorization to connect to the SAP account.
Password	The password to connect to the SAP account.
Client	The client number of the SAP application server. Get the required client number from the SAP system to which you want to connect.
Language	Language code that corresponds to the SAP language. Get the required language code from the SAP system to which you want to connect.

The following table describes the advanced SAP Table connection properties:

Property	Description
Saprfc.ini Path	Required. Local directory to the sapnwrfc.ini file. To write to SAP tables, use the following directory: <Informatica Secure Agent installation directory>/apps/Data_Integration_Server/ext/deploy_to_main/bin/rdtm
Destination	DEST entry that you specified in the sapnwrfc.ini file for the SAP application server. Use all uppercase letters for the destination. This property is required if you create the connection to write to SAP tables. If you enter the DEST entry in this field, do not enter the host name or IP address, and system number of the SAP application server in the Application Server and System Number fields.
Port Range	HTTP port range. The SAP Table connection uses the specified port numbers to connect to SAP tables using the HTTP protocol. Default range is 10000-65535. Enter a range in the default range, for example, 10000-20000. When a range is outside the default range, the connection uses the default range.
Test Streaming	Tests the connection. When selected, tests the connection using both RFC and HTTP protocol. When not selected, tests connection using RFC protocol.
Https Connection	When selected, connects to SAP through HTTPS protocol. To successfully connect to SAP through HTTPS, verify that an administrator has configured the machines that host the Secure Agent and the SAP system.
Keystore Location	Absolute path and file name of the keystore file to connect to SAP. Specify both the path and file name in the following format: <Directory>/<Keystore file name>.jks
Keystore Password	The destination password to access the keystore file.
Private Key Password	The export password to access the .P12 file.

After you configure a connection to SAP Table in IDMC Administrator, you can view the source connection name for that connection on the Data Profiling and Quality tab of the Configuration page in Metadata Command Center.

5Click Test to test your connection to the source system.

6Click Save.