--- title: "SAP HANA" slug: "sap-hana" status: "update" updated: 2026-05-21T19:01:06Z published: 2026-05-22T06:21:39Z canonical: "skthelp.syniti.com/sap-hana" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # SAP HANA ## Overview This page provides the required information for setting up replications using SAP HANA. Syniti Replicate supports use of SAP HANA as both [source](/v1/docs/sap-hana-as-source) and [target](/v1/docs/sap-hana-as-target) for: - [Refresh](/v1/docs/setting-up-a-replication) replications - [Mirroring](/v1/docs/setting-up-a-replication) replications. For source connections, Syniti Replicate offers [Triggers](/v1/docs/postgresql-as-source#enable-a-triggersbased-replication-from-postgresql) for SAP HANA. ## Prerequisites - Install SAP HANA Client 2.22 or later on the Syniti Replicate Server. - Select one of the following: - SAP HANA .NET Data Provider version 4.5 (Recommended). Search for “Software Downloads on the [SAP Development Tools](https://tools.hana.ondemand.com/#hanatools) page. **Assembly:** Usually located in C:\Program_Files\sap\hdbclient\ado.net\v4.5\Sap.Data.Hana.v4.5.dll ### Connection Properties | Property | Description | | --- | --- | | Server | Identifies the host name and the port of the SAP HANA database server. Server= | | User ID | Database user ID. | | Password | User Password. | | Database | Identifies the SAP HANA database instance. | | Pooling | Enables or disables connection pooling. | | Max Pool Size | The maximum number of connections allowed in the pool. | | Min Pool Size | The minimum number of connections allowed in the pool. | | Connection Lifetime | Specifies the maximum lifetime for a connection that is to be pooled. If a connection has been open for longer than the maximum lifetime, then the connection is not pooled when it is closed. The default value is 0, which means no maximum. | | Connection Timeout | Specifies the length of time (in seconds) to wait for a connection to the SAP HANA database server before terminating the attempt and generating an error. The default is 15. | | Current Schema | Specifies the default schema when connected to the SAP HANA database. | | Persist Security Info | Indicates whether the Password (PWD) connection parameter must be retained in the connection string property of the connection object. The default is false. | | Isolation Level | Specifies the default isolation level for the connection. | | Extended Properties | Additional properties not listed in the grid. Enter the properties as a list of “property = value” strings separated by “,”. | ### Creating a SSL Connection in SAP HANA for Syniti Knowledge Platform Enabling Secure Sockets Layer (SSL) on SAP HANA ensures secure communication between the Syniti Knowledge Platform (SKP) and the SAP HANA database server. Complete the following steps to create a SSL connection: 1. Obtain SSL certificates. You can use: - A self-signed certificate for internal use (not recommended for production). - A certificate issued by a trusted Certificate Authority (CA) for production. 2. Import SSL certificates into the Keystore. - SAP HANA uses the **SAP Cryptographic Library (CommonCryptoLib)** to manage SSL certificates. - Import the CA-signed certificate and the CA certificate chain into the Personal Security Environment (PSE) of HANA. 3. Update the HANA Configuration Files using the following steps: 1. Log in to the HANA server as **admin** user. 2. Navigate to the HANA instance profile directory: usr/sap//HDB/sec 3. Add the following parameters to the global.ini file: ```plaintext [communication] ssl = on ssl_keyfile = /path/to/ssl/key.pem ssl_certfile = /path/to/ssl/cert.pem ssl_trustfile = /path/to/ssl/trust.pem ``` 4. Replace `/path/to/ssl/...` with the actual file paths for your SSL key, certificate, and trust files. 4. Set Up the Trust Store. 1. The trust file should include the trusted CA certificates (root and intermediate). You can create a trust.pem file by concatenating these certificates: ```plaintext cat root-ca.pem intermediate-ca.pem > trust.pem ``` 5. Restart the SAP HANA database. For more information, refer to the official SAP documentation on [SSL for ODBC](https://help.sap.com/docs/PRODUCT_ID/0eec0d68141541d1b07893a39944924e/66a4169b84b2466892e1af9781049836.html?locale=en-US&state=PRODUCTION) and [SSL for .NET Driver](https://help.sap.com/docs/PRODUCT_ID/0eec0d68141541d1b07893a39944924e/469e137b6d611014ac27bffe40be2f18.html?locale=en-US&state=PRODUCTION). Once you complete the configuration in your database, you have to create the connection in the Catalog module of the SKP, and ensure that you select the **Enable TLS/SSL encryption for connection to SAP HANA** check box. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(664).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A45%3A27Z&se=2026-11-17T20%3A45%3A27Z&sr=b&sp=r&sig=2lxphBxiB849IcZ43%2FvqJzwk0BMY3X6H647lBfT7hwU%3D) ## Limitations If the .NET provider is used to establish the SAP HANA connection, the SAP HANA .NET client may fail to establish connections when SAP HANA sends a password expiration warning (`password_expire_warning_time` ), which occurs 7 days before the actual expiration date. This behavior effectively blocks connections for 7 days before the actual password expiration date, even though the SAP HANA system itself is not restricting access. We suggest increasing the password expiration duration (`maximum_password_lifetime` ) beyond the default of 182 days; however, as the expiration date approaches, connections to the SAP HANA system may start to fail. Refer to the [Password Policy Configuration Options](https://help.sap.com/docs/SAP_HANA_PLATFORM/b3ee5778bc2e4a089d3299b82ec762a7/61662e3032ad4f8dbdb5063a21a7d706.html?locale=en-US) external link for configuring password policy in the SAP HANA system.