Managing the Data Movement gateway server
This topic describes the various connectivity and management options that are available after you have installed Data Movement gateway.
Updating the Qlik Cloud tenant URL
You can change the Qlik Cloud tenant URL as needed.
To do this:
-
Run the following command to stop the Data Movement gateway service:
sudo systemctl stop repagent
-
Check that the service has stopped by running the following command:
sudo systemctl status repagent
The status should be as follows:
Active: inactive (dead) since <timestamp> ago
-
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
-
Run the following command to start the Data Movement gateway service:
sudo systemctl start repagent
-
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
Connecting to cloud data warehouses via a proxy server
You can configure the Data Movement gateway to connect to your cloud data warehouses via a proxy server. You can also disable proxy server connectivity should it no longer be required.
Enabling or editing proxy server connectivity
You can enable or edit proxy server connectivity as follows:
-
On the Data Movement gateway server, open a shell prompt and change the working directory to:
/opt/qlik/gateway/movement/bin
-
Run the following command to stop the Data Movement gateway service:
sudo systemctl stop repagent
-
Check that the service has stopped by running the following command:
sudo systemctl status repagent
The status should be as follows:
Active: inactive (dead) since <timestamp> ago
-
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@
-
Run the following command to start the Data Movement gateway service:
sudo systemctl start repagent
-
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:
-
On the Data Movement gateway server, open a shell prompt and change the working directory to:
/opt/qlik/gateway/movement/bin
-
Run the following command to stop the Data Movement gateway service:
sudo systemctl stop repagent
-
Check that the service has stopped by running the following command:
sudo systemctl status repagent
The status should be as follows:
Active: inactive (dead) since <timestamp> ago
-
Run the following command:
./agentctl qcs set_config --proxy_url ""
-
Run the following command to start the Data Movement gateway service:
sudo systemctl start repagent
-
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 Data Movement gateway settings (for example, Qlik Cloud tenant URL, proxy URL, and so on).
To do this:
-
Open a shell prompt and change the working directory to:
/opt/qlik/gateway/movement/bin
-
Run the following command:
./agentctl qcs show_config
Your current settings will be shown.
Example:
[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.
Data Movement gateway service commands
Before changing a setting on the Data Movement gateway server, you need to stop the Data Movement gateway service, and then start it once the setting has been changed.
Stopping the service
-
Run the following command to stop the Data Movement gateway service:
sudo systemctl stop repagent
-
Check that the service has stopped by running the following command:
sudo systemctl status repagent
The status should be as follows:
Active: inactive (dead) since <timestamp> ago
Starting the service
-
Run the following command:
sudo systemctl start repagent
-
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
-
Run the following command:
sudo systemctl restart repagent
-
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