On this Page
This account is used by the Snaps in the SAP HANA Snap Pack.
You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for SAP HANA:
Avoid changing account credentials while pipelines using them are in progress. This may lead to unexpected results, including locking the account. |
If the Snap fails to connect to the database, it will retry three more times. |
Label | Required. User provided label for the account instance. | |
---|---|---|
Account Properties | Required. | |
Hostname | Required. Database server host name Example: localhost Default value: [None] | |
Port Number | Required. Database server port number Example: 30015 Default value: 30015 | |
Database name | Required. Specify the database name to connect. Example: sample Default value: [None]
| |
JDBC Driver | Select the JDBC driver to use. The default driver is included in the Snap. If the user wants to override it then upload the jar here. Default value: [None] | |
JDBC Driver Class | The JDBC Driver class name to use. Example: com.sap.db.jdbc.Driver Default value: [None] | |
Username | Specify the database username to use in the following format: Example: Snapuser Default value: [None] | |
Password | Database password to use. Example: Snapuser Default value: [None] | |
Advanced Properties Required. | ||
Min pool size | Required. Minimum connection pooling size to use. Example: 1 Default value: 1 | |
Max pool size | Required. Maximum connection pooling size to use. Example: 10 Default value: 10 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Url Properties | Properties to use in JDBC url. Example: maxAllowedPacket | 1000 Default value: [None] | |
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Fetch size | Required. Number of records to retrieve from the DB at a time. Example: 100 Default value: 100 | |
Batch size | Required. Number of statements to execute at a time. Example: 1000 Default value: 1000 |
For a DB Execute Snap, assume that a stream of documents enters the input view of the Snap and the SQL statement property has JSON paths in the WHERE clause. If the number of documents are large, the Snap executes in more than one batches rather than executing one per each document. Each batch would contain a certain number of WHERE clause values. If Auto commit is turned on, a failure would only roll back the records in the current batch. If Auto commit is turned off, the entire operation would be rolled back. For a single execute statement (with no input view), the setting has no practical effect.
Example
To enable SSL you must ensure that:
To enable SSL, configure the following URL properties:
There are also other applicable URL properties aside from those above. See Client-Side TLS/SSL Configuration Properties (JDBC) for details on all URL properties.
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account. Account:
|