Skip to main content

Step 1: Install Qlik Replicate in the cluster

To install Qlik Replicate in your cluster environment, perform steps 1-3 on each of the cluster nodes:

  1. Run the Qlik Replicate setup wizard on the first node that is part of your cluster (the active node). Install Qlik Replicate to a local folder. The default path is C:\Program Files\Attunity\Replicate.

    In the setup wizard, specify a shared storage location for the "data" folder; for example, F:\Replicate\data.

    For more information, see Setting up Qlik Replicate on Windows.

  2. Once setup has completed, open a command prompt as an administrator and change the working directory to the Replicate bin directory. The default path is C:\Program Files\Attunity\Replicate\bin.

    Then, run the following three commands, where Command 1 should only be run on the first cluster node.

    Warning note
    • The new_master_user_key must be identical on all participating cluster nodes.

      For more information on the role played by the master user key in Replicate, see Encrypting the user permissions file.

    • Setting the admin password using the setserverpassword command will invalidate the master key. Therefore, make sure to set the admin password before running the setmasterkey command.

    • The setmasterkey command overrides the mk.dat file, rendering all stored secrets invalid (as they were encrypted using the old key). Therefore, after changing the master key, you need to reenter the passwords in all of the relevant places. For more information, see Changing and protecting the master key.

      Additionally, because the Replicate server password is also stored in the mk.dat file, you need to reset it as described in Changing the server password

    repctl -d replicate_data_folder setmasterkey new_master_key master_key_scope=1

    Where:

    • replicate_data_folder is the shared storage location of the Replicate data folder defined earlier (for example, F:\Replicate\data). Paths with spaces must be enclosed with quotation marks.
    • new_master_key is the new master key
    repuictl -d replicate_data_folder masterukey set -p new_master_user_key

    Where:

    • replicate_data_folder is the shared storage location of the Replicate data folder defined earlier (for example, F:\Replicate\data). Paths with spaces must be enclosed with quotation marks.
    • new_master_user_key is the new master user key
    Information noteThis command is only required if you are using one of the following source endpoints: MongoDB, Salesforce, or Sap Extractor. Before running this command, make sure you have registered your license.

    Change your working directory to <REPLICATE_INSTALL>\endpoint_srv\bin and then run the following command to add the Endpoint Server data folder:

    rependctl -d replicate_endpoint_server_folder masterukey set new_master_key

    Where:

    replicate_endpoint_server_folder is the path to the endpoint_srv folder (as shown in the example below):

    Example:

    rependctl -d F:\Replicate\data\endpoint_srv masterukey set J8kaFbTUi22Mu5vSHdEBA5fHm36h8sqD
  3. Leave the command prompt open.

  4. Stop the Replicate services.
  5. Move your cluster to the next cluster node and install Qlik Replicate as described in Steps 1-2 above. Make sure you only run Command 2 and Command 3 (only required with certain endpoints - see note above) in Step 2.

  6. After Replicate is installed on all nodes, move all resources back to node 1, where the command prompt is still open. Then run the following command (from <REPLICATE_INSTALL>\bin) to set the Client Access Point name:

    repuictl -d replicate_data_folder configuration set --address client-access-point-name

    Where:

    • replicate_data_folder is the shared storage location of the Replicate data folder defined earlier (for example, F:\Replicate\data). Paths with spaces must be enclosed with quotation marks.
    • client-access-point-name is the Client Access Point name for the cluster.

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!