New Direct Access gateway version (1.7.6)

Direct Access gateway 1.7.6 introduces both new and enhanced features, and resolves several issues. For upgrade instructions and a list of resolved issues, see Upgrading the Direct Access gateway installation

File (via Direct Access gateway) connector: Restricting file system access to specific spaces

When using the File (via Direct Access gateway) connector, you can now restrict file system or network drive access to specific spaces. Pairing each path with spaces within your Qlik Cloud tenant means that only space members with the Can consume data role or higher will be able to access the specified path. When no space is configured, the specified paths will be accessible to all spaces.

The new configuration can be made via the public API, or directly in the configuration file on the gateway server.

Public API

File (via Direct Access gateway) connector

Support for applying changes without requiring a gateway restart

From this version, when updating the allowed paths/URLs for the File (via Direct Access gateway) and REST (via Direct Access gateway) connectors, you no longer need to restart the Direct Access gateway service to apply the changes. This is also true when making changes to the following ODBC (via Direct Access gateway) properties:

• Allowed drivers

• Allowed DSNs

• Custom type mappings

Oracle (via Direct Access gateway) connector: Support for the Oracle TNS Names connection method

This version adds support for accessing Oracle using TNS Names.

Create an Oracle connection

File (via Direct Access gateway) connector: Process isolation enabled by default

When performing a clean install of Direct Access gateway, process isolation will now be enabled by default with the Number of concurrent reload processes set to 10.

Process isolation

Allowing connections to localhost using the REST (via Direct Access gateway) connector

You can now allow the REST (via Direct Access gateway) connector to connect to localhost. This facilitates the use of local (to the gateway server) REST endpoints such as using the connector-agent/ status endpoint to determine the active number of loads on an agent.

This is also configurable using the public API, when adding local URLs (http://localhost:5050/status for example) to the restconnector_allowed_urls.txt file.

Allowing connections to localhost using the REST (via Direct Access gateway) connector

Public API

Support for using the public API to perform “load data” requests asynchronously

Performing Load Data request asynchronously on the agent significantly shortens the time the cloud service needs to wait for responses from the agent.

This feature, which was introduced in Direct Access gateway 1.7.5, is now available via the public API using the OPTIONAL_CAPABILITIES parameter.

Public API

Process isolation enhancements in heavy load scenarios

When a gateway is under heavy load with limited resources, enhancements were made to prevent the following issues:

• Connector port conflicts when process isolation is enabled

• Over-frequent attempts to start the connector process