Installing OpsCenter with a tarball on any Linux distribution

Install DataStax OpsCenter on any Linux Distribution or Mac OS X using the OpsCenter binary tarball.

Install DataStax OpsCenter on any Linux Distribution or Mac OS X using the OpsCenter binary tarball.
Note: Mac OS X is supported for development and testing purposes only.

For a complete list of supported platforms, see OpsCenter Supported Platforms.


Minimum hardware requirements for the machine on which OpsCenter runs:
  • 2 CPU cores
  • 2 GB of RAM available to OpsCenter

Permission and software requirements:

  • Oracle Java SE Runtime Environment 8 (JRE or JDK) or OpenJDK 8. Earlier or later versions are not supported. See installing the Oracle JDK or OpenJDK.
    Tip: Use OpsCenter Lifecycle Manager to automatically manage Java and JCE installs for DSE clusters.
  • DataStax recommends using a recent version of one of the major web browsers. OpsCenter does not support Internet Explorer or Microsoft Edge.


  1. Download the tarball distribution of OpsCenter.

    To install the latest version:

    curl --user dsa_email_address:password -L \ | tar xz
    where dsa_email_address and password are your DataStax Academy account credentials.
    Attention: Depending on your environment, you might need to replace @ in your email address with %40 and escape any character in your password that is used in your operating system's command line. Examples: \! and \|.
    To install earlier versions, add the version number in the above command. For example:
    curl --user -L \ | tar xz

    To view the available versions, see the OpsCenter Release Notes.

    Files for OpsCenter and a single DataStax agent are now in place.

  2. Change to the opscenter-version_number directory.
    cd opscenter-version_number
  3. Start OpsCenter from the install location:
    Note: Use bin/opscenter -f to start OpsCenter in the foreground.
  4. Connect to OpsCenter in a web browser using the following URL:

What's next

Add an existing cluster or provision a new cluster in Lifecycle Manager.