Перейти к основному содержимому Перейти к дополнительному содержимому

Managing the Шлюз движения данных server

This topic describes the various connectivity and management options that are available after you have installed Шлюз движения данных.

Updating the Qlik Cloud tenant URL

You can change the Qlik Cloud tenant URL as needed.

To do this:

  1. Run the following command to stop the Шлюз движения данных service:

    sudo systemctl stop repagent

  2. Check that the service has stopped by running the following command:

    sudo systemctl status repagent

    Статус должен быть следующим:

    Active: inactive (dead) since <timestamp> ago

  3. Change the working directory to:

    /opt/qlik/gateway/movement/bin

    Then run the following command to set the Qlik Cloud tenant URL:

    Syntax:

    ./agentctl qcs set_config --tenant_url URL

    Example:

    ./agentctl qcs set_config --tenant_url mytenant.us.qlikcloud.com

  4. Run the following command to start the Шлюз движения данных service:

    sudo systemctl start repagent

  5. Check that the service has started by running the following command:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Примечание к информацииUpdating the Qlik Cloud tenant URL also requires you to generate a new registration key and register it in Администрирование > Data gateways. For details, see Stage two: Install and set up Шлюз данных — движение данных on a server behind the firewall protecting your data sources, and Stage three: Return to Администрирование and register Шлюз данных — движение данных).

Connecting to cloud data warehouses via a proxy server

You can configure the Шлюз движения данных to connect to your cloud data warehouses via a proxy server. You can also disable proxy server connectivity should it no longer be required.

Примечание к информацииThis proxy is only used for the connection between Шлюз движения данных server and your cloud data warehouses.

Enabling or editing proxy server connectivity

You can enable or edit proxy server connectivity as follows:

  1. On the Шлюз движения данных server, open a shell prompt and change the working directory to:

    /opt/qlik/gateway/movement/bin

  2. Run the following command to stop the Шлюз движения данных service:

    sudo systemctl stop repagent

  3. Check that the service has stopped by running the following command:

    sudo systemctl status repagent

    Статус должен быть следующим:

    Active: inactive (dead) since <timestamp> ago

  4. Run the following command to set the proxy:

    Syntax:

    ./agentctl qcs set_config --proxy_url https|http://host:port --proxy_username username --proxy_password password

    Example:

    ./agentctl qcs set_config --proxy_url https://myproxy:1212 --proxy_username admin --proxy_password f56weqs@

  5. Run the following command to start the Шлюз движения данных service:

    sudo systemctl start repagent

  6. Check that the service has started by running the following command:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Disabling proxy server connectivity

You can turn off proxy server connectivity as follows:

  1. On the Шлюз движения данных server, open a shell prompt and change the working directory to:

    /opt/qlik/gateway/movement/bin

  2. Run the following command to stop the Шлюз движения данных service:

    sudo systemctl stop repagent

  3. Check that the service has stopped by running the following command:

    sudo systemctl status repagent

    Статус должен быть следующим:

    Active: inactive (dead) since <timestamp> ago

  4. Run the following command:

    ./agentctl qcs set_config --proxy_url ""

  5. Run the following command to start the Шлюз движения данных service:

    sudo systemctl start repagent

  6. Check that the service has started by running the following command:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Viewing the current settings

You can view the current Шлюз движения данных settings (for example, Qlik Cloud tenant URL, proxy URL, and so on).

To do this:

  1. Open a shell prompt and change the working directory to:

    /opt/qlik/gateway/movement/bin

  2. Run the following command:

    ./agentctl qcs show_config

    Your current settings will be shown.

    Пример:  

    [qlik@gatewayhost bin]# ./agentctl qcs show_config
    --tenant_url “tenant.qlik.com”
    --proxy_url “”
    --proxy_username “”
    --connection_mode “DATA_GATEWAY”
    --listening_address “localhost”
    --listening_port “443"
    ReplicateAgent Control Program completed successfully.

Шлюз движения данных service commands

Before changing a setting on the Шлюз движения данных server, you need to stop the Шлюз движения данных service, and then start it once the setting has been changed.

Stopping the service

  1. Run the following command to stop the Шлюз движения данных service:

    sudo systemctl stop repagent

  2. Check that the service has stopped by running the following command:

    sudo systemctl status repagent

    Статус должен быть следующим:

    Active: inactive (dead) since <timestamp> ago

Starting the service

  1. Run the following command:

    sudo systemctl start repagent

  2. Check that the service has started by running the following command:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Restarting the service

  1. Run the following command:

    sudo systemctl restart repagent

  2. Check that the service has started by running the following command:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Примечание к предупреждениюAfter starting the gateway service, you must refresh your browser to see the updated data gateway status (Connected) in Администрирование > Data gateways.

Помогла ли вам эта страница?

Если вы обнаружили какую-либо проблему на этой странице или с ее содержанием — будь то опечатка, пропущенный шаг или техническая ошибка, сообщите нам об этом!