Licensing options for this format begin with FME Professional Edition.
The Denodo reader module provides FME with access to attribute data held in Denodo database tables. FME provides read access via Denodo's JDBC driver.
Denodo’s JDBC driver is not bundled with FME, but can be installed as part of Denodo Express. To install Denodo Express, please visit http://www.denodo.com/en/denodo-platform/denodo-express.
Denodo’s JDBC driver is located at
<Denodo folder location>/lib/vdp-jdbcdriver-core/denodo-vdp-jdbcdriver.jar
within the installed Denodo Express folder.
Please note that in order for Denodo’s JDBC driver to work correctly, the version of the driver must match the version of the Denodo server used.
Installing the JDBC Driver
To view instructions for installing the JDBC driver, please see Getting Started with JDBC.
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.
FME32_JVM_MIN_HEAP_SIZE: Same as FME_JVM_MIN_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MIN_HEAP_SIZE.
- FME_JVM_MAX_HEAP_SIZE: Maximum heap size for initializing the JVM.
FME32_JVM_MAX_HEAP_SIZE: Same as FME_JVM_MAX_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MAX_HEAP_SIZE.
These variables must be set for FME to honor them, and must be multiples of 1024K (for example, 4M and 64M, or 4096K and 32768K).
Note: To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.