New Direct Access gateway version (1.7.11)

Direct Access gateway 1.7.11 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

ODBC (via Direct Access gateway) connector enhancements

Newly exposed configuration settings

The following settings, which previously could only be figured by manually editing a configuration file have now been exposed in the Gateway settings for <gateway-name> dialog:

• Allowing only specific DSNs

• Allowing only specific drivers

• Custom data type mapping

Support for delimiting table names

Some data sources require table names with upper case letters or special characters to be delimited in the load script. Otherwise, an error will occur. The new Delimit table names option eliminates the need to manually add delimiters to the load script when loading or previewing data.

For details, see Create an ODBC (via Direct Access gateway) connection.

Exposing the parameter for getting detailed error messages when using ODBC sources

Due to security concerns, the default error message returned by the ODBC driver contains minimal information. However, in certain scenarios, you might need more information to troubleshoot a specific issue. Previously this required adding the ShowErrorDetailMessage property to the Advanced section in the connector dialog and setting it to True. Now, you can select the Show detailed error message check box in the Gateway settings dialog.

For details, see Show detailed error message.

Support for changing the process isolation settings without restarting the gateway service

In previous versions, any changes to process isolation settings such as increasing the number of processes during a reload required the gateway service to be restarted. Now, changes to these settings will be applied without needing to restart the gateway service.

Logging improvements

• Reduced excessive logging when AGENT_LOG_LEVEL=DEBUG and AGENT_LOG_OPTIONS are not set.

• The connector-agent logs for file connector reloads now show the actual AppId instead of AppId=dummyDocId.

Enhanced async command support

Async command support increases efficiency by enabling Direct Access gateway to handle multiple commands (requests) simultaneously, as opposed to one at a time. In the past, when the destination command pod on Qlik Cloud was not available to handle a request, Direct Access gateway would continue sending the request to the same pod instead of failing. This would cause the command to fail after 10 attempts, with a generic error instead of pointing to the actual cause of the failure.

Qlik telemetry

A UserAgent header has been added to all connector-agent command responses (via HTTP POST). This will improve tagging of Direct access gateway usage in Qlik telemetry.

Header format:

qlik-direct-access-gateway/version

Example:

qlik-direct-access-gateway/1.7.10