Skip to main content Skip to complementary content

Setting advanced connection properties

In the Advanced tab, you can enable the creation of reference files and set post-processing actions. These options are described in detail below.

Post upload processing - Run command after upload

You can process the final target files using a custom command. The command will be run whenever a data file is created.

Information note

If the Generate a reference file option is selected, a row (specifying the file's location) will be added to the Reference File only after the command completes successfully.

  • Command name - The location of the command e.g. C:\utils\move.exe.

  • Working directory - The directory where you want the command to run.

  • Parameters - Specify any parameters that need to be passed to the command during runtime. You can use the following built-in parameters:

    ${FILENAME} - The full path to the CSV file containing the full load or CDC data.

    ${METADATA_FILENAME} - The full path to the DFM file containing the metadata.

    For information on creating metadata files, see Setting general connection properties.

     

    Information note
    • If the CSV/DFM file paths contain spaces, you must enclose these parameters with quotation marks (e.g "${FILENAME}").
    • The post-processing command must return a proper exit code. For information on the available exit code options, see Exit Codes for the Post-Processing Command.

Generate Reference Files - Select this option to generate a Reference File (on Replicate Server) containing the full path to the Apply Changes data files.

Information note

The reference file only points to the location of the Apply Changes files, and not the Full Load files.

Reference File(s) folder - The folder on the Replicate machine in which the Reference File will be created.

Example:  

c:\temp\

Proxy Server

The available settings differ according to the selected storage type (Azure Data Lake Storage (ADLS) Gen1 or Azure Data Lake Storage (ADLS) Gen2).

Settings when using Azure Data Lake Storage (ADLS) Gen1 storage

The following settings are available when using Azure Data Lake Storage (ADLS) Gen1 storage:

  • Use proxy server: Select this option to access Microsoft Azure ADLS via a proxy server.
  • Host name: The host name of the proxy server.
  • Port: The port via which to access the proxy server.
  • User name: The user name for accessing the proxy server.
  • Password: The password for accessing the proxy server.
  • Scheme: Select which protocol to use to access the server (HTTP or HTTPS).

    Information note

    The selected Scheme applies to the storage, but does not apply to the ODBC connection.

  • SSL CA Path - The location of the CA file on the Replicate Server machine when HTTPS is the selected Scheme.

Settings when using Azure Data Lake Storage (ADLS) Gen2 storage

The following settings are available when using Azure Data Lake Storage (ADLS) Gen2 storage:

Information note

Proxy authentication and the HTTPS scheme are not supported when using Azure Data Lake Storage (ADLS) Gen2 storage.

  • Connect via proxy server to:
    • Cloud storage: Select to connect to Azure Data Lake Storage (ADLS) Gen2 storage via a proxy server.
    • Azure Active Directory: Select to connect to Azure Active Directory via a proxy server.

      Information noteWhen Azure Active Directory is selected, the connection is established via https://login.microsoftonline.com/.
  • Host name: The host name of the proxy server.
  • Port: The port via which to access the proxy server.

Exit Codes for the Post-Processing Command

The post-processing command must return a proper exit code. You can either use the standard exit code values described below or set a custom exit code value as described in Setting Post Command exit codes with an internal parameter below.

Standard Post Command exit codes

  • 0 - Success
  • 1 - Recoverable error. The task will recover from the point of failure according to the settings in the Environmental errors tab.
  • 2 - Table error. If a table error occurs, Replicate will handle the error according to the settings in the Table Errors tab.
  • 3 (or any other value e.g. -100) - Fatal error. The task will fail and not attempt recovery.

Setting Post Command Exit Codes with an Internal Parameter

You can use internal parameters to set exit codes with custom values. This is especially useful if your application already uses the standard exit code values.

See Standard Post Command exit codes above for a description of the exit codes.

  • successExitCode
  • recoverableErrorExitCode
  • tableErrorExitCode
  • fatalErrorExitCode

Internal Parameters

Internal parameters are parameters that are not exposed in the UI and should only be used if instructed by Qlik Support.

To add internal Qlik Replicate parameters:

  1. Click the Internal Parameters link.

    The Internal Parameters dialog box opens.

  2. In the edit box, type the name of the parameter you need to add and then click it.
  3. The parameter is added to the table below the search box with its default value.
  4. Change the default value as required.
  5. To reset the parameter value to its default, click the "Restore default value" icon at the end of the row.

More options

These options are not exposed in the UI as they are only relevant to specific versions or environments. Consequently, do not set these options unless explicitly instructed to do so by Qlik Support or product documentation.

To set an option, simply copy the option into the Add feature name field and click Add. Then set the value or enable the option according to the instructions you received.

Settings Summary

You can view a summary of your setting by clicking the View Setting Summary link. This is useful if you need to send a summary of your setting to Qlik Support.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!