Application deployment with Elastic Beanstalk - Data360_DQ+ - 12.2

Prerequisites:

• You have created the required infrastructure, and you have a copy of the dqplus.properties and pw.properties files that were created as part of this process (see Creating the infrastructure). Ensure that you have a copy of the latest versions of these files.
• Your Precisely representative must have provided you with a <build>-dist.zip file.
• If you are installing from a separate virtual machine, also known as a maintenance node, you need at least 32 GB of free disk space, to deploy Data360 DQ+ and to run server utilities later.

1. Unzip <build>-dist.zip and create the following folder:

   <build>/deployment/environments/<deployment_id>

2. Copy the dqplus.properties and pw.properties files to the folder that you created in step 1.
3. Rename the dqplus.properties file to <deployment_id>.properties
4. If it does not already exist, create a /etc/cafe folder on the machine from which you are deploying the application, and ensure that this folder is owned by the user who will be running the deployment scripts.

5. Ensure that the gradle.sh script is executable by running these commands from the deployment folder:

   chmod +x gradle.sh

   chmod +x gradle-dist/bin/gradle

6. Initialize the database by running the following command, replacing <deployment_ID> with the actual deployment ID:

   ./gradle.sh currentBuild to-<deployment_ID> initialize

7. Run the following command to deploy the application, replacing <deployment_ID> with the actual deployment ID:

   ./gradle.sh currentBuild to-<deployment_ID> deploy

Adding third-party or custom files after installation

To enable the functionality of some third-party products or to deploy custom node plugins, you may need to add third-party or custom JAR files to your installation. For example, Data360 DQ+ supports the ability to connect to an external database by deploying the database vendor's JDBC driver files.

1. Add the required JAR files to the following folders:
   • <OVERRIDES_FOLDER>/spark/jars
   • <OVERRIDES_FOLDER>/lib
2. Run the following command to deploy the application, replacing <deployment_ID> with the actual deployment ID:

   ./gradle.sh currentBuild to-<deployment_ID> deploy

   This will push the files to the Application Server Docker containers.

Changing the location of the overrides folder

You can change the location of the <OVERRIDES_FOLDER> folder by editing the OVERRIDES_FOLDER property in the target environment properties file.

1. Open the target environment properties file. For example, for the example_dev environment, the properties file is located at environments\example_dev\example_dev.properties
2. Set the OVERRIDES_FOLDER property to point to the path where you want to store the overrides folder.
   Note: It is recommended that you save the <OVERRIDES_FOLDER> folder in a separate location to the build folder so that it is not deleted when an older build is removed.

   On Windows, the path must be specified with double slashes, for example:

   OVERRIDES_FOLDER=C:\\example_dev\\b52\\cafe_5.2\\overrides

   On Linux, the path must be specified with single forward slashes, for example:

   OVERRIDES_FOLDER=/home/overrides