SAP HANA and Cloud Platform HANA Service Non-Spatial Reader/Writer

The SAP HANA and Cloud Platform HANA Service Non-Spatial reader and writer modules provide FME with access to attribute data held in SAP HANA database tables.

FME provides read and write access via SAP's JDBC driver, which must be installed separately.

Downloading the JDBC Driver

Note  For best results, use the JDBC driver that matches the version of the software being communicated with.The JDBC driver is available in the SAP HANA Client Libraries package, and is usually named ngdbc.jar.

This driver is downloadable from https://support.sap.com/swdc as part of the SAP HANA Client package. It is also bundled with most SAP HANA distributions.

Installing the JDBC Driver

To view instructions for installing the JDBC driver, please see Getting Started with JDBC.

Usage Notes

The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variables allow you to specify memory available to Java Plugins:

FME_JVM_MIN_HEAP_SIZE

Initial heap size for initializing the JVM. If unset, the default value is 1024K.

This variable must be set in multiples of 1024 and greater than 1 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

6291456

6144k

6m

FME_JVM_MAX_HEAP_SIZE

Maximum heap size for initializing the JVM. If unset, the default value is 16384K.

This variable must be set in multiples of 1024 and greater than 2 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

83886080

81920k

80m

Tip  To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.
Memory Usage (applicable to writers only): Changing the value in the writer parameter Features Per Transaction can control the number of features that FME places in each transaction before a transaction is committed to the database.