Add a SAP HANA Source Datastore
A source datastore is a storage location Qualytics connects to so it can profile, scan, and monitor data. Adding SAP HANA as a source lets Qualytics query your HANA tables and views through the SAP HANA JDBC driver and run quality operations on the schemas it discovers.
Before you start, review the SAP HANA Permissions and the Authentication pages.
Tip
SAP HANA can also hold an enrichment datastore, where Qualytics writes anomalies and metadata. Link one during creation via Link Enrichment on Datastore Creation, or afterwards via Link Enrichment Datastore.
Field reference
The Add Datastore page shows the sections below when SAP HANA is selected. When reusing an existing connection, the Connection Properties and Secrets Management sections come already filled in and read-only: Qualytics has already validated those credentials, so you fill in only the Datastores Extraction and the Datastore Properties. To change a saved connection's credentials, edit the connection through the Manage Connections page; edits there apply to every datastore that reuses the connection.
Connection Properties
These fields define the SAP HANA endpoint Qualytics connects to and the account it connects with. They belong to the connection: when reusing an existing connection, they come already filled in and read-only.
| FIELD | REQUIRED | TYPE | DESCRIPTION |
|---|---|---|---|
| Connection Name | Text | A label for the saved connection (e.g., acme_hana_prod), so other datastores can reuse it later. |
|
| Host | Text | The HANA endpoint. On HANA Cloud, the URL SAP provides (e.g., xxxxxxxx.hna1.prod-us10.hanacloud.ondemand.com). On on-premises HANA, the hostname or address of the system. |
|
| Port | Number | The HANA SQL port. Defaults to 443, which is what HANA Cloud uses. On-premises systems usually listen on 3<instance>15, commonly 39015. |
|
| User | Text | The HANA database user Qualytics connects as. | |
| Password | Text | The password for that user. | |
| Encryption | Option | How the connection is secured. Encrypt and verify certificate is the default and is required by HANA Cloud. Encrypt, skip certificate verification suits an on-premises server presenting a self-signed or private-CA certificate your deployment does not trust. No encryption is only for a server not configured for TLS. |
Tip
For the exact HANA privileges the user needs, see SAP HANA Permissions.
Secrets Management
This group is optional: use it only if you want Qualytics to pull credentials from a secrets manager instead of typing them into the form. Turn on HashiCorp Vault to show the fields below. Despite the label, any secrets manager that exposes a compatible REST API works, not only HashiCorp Vault; see Secrets Management. It also belongs to the connection: read-only when reusing an existing connection.
| FIELD | REQUIRED | TYPE | DESCRIPTION |
|---|---|---|---|
| Login URL | Text | The Vault endpoint Qualytics uses to authenticate (e.g., https://vault.example.com/v1/auth/approle/login). |
|
| Credentials Payload | Text | A JSON body containing the credentials Vault expects (e.g., {"role_id":"...","secret_id":"..."}). |
|
| Token JSONPath | Text | The JSONPath that extracts the client token from Vault's response. Defaults to $.auth.client_token. |
|
| Secret URL | Text | The Vault path where the secret is stored (e.g., https://vault.example.com/v1/secret/data/sap-hana). |
|
| Token Header Name | Text | The HTTP header name used to send the token. Defaults to X-Vault-Token. |
|
| Data JSONPath | Text | The JSONPath that extracts the secret payload from Vault's response. Defaults to $.data. |
Note
Once the secrets manager is configured, reference any secret from a Connection Properties field with ${key}, for example ${password}. Qualytics resolves it each time the connection is opened, so a changed value takes effect on the next connection.
Datastores Extraction
Pick the tenant database, where applicable, and the schema or schemas Qualytics should read from. You fill these in on both flows.
| FIELD | REQUIRED | TYPE | DESCRIPTION |
|---|---|---|---|
| Database | Option | The HANA tenant database. Leave it empty on HANA Cloud, where the tenant is part of the hostname. On an on-premises multi-tenant system, pick the tenant. | |
| Schema | Option | One or more HANA schemas inside the tenant. Each schema you pick becomes its own Qualytics datastore. Click the refresh icon to load the ones visible to the user. |
One datastore per schema
HANA has no catalog above the schema, so the schema is the unit of discovery. Selecting more than one creates one source datastore per schema, named from the Name Template. See Multi-Schema Source Datastore Creation for details.
Datastore Properties
Common fields for every source datastore, shown below the Datastores Extraction section. You fill these in on both flows.
| FIELD | REQUIRED | TYPE | DESCRIPTION |
|---|---|---|---|
| Name Template | Text | Defines the naming pattern for each source datastore being created. Use {{schema}} as a placeholder that gets replaced with the actual schema name (e.g., hana_{{schema}} becomes hana_sales). Left empty, the datastore is named from the connection name and the schema. |
|
| Group | Option | Organizes your datastores under a shared group in the navigation tree. Select an existing group or create a new one with the Add New Group toggle. | |
| Teams | Option | Select one or more teams to associate with this source datastore. | |
| Initiate Sync | Checkbox | Automatically sync the datastore to detect containers and fields after creation. |
Allowlisting
A banner at the bottom of the form shows the IP address the connection is established from. Allowlist it on your HANA endpoint so the connection can be opened.
Steps
There are two ways to set up the connection: reuse a connection you already saved (Existing Connection) or create a new one from scratch (New Connection). The tabs below walk through each option; pick the one you want to follow. Each field is described in the Field reference above.
Step 1: Navigate to the Source Datastores page.
Step 2: Click the Add Source Datastore button at the top-right corner.
Step 3: The Add Datastore page opens.
Step 4: Select New Connection next to the Search field.
Step 5: Select SAP HANA from the connector grid. Use the search field to filter connectors by name.
Step 6: Fill in the Connection Properties: the Connection Name, Host, Port, User, and Password, and set Encryption to match how your HANA endpoint is secured.
Step 7: Optionally, expand Secrets Management to retrieve credentials from a secrets manager.
Step 8: Fill in the Datastores Extraction fields (Database and Schema) and the Datastore Properties.
Step 9: Click Test connection. A success message confirms that the connection has been verified.
Info
The Finish and Next buttons stay disabled until the connection test passes on the current values. If the test fails, see Troubleshooting.
Step 10: Click Finish to create the datastore.
Tip
To link an enrichment datastore so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.
Step 11: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.
Step 1: Navigate to the Source Datastores page.
Step 2: Click the Add Source Datastore button at the top-right corner.
Step 3: The Add Datastore page opens.
Step 4: Select Existing Connection next to the Search field.
Step 5: Select the saved SAP HANA connection from the grid. Use the search field to filter connections by name. The Connection Properties and Secrets Management sections come already filled in and read-only.
Start a new connection from this one
To use the selected connection as a starting point for a brand-new connection instead, click the Duplicate as a new connection button on the selected connection. The form switches to New Connection mode with the connection's settings already filled in for you to adjust.
Step 6: Fill in the Datastores Extraction fields (Database and Schema) and the Datastore Properties. These are the only fields left to fill in.
Step 7: Click Test connection. A success message confirms that the connection has been verified.
Info
The Finish and Next buttons stay disabled until the connection test passes on the current values. If the test fails, see Troubleshooting.
Step 8: Click Finish to create the datastore.
Tip
To link an enrichment datastore so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.
Step 9: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.