Connectors and Connections

Back Next

SAP HANA Database Ingestion connection properties

To define an SAP HANA Database Ingestion connection, configure the connection properties. You can use this connection for sources in

database ingestion and replication

tasks configured in Data Ingestion and Replication.

The following table describes the SAP HANA connection properties:

Connection property	Description
Connection Name	A name for the connection. This name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + - Spaces at the beginning or end of the name are trimmed and are not saved as part of the name. Maximum length is 100 characters. Connection names are not case sensitive.
Description	An optional description for the connection. Maximum length is 255 characters.
Runtime Environment	The name of the runtime environment where you want to run database ingestion and replication tasks. You define runtime environments in Administrator .
User Name	The user name for connecting to the SAP HANA instance. Enter the user name in the same case as in the database user name specified in SAP HANA.
Password	The password for connecting to the SAP HANA instance.
Host	The name of the machine that hosts the SAP HANA database server.
Port	The port number for the SAP HANA server to which you want to connect. Default is 30015.
Database Name	The SAP HANA source database name.
Advanced Connection Properties	Optional advanced properties for the SAP HANA JDBC driver, which is used to connect to the SAP HANA source. If you specify more than one `property`=`value` entry, separate them with an ampersand (&). The JDBC connection properties that you can enter in this field are described in the SAP JDBC Connection Properties documentation. For example: encrypt=true.
Capture Type	Select one of the following options to indicate the capture method that database ingestion incremental load jobs use to capture change data from SAP HANA databases: Trigger Based . Capture change data from SAP HANA source tables in the schema by using AFTER DELETE, AFTER INSERT, and AFTER UPDATE triggers. The triggers get before images and after images of DML changes for each source table and write entries for the changes to the PKLOG and shadow _CDC tables. Log Based . Capture change data from the SAP HANA database logs. Default is Trigger Based.
Log Clear	Required for incremental loads. Depending on the capture type, set this property as follows: For Trigger Based change capture, enter the time interval, in days, after which the PKLOG table entries and shadow _CDC table entries are purged. The purging occurs only while an incremental load job is running. Valid values for a database ingestion job are 0 to 366. Any positive value in this range cause automatic housekeeping to run while the incremental job is running. Default is 14. A value of 0 means that the table entries are not purged. For manual housekeeping, enter 0 and use your in-house process. Any value outside the range of 0 to 366, including a negative number or non-numeric value, causes database ingestion jobs that use the connection to fail with the following error: LogClear contains a non numeric number. Caused by: LogClear contains a non numeric number. For Log Based change capture, enter the number of days for which data records are stored in the HANA or Oracle database cache before they’re compacted. When this time interval is met, the records are compacted but not deleted. Default is 14. A value of 0 means compaction does not occur. No maximum value is in effect.
Trigger Prefix	For the Trigger Based capture type, you can add a prefix to the names of the AFTER DELETE, AFTER INSERT, and AFTER UPDATE triggers that the CDC script generates for each source table to get before images and after images of the DML changes. Enter any prefix value up to 16 characters in length. An underscore (_) follows the prefix in the trigger name, for example, TX_ SAP_DEMO_TABLE_DBMI_USER_t_d. You can use the prefix to comply with your site's trigger naming conventions.
Cache Type	For the Log Based capture type, select Hana or Oracle as the cache type. The Secure Agent stores change data in the cache until the change records are ready to write to the target.
Cache Host	For the Log Based capture type, enter the host name of the machine that hosts the cache database.
Cache Port	For the Log Based capture type, enter the port number for the cache database server.
Cache User Name	For the Log Based capture type, enter the user name to use for connecting to the cache database.
Cache Password	For the Log Based capture type, enter the password to use for connecting to the cache database.
Cache Database/Service Name	For the Log Based capture type, enter either the HANA cache database name or the Oracle cache service name, depending on the cache type you selected.
Cache Additional Connection Properties	For the Log Based capture type, you can enter a list of optional cache connection properties. If you use a HANA cache, use the ampersand (&) separator. If you use an Oracle cache, use the semicolon (;) separator. Examples: HANA: latency=0&communicationtimeout=0 Oracle: EncryptionMethod=SSL;CryptoProtocolVersion=TLSv1.1
Cache Security Connection Properties	For the Log Based capture type, you can enter a list of optional security properties for the cache connection. If you use HANA cache, use the ampersand (&) separator. If you use Oracle cache, use the semicolon (;) separator. Examples: HANA: encrypt=true&validateCertificate=false Oracle: KeyStorePassword=xyz;TrustStorePassword=xy
Server Log Path	For the Log Based capture type, enter the log path for the SAP HANA database server.
Client Log Path	For the Log Based capture type, enter the mapping of the Secure Agent machine mount path to the source database log location.
Client Archive Log Path	For the Log Based capture type, enter the mapping of the Secure Agent machine mount path to the source database archive log location.