SAP HANA and Cloud Platform HANA Service Non-Spatial: Add Database Connection

To define a new connection from the Connection parameter in a SAP HANA format:

Select Add Database Connection. See database-specific parameters below, as well as the section Adding a Database Connection in a Workspace in Using Database Connections The new connection can be made visible only to the current user, or can be shared among multiple users.

Note To select an existing, previously defined connection, see the section Reusing a Database Connection in Using Database Connections

Database Connection

SAP HANA or SAP Cloud Platform HANA Service

Name

Enter a name for the new connection.

Connection Parameters

Server

The host name of the SAP HANA database.

Port

The port of the SAP HANA database. Typically, this is 3<instance id>15. For example, instance ID 00 would have a port of 30015 and instance ID 90 would have a port of 39015.

Database

In a multiple-database environment, the name of the database to connect to.

Username and Password

Enter the username and password to access the service.

Encrypt Connection

Note This parameter is not present in the Cloud Platform HANA Service Reader and Writer. The Cloud Platform HANA Service Reader and Writer will always request Secure Sockets Layer (SSL) encrypted connections.

When enabled, this parameter requests encryption for the connection. If the server does not have a certificate trusted by the client machine, the connection will fail. Otherwise, data will be encrypted before traveling over the network.

If this parameter is not enabled, data will not be encrypted over the network and the host certificate will not be validated.

Advanced – Specify JDBC Connection

When enabled, this parameter will allow JDBC connection string and properties to be specified directly. The specified connection string and properties will be used to connect to the database.

Option	Description
Connection String	The connection string for the database to which you are connecting, in the format: jdbc:sap://<server>:<port>
Mask Connection Details	When this option is checked (set to Yes), connection strings and properties for database connections are masked in translation and error logs. Connection details may contain sensitive information, such as passwords. A masked connection string appears as: jdbc:<subprotocol>:********** While masked connection properties appear as: {<property_name1>=********, <property_name2>=********, ...} Warning** Connection strings for connections whose parameters are embedded in the workspace are not masked, regardless of this setting. When this option is unchecked (set to No), connection strings are logged in plain text.
Connection Property and Value	JDBC connections can be configured with driver-specific arbitrary name/value pairs. The name/value pairs can often be specified in either the Connection String or a Properties object (sometimes only in one way or the other). Name/value pairs entered here will be set in the order specified, then passed on in a Properties object. They do not require manual encoding of characters that are not safe in Connection Strings.

Option

Description

Connection String

The connection string for the database to which you are connecting, in the format:

jdbc:sap://<server>:<port>

Mask Connection Details

When this option is checked (set to Yes), connection strings and properties for database connections are masked in translation and error logs.

Connection details may contain sensitive information, such as passwords. A masked connection string appears as:

jdbc:<subprotocol>:************

While masked connection properties appear as:

{<property_name1>=************,
<property_name2>=************, ...}

Warning Connection strings for connections whose parameters are embedded in the workspace are not masked, regardless of this setting.

When this option is unchecked (set to No), connection strings are logged in plain text.

Connection Property and Value

JDBC connections can be configured with driver-specific arbitrary name/value pairs. The name/value pairs can often be specified in either the Connection String or a Properties object (sometimes only in one way or the other).

Name/value pairs entered here will be set in the order specified, then passed on in a Properties object. They do not require manual encoding of characters that are not safe in Connection Strings.