Data Integration Connections

Back Next

Advanced settings

The following table describes the advanced 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