Skip to main content

Installing Qlik Enterprise Manager in a Windows cluster

This topic explains how to install Enterprise Manager in a Windows 2008 R2 cluster, a Windows 2012 R2 cluster, and a Windows 2016 cluster.

Installing Enterprise Manager in a Windows 2012 R2 cluster or in a Windows 2016 cluster

Note:

Unless specified otherwise, all commands should be run from the Enterprise Manager bin folder. The default location is:

C:\Program Files\Attunity\Enterprise Manager\bin

  1. Open Failover Cluster Manager and connect to a network that contains the cluster nodes and a clustered disk (for the Enterprise Manager "data" folder).
  2. Install Enterprise Manager on Node 1. This node should be the Cluster Disk owner. You can specify any Destination Location, but the "data" folder must be installed on a clustered disk (i.e. a disk that is accessible to the other cluster node).

    Note:

    The "data" folder contains a "java" subfolder. At various points in the cluster setup, you will need to specify the location of both the "data" folder and the "java" folder. It is therefore recommended to make a note of the "data" folder location.

  1. Set the Enterprise Manager Master User Key by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path masterukey set -p password

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

  1. Set the Java Master User Key by opening a command prompt and running the following command from the Java bin folder (<INSTALL_DIR>\Enterprise Manager\java\bin by default):

    atajs.bat -d java_data_folder_path masterukey set password

    where -d java_data_folder_path is the path to the shared Enterprise Manager data\java folder.

  2. On Node 1, open the Windows Services console and stop the Enterprise Manager service.
  3. Move the shared Cluster Disk to Node 2.

    Example image of the context menu opened by right clicking on a storage disk in the Cluster tree view, with Move Available Storage - Select Node... selected

  4. Install Enterprise Manager on Node 2. The Destination Location can be any local folder, but make sure to install the "data" folder on the same clustered disk specified in step 2 above.
  5. Make sure the Enterprise Manager service is stopped on Node 2.
  6. Set the Enterprise Manager Master User Key by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path masterukey set -p password

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

  1. Set the Java Master User Key by opening a command prompt and running the following command from the Java bin folder (<INSTALL_DIR>\Enterprise Manager\java\bin by default):

    atajs.bat -d java_data_folder_path masterukey set password

    where -d java_data_folder_path is the path to the shared Enterprise Manager data\java folder.

  1. Configure the Enterprise Manager cluster role as follows:
    1. Right click on Roles and select Configure Role.
    2. In the Select Role: Choose "Generic Service" and then click Next.

      High Availability Wizard dialog, Select Role step, with Generic Service selected in the role list

    3. In the Select Service screen, choose "Enterprise Manager". Click Next.
    4. In the Client Access Point screen, enter the Enterprise Manager host name without the domain information (e.g. mycompany and not mycompany.qa.int). Click Next.

    5. In the Select Storage, select the location on the clustered disk where the Enterprise Manager "data" folder was installed. Click Next.
    6. Continue clicking Next until the Finish button is displayed and then click Finish.
  2. Configure the host name by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path configuration set -a host_name

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

    Note:

    The host name must be specified as a FQDN (e.g. mycompany.qa.int and not mycompany)

  3. Enterprise Manager Cluster Role Dependencies: Verify that the Enterprise Manager cluster role has set dependency on the clustered disk and the Enterprise Manager service. You can view the dependencies in the role properties.

    Your Enterprise Manager cluster should now be ready for use.

Installing Enterprise Manager in a Windows 2008 R2 cluster

Note:

All commands should be run from the Enterprise Manager bin folder. The default location is:

C:\Program Files\Attunity\Enterprise Manager\bin

  1. Open Failover Cluster Manager and connect to a network that contains the cluster nodes and a clustered disk (for the Enterprise Manager "data" folder).
  2. Install Enterprise Manager on Node 1. This node should be the Cluster Disk owner. During the installation, you can specify any Destination Location, but the "data" folder must be installed on a clustered disk (i.e. a disk that is accessible to the other cluster node).

  1. Set the Enterprise Manager Master User Key by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path masterukey set -p password

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

  1. Set the Java Master User Key by opening a command prompt and running the following command from the Java bin folder (C:\Program Files\Attunity\Enterprise Manager\java\bin by default):

    atajs.bat -d java_data_folder_path masterukey set password

    where -d java_data_folder_path is the path to the shared Enterprise Manager data\java folder.

  1. On Node 1, open the Windows Services console and stop the Enterprise Manager service.
  2. Move the clustered disk to Node 2. This can either be performed using a command line in PowerShell or by adding a service to the cluster that allows both of the cluster nodes to communicate with the clustered disk.
  3. Install Enterprise Manager on Node 2. The Destination Location can be any local folder, but make sure to install the "data" folder on the same clustered disk specified in step 2 above.
  4. Make sure the Enterprise Manager service is stopped on Node 2.
  5. Set the Enterprise Manager Master User Key by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path masterukey set -p password

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

  1. Set the Java Master User Key by opening a command prompt and running the following command from the Java bin folder (C:\Program Files\Attunity\Enterprise Manager\java\bin by default):

    atajs.bat -d java_data_folder_path masterukey set password

    where -d java_data_folder_path is the path to the shared Enterprise Manager data\java folder.

  1. Configure the Enterprise Manager cluster service as follows:
    1. Right click on Services and applications and select Configure Service or Application.

      Example image of the context menu opened by right clicking on Services and applications in the Cluster tree view, with Configure Service or Application selected

    2. In the Select Service or Application screen, choose "Generic Service". Click Next.

    3. In the Select Service screen, choose "Enterprise Manager". Click Next.

    4. In the Client Access Point screen, enter the Enterprise Manager host name without the domain information (e.g. mycompany and not mycompany.qa.int). Click Next.

    5. In the Select Storage screen, select the location on the clustered disk where the Enterprise Manager "data" folder was installed.

    6. Continue clicking Next until the Finish button is displayed and then click Finish.
  2. Configure the host name by opening a command prompt and running the following command:

    aemctl.exe -d data_folder_path configuration set -a host_name

    where -d data_folder_path is the path to the shared Enterprise Manager data folder.

    Note:

    The host name must be specified as a FQDN (e.g. mycompany.qa.int and not mycompany)

  3. Enterprise Manager Cluster Service Dependencies: Verify that the Enterprise Manager cluster service has set dependency on the clustered disk and the Enterprise Manager service. You can view the dependencies in the service properties.

    Your Enterprise Manager cluster should now be ready for use.