Creating the infrastructure - Data360_DQ+ - 11.X

Data360 DQ+ Azure Installation

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
11.X
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Azure Installation
Copyright
2024
First publish date
2016
ft:lastEdition
2024-06-06
ft:lastPublication
2024-06-06T12:37:34.761477

Prerequisite: You have a Linux machine with the necessary Setup requirements that you can use to deploy the infrastructure and install the application.

  1. Unzip the installation zip file and navigate to the infra/azure/config directory.
  2. Run the following command:

    python3 setup.py

    Follow the instructions provided by the script. You will need to provide the following information:

    • The tenant ID that you obtained from the App registrations section of your Azure account. See step 1 in the Azure requirements section.
    • The subscription ID that you obtained from the App registrations section of your Azure account. See step 1 in the Azure requirements section.
    • The client ID that you obtained from the App registrations section of your Azure account. See step 1 in the Azure requirements section.
    • The client secret that you obtained from the App registrations section of your Azure account. See step 1 in the Azure requirements section.
    • The application ID that you obtained from the Enterprise applications section of your Azure account. See Step 2 in the Azure requirements section.
    • The object ID that you obtained from the Enterprise applications section of your Azure account. See Step 2 in the Azure requirements section.
    • The location where you want to store the infrastructure.
    • If using an existing virtual network, you need to know its details. See Step 4 in the Azure requirements section.
    • A unique value that can be used to identify your company, which must be between three and twelve characters in length.
    • A deployment ID for the Data360 DQ+ installation, for example dev or prod.
    • The password to use for the Postgres database.
    • The external IP address of the host. You can use websites such as www.whatismyipaddress.com to find out what your IP is.
    • The location where you want to store a backup. This location should be the paired location of your primary region. For more information, see the Azure documentation, for example: https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions
    • The password to use for the SQL Server database.
    • The name of the email server, for example smtp.office365.com
    • The port of the email server, for example 587.
    • The email address from which you want to send application emails.
    • The tenant name to use for your company's installation of Data360 DQ+, for example infogix.com
    • The name of your company, for example Infogix, Inc
    • The email address of the system administrator.
    • The first and last names of the system administrator.
    • The password to authenticate against the specified email server.
    • You need to have a keypair that will be used for controlling access to the VM used for the JGroups Gossip Router service. You need to have the Public and Private key local on the deployment machine, and provide the full path to these files.
    Tip: If the deployment fails on the first attempt, please re-run python3 setup.py to attempt a second build which will continue from where the first run stopped. In some cases, transient network problems, or problems with individual components in Azure, can cause a failure when creating, editing or deleting components. If the deployment fails for a second time, please confirm that there are no Azure issues by checking the relevant Azure Service Status pages for your region/subscription.
  3. Run the following SQL statement for the init.sql file:

    sqlcmd -U mssqladmin -P DBPASSWORD -S DBSERVERNAME -d DATABASENAME -i PATHTOINITSQL -I

  4. Make a copy of the following files from the infra folder, and save them in a different location as a backup:
    • terraform.tfstate - This is a JSON file that is created dynamically by Terraform, containing the metadata of the resources that are created by Terraform. This file is created the first time that you run Terraform in your environment. This file is critical because it is used by Terraform to determine the changes that should be made to the infrastructure. If you are installing a new patch, Terraform will use this file to determine what changes need to be made for the new release.
    • dqplus.tfvars - This file contains a list of variables that are consumed by Terraform as part of the build and is populated based on your responses to the install questions.
    • dqplus.properties - This is a dynamically generated file and is created when the properties.py Python script is run during setup. It takes outputs from Terraform and constructs a file containing the properties that are needed to install the application.
    • pw.properties - This is a dynamically generated file and is created when the password.py Python script is run during setup. It contains password information for the created infrastructure which is then used by the application.