New Direct Access gateway version (1.7.1)

Direct Access gateway 1.7.1 introduces new capabilities and resolves several issues. To benefit from the enhancements and resolved issues, customers are encouraged to upgrade at the earliest opportunity. For upgrade instructions and a list of resolved issues, see Upgrading the Direct Access gateway installation

• REST Connector

  The new REST (via Direct Access gateway) connector provides secure access to private REST API endpoints via Direct Access gateway, allowing you to stream data directly into your Qlik Sense app.

  For more information, see REST data sources.

  The REST (via Direct Access gateway) connector will be rolled out to Qlik Cloud regions in four phases, with phase 4 scheduled to be completed by February 17th.

  • Phase 1: SE (Sweden), JP (Japan), and UK (United Kingdom)
  • Phase 2: DE (Germany), SG (Singapore), AP (Asia Pacific), and IN (India)

  • Phase 3: US (United States) and Qlik Cloud Government

  • Phase 4: EU (European Union)
    

• Overriding the default chunks cache directory

  For each reload operation, Direct Access gateway can cache data chunks in memory and offload them to disk (when the size allocated for caching is exceeded). You can override the default chunks cache directory (C:\ProgramData\Qlik\Gateway\tmp) directory if you do not have enough disk space on the system drive.

  For more information, see Overriding the default chunks cache directory.

• Overriding the default number of tables retrieved when working with the ODBC (via Direct Access gateway) Connector

  By default, 10,000 tables are retrieved for selection, which might not be enough when working with very large databases. This version introduce the ability to override the default by increasing the ODBC_TABLES_LIMIT_FOR_GENERICODBC property in the Direct Access gateway configuration.properties file.

  For more information, see Select and load data from an ODBC data source.

• Multiple catalog support with the Google BigQuery (via Direct Access gateway) Connector

  The Google BigQuery (via Direct Access gateway) Connector now supports accessing multiple catalogs (the equivalent of Google BigQuery projects) in a single connection.

  For more information, see Create a Google BigQuery Connection.

• Support for Unity Catalog with the Databricks (via Direct Access gateway) Connector

  The Databricks (via Direct Access gateway) Connector now supports accessing data in Unity Catalog on Databricks.

  For more information, see Create a Databricks connection.

• Mitigating data errors caused by the ODBC driver when using the ODBC (via Direct Access gateway) connector

  Sometimes, due to an issue with the vendor ODBC driver’s handling of source data types, either an error will occur during the reload or incorrect data will be loaded to Qlik Cloud. In such cases, you can override the Qlik Cloud data type or its specification (scale or precision, for example).

  For more information, see Overriding default the Qlik Cloud data type when working with the ODBC (via Direct Access gateway) connector.

• Relocation of connector start, exit, and restart events log events

  From Direct Access gateway 1.7.1, connector start, exit, and restart events will be written to the Direct Access gateway (DirectAccessAgent) log file. In previous versions, they were written to the Connector agent logs (connector-agent_logs_<date>) log file.