Installing Matillion ETL using the Universal Installer (RPM install)
    • Dark
      Light

    Installing Matillion ETL using the Universal Installer (RPM install)

    • Dark
      Light

    Article Summary

    Customers installing Matillion ETL via the Matillion Hub and the "bring your own license" (BYOL) method must download the correct configuration files for their environment, and then download and execute a single install script, as described below.

    Please note the following information:

    • To use this build process, all RPM build actions must be run as a root user on the virtual machine (VM) that the installation is being executed on.
    • The RPM installation method only applies to Matillion Hub customers and bring your own license (BYOL) customers. AWS customers who launch Matillion ETL via the original marketplace method can only install Matillion ETL on their golden AMI, via Private Image Build. Please submit a case at the Matillion Support Portal if you require further assistance with this.
    • New customers are advised to go through the Matillion Hub to select their preferred cloud provider and data warehouse to begin their Matillion ETL journey. For further information, read Matillion Hub - Instance Creation.
    • To update Matillion ETL to a specific version, refer to Updating - Specific Releases.

    Download the configuration files

    There are two configuration files needed for the installation of Matillion ETL:

    • installation.vars — is used to tell your environment how Matillion ETL will be installed.
    • Emerald.properties — is used to define the product you want to install. There are several versions of this file, one for each possible product variant. You will need to choose the file that matches your requirements.

    To download the installation.vars file, run the following command:

    curl https://bitbucket.org/matillion/matillion-etl-system-configuration/raw/stable/example-config/installation.vars > /tmp/installation.vars
    

    To download the correct Emerald.properties file:

    1. In a browser, go to https://bitbucket.org/matillion/matillion-etl-system-configuration/src/stable/example-config/. This will show you a list of Emerald.properties files.
    2. The filename suffix will identify which product variant the properties file is for. For example, Emerald.properties-AWS-SF-HUB is the properties file for Snowflake (SF) on AWS, for Hub licensing. Identify which file you need and copy or make a note of the filename for use in the following command.
    3. Download the correct Emerald.properties file into the /tmp directory using the following command:
    curl https://bitbucket.org/matillion/matillion-etl-system-configuration/raw/stable/example-config/[filename] > /tmp/Emerald.properties
    

    Where filename is the name you determined in step 2. For example, to install Matillion ETL for Snowflake on AWS using Hub licensing, the command is:

    curl https://bitbucket.org/matillion/matillion-etl-system-configuration/raw/stable/example-config/Emerald.properties-AWS-SF-HUB > /tmp/Emerald.properties
    

    Execute the install script

    1. Login with administrator privileges (root):
    sudo -i
    
    1. Run the following command to download the latest install script:
    curl https://bitbucket.org/matillion/matillion-etl-system-configuration/raw/stable/orchestrate-install.sh > /tmp/orchestrate-install.sh
    
    1. Change the script permissions as follows:
    chmod a+x /tmp/orchestrate-install.sh
    
    1. Run the script as follows:
    /bin/bash /tmp/orchestrate-install.sh /tmp/installation.vars
    
    1. After a successful install, restart your Matillion ETL instance by running the following command:
    reboot
    
    Note

    Send the universal installer output to a file on disk

    If you need support, capturing the output of the universal installer helps our support team to work with you to solve your support issue.

    These steps can also be found here.

    1. When executing the installer's orchestration shell script, orchestrate-install.sh, pipe the standard output of the script (and child Ansible playbook) to a file in the desired location. In the following example, the installer log file can be located at /var/log/metl-installer.log.
    /bin/bash /tmp/orchestrate-install.sh /tmp/installation.vars >/var/log/metl-installer.log
    
    1. If necessary, review the logs for signs of a critical failure and remediate as possible.
    2. If assistance is required, submit a support case at https://support.matillion.com and include the log file for review guidance as needed.