Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content

Step 3: Define the dependencies for each service

You should define dependencies for the Qlik Replicate services. This allows the Storage and the Network names to start before the Qlik Replicate services. If these resources do not start up before the services, Qlik Replicate will not start because it will continue to search for the data location.

To define the dependencies:

  1. In the left pane of the Failover Cluster Manager console, select Roles. The available roles will be listed in the right pane of the console. Select the role you are working with and then, in the bottom right pane, select the Resource tab. From the list of the available roles, select Qlik Replicate UI Server.

  2. Right-click the Qlik Replicate UI Server role and select Properties.

    The Qlik Replicate UI Server Properties dialog box opens.

  3. In the Qlik Replicate UI Server Properties dialog box, select the Dependencies tab.
  4. Click Insert. A new line is added to the Resource list.
  5. In the Resource column, click the arrow and select the Replicate Data storage resource from the list.
  6. Click Insert and add the Network Name resource (its name should be the same as the cluster name).
  7. Repeat the steps for the Qlik Replicate Server service.
  8. Start the Services using the Failover Cluster Manager and access the console using the Network name.
  9. Register the license. The license should contain all host names of the cluster.

    Information note

    To open Qlik Replicate Console, it is recommended to use an address that includes the name or IP address of the cluster machine (as opposed to the specific node name).

    Example:

    https://cluster_name_ip/attunityreplicate/

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!