Zoomdata Version

Managing Configurations in Zoomdata

The Zoomdata server leverages two configuration files to ensure successful deployment in your operating environment.

  • The zoomdata.properties file defines variables and parameters related to Zoomdata specifically.
  • The zoomdata.env file defines configurations and variables that help Zoomdata connect to and communicate with your network.

Both of these configuration files are the 'public-facing' documents where the Zoomdata administrator can make changes to the Zoomdata server. These files need to be created after the Zoomdata server has been installed.

With the release for version 2.6.2, the default server port configuration has changed. For new installations and upgrades, a single http port is configurable. By default, Zoomdata now uses http, rather than the previsously default value of https. You can configure the zoomdata.properties file to use self-signed certificates and https by configuring two variable in the properties for your Zoomdata environment. For information about these properties, see Zoomdata Configuration Files and their Properties.

To access these files on the Zoomdata Server and make edits, follow the step-by-step instructions provided below.

Accessing the Zoomdata.Properties or the ZOOMDATA.env File

Both the zoomdata.properties and zoomdata.env files are located in the /etc/zoomdata directory. Take the following steps to access either of these files:

  1. Log out of Zoomdata, if you are still in the program and close the browser.

  2. From your terminal, open a command line session.

  3. Via a command prompt, connect to your Zoomdata server.

  4. Stop the Zoomdata server service:

    sudo service zoomdata stop
  5. Use one of the following commands to access and open the configuration file:

    vi /etc/zoomdata/zoomdata.properties

    or

    vi /etc/zoomdata/zoomdata.env
    • If you are not logged in as a root user, then you will need to enter sudo vi /etc/zoomdata/zoomdata.properties or zoomdata.env to create this file.

    • If the configuration file does not exist, this command will create it.

  6. Add the new variable or property to the file on a new line or edit an existing variable or property, as needed.

  7. Save and exit the configuration file.

  8. Restart the Zoomdata Server:

    sudo service zoomdata start

Once the Zoomdata Server has successfully restarted, you can open a new browser window and log in. Check to determine whether your change(s) has taken effect.

Situations where the zoomdata.properties file needs to be created include:

  • Connecting Zoomdata to an existing MongoDB instance
  • Disabling SSL in Zoomdata
  • Setting up the screenshot feature (for RPM and Ubuntu )
  • Creating a symmetric key
  • Disabling the Real Time Sales Demo Source
  • Connecting Zoomdata to Spark on a Yarn server
  • Changes to Tomcat configurations (in other words, backend changes, where you cannot directly access the secured environment)

Situations where the zoomdata.env file needs to be created include:

  • Adding an SSL Certificate to the Zoomdata Server
  • Configuring Zoomdata Memory Settings

  • Configuring a Connection to a Standalone Spark Server

  • Connecting Impala to Secure CDH Cluster

  • Setting Up the Screenshot Feature (for RPM for CentOS)

  • Setting Up the Screenshot Feature (for Ubuntu)

Was this topic helpful?