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. |
Type | SAP BW BEx Query |
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. This property is not supported by Data Ingestion and Replication. When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. For information about how to configure and use a secrets manager, see Secrets manager configuration. |
Runtime Environment | The name of the runtime environment where you want to run tasks. Select a Secure Agent or serverless runtime environment. For more information about how to configure a serverless environment, see Use the serverless runtime environment. |
Authentication | The authentication type to access SAP BW and read SAP BW BEx queries. Select the SAP authentication type and then configure the authentication-specific parameters. |
Username | The user name with the appropriate user authorization to connect to the SAP BW account. |
Password | The password to connect to the SAP BW account. |
Connection property | Description |
|---|---|
Host name | The host name or IP address of the SAP BW server to which you want to connect. |
System number | The system number of the SAP BW server. Get the required system number from the SAP system to which you want to connect. |
Client | The client number of the SAP BW 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. |
Property | Description |
|---|---|
Trace | Determines whether to track the JCo calls that the SAP system makes. Enter one of the values between 0 and 8. By default, SAP doesn't store information about the JCo calls in a trace file. Default is 0. For more information about trace level values, see Setting up an SAP Java Connector (SAP JCo) and Related Traces. You can access the trace files from the following directories:
|
Additional parameters | Additional JCo connection parameters that you can use when you read SAP BW BEx queries from SAP BW. You can enter multiple JCo connection parameters, separated by a semicolon, in the following format: <parameter name1>=<value1>;<parameter name2>=<value2>;<parameter name3>=<value3>.... For example, if you want to create an SAP SNC connection, enter the following additional parameters: SNC_MODE=1;SNC_QOP=3;SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_LIB=C:\SNC_11\sapcrypto.dll;TRACE=1 |
SAP Additional Parameters | Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. Specify the required RFC-specific parameters and connection information that enable the Secure Agent to connect to SAP. For example, you can specify the SNC connection parameters as additional arguments listed in the following sample: GROUP=interfaces ASHOST=<Application server hostname> SYSNR=20 SNC_MODE=1 SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization> SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization> SNC_LIB=<Secure Agent installation directory>/apps/server/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows> X509CERT=<X509 certificate> TRACE=2 For more information about RFC-specific parameters, see the SAP documentation. Note: If you specify a parameter in both the SAP Additional Parameters and Additional parameters fields, the value specified in the SAP Additional Parameters field takes precedence. |
Connection property | Description |
|---|---|
Username | The user name with the appropriate user authorization to connect to the SAP BW account. |
Password | The password to connect to the SAP BW account. |
Host name | The host name or IP address of the SAP BW server to which you want to connect. |
System number | The system number of the SAP BW server. Get the required system number from the SAP system to which you want to connect. |
Client | The client number of the SAP BW 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. |
Property | Description |
|---|---|
Message host name | Required. The host name of the SAP message server to which you want to connect when you use a load balancing connection. |
R3 name/SysID | Required. The system ID of the SAP message server to which you want to connect when you use a load balancing connection. |
Group | Required. The name of the SAP logon group through which you want to connect when you use a load balancing connection. |
Trace | Determines whether to track the JCo calls that the SAP system makes. Enter one of the values between 0 and 8. By default, SAP doesn't store information about the JCo calls in a trace file. Default is 0. For more information about trace level values, see Setting up an SAP Java Connector (SAP JCo) and Related Traces. You can access the trace files from the following directories:
|
Additional parameters | Additional JCo connection parameters that you can use when you read SAP BW BEx queries from SAP BW. You can enter multiple JCo connection parameters, separated by a semicolon, in the following format: <parameter name1>=<value1>;<parameter name2>=<value2>;<parameter name3>=<value3>.... For example, if you want to create an SAP SNC connection, enter the following additional parameters: SNC_MODE=1;SNC_QOP=3;SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization>, C=<Country>;SNC_LIB=C:\SNC_11\sapcrypto.dll;TRACE=1 |
SAP Additional Parameters | Additional SAP properties that the Secure Agent uses to connect to the SAP system as an RFC client. Specify the required RFC-specific parameters and connection information that enable the Secure Agent to connect to SAP. For example, you can specify the SNC connection parameters as additional arguments listed in the following sample: GROUP=interfaces ASHOST=<Application server hostname> SYSNR=20 SNC_MODE=1 SNC_PARTNERNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization> SNC_MYNAME=p:CN=<Common name>, OU=<Organizational unit>, O=<Organization> SNC_LIB=<Secure Agent installation directory>/apps/server/bin/<libsapcrypto.so for Linux/sapcrypto.dll for Windows> X509CERT=<X509 certificate> TRACE=2 For more information about RFC-specific parameters, see the SAP documentation. Note: If you specify a parameter in both the SAP Additional Parameters and Additional parameters fields, the value specified in the SAP Additional Parameters field takes precedence. |