Table of Contents

Search

  1. Preface
  2. Connectors and connections
  3. Connection configuration
  4. Connection properties
  5. Swagger file generation for REST V2 connections

Connections

Connections

SAP HANA Database Ingestion connection properties

SAP HANA Database Ingestion connection properties

When you set up an SAP HANA connection, you must configure the connection properties.
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.
Type
The type of connection. Ensure that the type is
SAP HANA Database Ingestion
.
Runtime Environment
The name of the runtime environment where you want to run
database ingestion
tasks. You define runtime environments in
Administrator
.
User Name
The user name to use for connecting to the SAP HANA instance.
Password
The password to use 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
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.
Log Clear
Required for incremental loads. 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.
Trigger Prefix
Adds 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.
If you test the connection and the test fails, check that the SAP HANA JDBC driver file, ngdbc.jar, has been installed at
Secure Agent installation directory
>/ext/connectors/thirdparty/informatica.hanami
.

0 COMMENTS

We’d like to hear from you!