Vexdata.io Documentation
  • Vexdata Overview
  • Installation
    • System Requirements
    • Windows Installation
    • Linux Installation
    • Cloud Installation
      • GCP
      • Azure
      • AWS Cloud Deployment Architecture Diagram
        • Pre-requisites
        • Manual Install on ec2
        • Cloud Formation Scripts (command line)
    • Admin Post Installation Setup
    • User Post Installation Setup
    • Server Improvement (Optional)
  • Getting Started
    • Roles and Permissions
    • Managing Groups and Projects
      • Folders
      • Projects
    • Settings
      • Slack Integration
      • Integrations
      • Rules
      • Properties
      • Integrations
      • Email Template
      • Report Template
      • Create Data Connections
        • Databases/Warehouses
        • Run On
  • Creating and Executing Test Cases
    • Test Case
      • Create Test Cases
        • Define Data Source and Target
          • Configure Table/s from Database
          • Input SQL Data
          • Input Files
            • Excel/CSV
            • XML
            • JSON
            • Parquet/AVRO
          • API Input
          • Table Filter
          • Advance - Input
        • Data Compare
          • ETL Testing/Cell By Cell Compare
            • Data Compare Mapping
            • Data Compare Options
          • Schema Compare
          • Counts Compare
        • Schema Monitoring
        • Data Quality
          • SQL Rules
          • Column Level Rules
          • Duplicates
      • Executing Test Cases
      • Defining Test Case Settings
    • Test Runs
    • Variables
    • Note
    • Label
  • Reports
    • User Reports
    • Admin Report or Manager Reports
  • Current Limitations
Powered by GitBook
On this page
  • Software Download and Installation
  • Set License Name and License Key (Optional -for paid subscription)
  • Set Server URL (Optional -If running jobs on Hadoop cluster/Kubernetes)
  • Starting the server
  • Update the software
  • HTTPS Setup
  • Create a .p12 (PKCS#12) File for HTTPS from a Key File
  • 1️⃣ Convert Your Key File to a .p12 Keystore
  1. Installation

Linux Installation

Software Download and Installation

The URL will be sent to you through email, along with your license key. After receiving it, use the wget command to retrieve the URL.

wget https://dataops-store.s3.amazonaws.com/dataops_server.zip

After retrieving the file, unzip it with the unzip command.

# unzip the folder
unzip dataops_server.zip
# change to the folder 
cd dataops_server

Set License Name and License Key (Optional -for paid subscription)

Edit the .env file and update the following three properties using the licensing information values provided to you by email after purchasing Vexdata. Be certain to update the default value of the LICENSE_NAME with the value shown in the email.

LICENSE_COMPANY_NAME=<Name>
LICENSE_NAME=<Name>
LICENSE_KEY=<key>

Setting License Key and Name are not required for Starter_Version

Set Server URL (Optional -If running jobs on Hadoop cluster/Kubernetes)

The default value for the server is http://dq-nginx. Set it to the server's URL if cluster (Hadoop, EMR, Databricks) is being used for jobs processing.

HOST_URL=< URL ex: dv.example.com or, if there is no URL, you can also set IP addrress>

If https keys are provided, set the HOST_URL to https://<server URL>

Starting the server

When running for the first time, get the latest software by running below command

 ./update_software.sh

Start the server either with the sudo command, or by logging in as a user with admin privileges.

 ./start_server.sh

Open an internet browser and go to your own host's URL : http://<HOST_URL>

If installing on the local machine, URL will be http://127.0.0.1

Note: Host is the server's URL or the IP address.

Do not use localhost in the URL.

Update the software

Follow the steps below to update the software with patches and upgrades.

  1. Update the Software Replace NEW_VERSION with the provided version (e.g., 7_35), and run the following command:

    ./update_software.sh NEW_VERSION
  2. Start the Server

    ./start_server.sh

HTTPS Setup

Create a .p12 (PKCS#12) File for HTTPS from a Key File

To enable HTTPS, you need a .p12 (PKCS#12) keystore that contains your SSL certificate and private key.


1️⃣ Convert Your Key File to a .p12 Keystore

If you have a private key (.key) and a certificate (.crt or .pem), use openssl to create a .p12 file.

🔹 Convert .key + .crt to .p12

openssl pkcs12 -export -inkey your-key.key -in your-certificate.crt -out keystore.p12 -name myalias

Explanation:

• -export → Creates an exportable keystore.

• -inkey your-key.key → Specifies your private key.

• -in your-certificate.crt → Your SSL certificate.

• -out keystore.p12 → Output .p12 file.

• -name myalias → Alias name for the key entry.

🔹 You’ll be prompted to enter an export password.

🔹 Remember this password—you’ll use it in app.properties.

  1. Copy the keystore.p12 file created above to my_data/keys/

  2. Update the SSL_PATH and SSL_PWD in app.properties file with keystore path and the password created above.

PreviousWindows InstallationNextCloud Installation

Last updated 3 months ago

You will need to have https .

certificate and keys