Using Mission Control 3.x ?
JFrog Mission Control 3.x User Guide
Need help with other JFrog products ?
JFrog Enterprise+ User Guide
JFrog Artifactory User Guide
JFrog Xray User Guide
JFrog Distribution User Guide
JFrog Bintray User Guide
JFrog Access User Guide
JFrog CLI User Guide
Have a question? Want to report an issue? Contact JFrog support
You can download the latest version of Mission Control in all its formats from its download page on JFrog Bintray.
Removing InfluxDB
If you are upgrading from a previous version of Mission Control that used InfluxDB to store graph data, the upgrade script will suggest removing the InfluxDB installation.
To upgrade Mission Control that is run as a Docker installation, please refer to Running with Docker.
Upgrading from versions below 1.3 to versions 1.3 and above?
When upgrading from versions below 1.3 to version 1.3 and above, you first need to delete $MC_HOME/data/storage/instanceConfigDescriptors before you proceed with the upgrade.
Upgrading a standalone or ZIP installation from below version 1.6 to 2.x
From version 2.0, Mission Control does not support a standalone or ZIP installation. If you are running a standalone or ZIP installation of Mission Control that is below version 1.6, upgrading to version 2.x is a two step process:
For details, please refer to Upgrading Mission Control under Running with Docker.
Upgrading Mission Control is a simple process during which all of your instance data, repository data and configuration scripts remain intact.
Upgrading Mission Control involves the following basic steps:
If you have modified either of $MC_HOME/etc/mission-control.properties or $MC_HOME/etc/logback.xml, save a copy of these files in a temporary location.
To install the new version of Mission Control, unzip the distribution archive in a temporary location and replace the following files and folders with the corresponding ones from the newly unzipped archive.
under $MC_HOME :
$MC_HOME/data
$MC_HOME/etc
$MC_HOME/logs
Replace the files you backed up in the upgraded installation.
To reconnect to Artifactory following an upgrade, you need to upload the Mission Control extensions to Artifactory as follows:
When viewing the details of a service, from the Actions menu, click Upload Extensions.
Once you have reconnected to services, make sure to add them to sites in your system so they can be fully managed by Mission Control
Repeat this for all the Artifactory services being managed by Mission Control.
Upgrading from versions below 1.3 to versions 1.3 and above?
When upgrading from versions below 1.3 to version 1.3 and above, your first step should be to delete $MC_HOME/data/storage/instanceConfigDescriptors before you proceed with the upgrade.
To upgrade Mission Control that is run as an Centos, download the latest version and browse to its location on your file system.
Execute the following command:
sudo su service mission-control stop tar -xvf jfmc-centos-<version>.tar.gz cd jfmc-centos-<version> ./installJFMC-centos.sh
Externalizing a Database?
Mission Control gives you the option to externalize one or more of its databases during an upgrade.
To externalize a database, when prompted with Perform a standard Installation? [Y/n]: , respond with "n" and then follow the prompts as described in Using External Databases.
To upgrade Mission Control that is run as a Ubuntu installation, download the latest version and browse to its location on your file system.
Execute the following commands:
sudo su service mission-control stop tar -xvf jfmc-ubuntu-<version>.tar.gz cd jfmc-ubuntu-<version> ./installJFMC-ubuntu.sh
Externalizing a Database?
Mission Control gives you the option to externalize one or more of its databases during an upgrade.
To externalize a database, when prompted with Perform a standard Installation? [Y/n]: , respond with "n" and then follow the prompts as described in Using External Databases.
To upgrade Mission Control that is run as a RedHat installation, download the latest version and browse to its location on your file system.
Execute the following commands:
sudo su service mission-control stop tar -xvf jfmc-redhat-<version>.tar.gz cd jfmc-redhat-<version> ./installJFMC-redhat.sh
Externalizing a Database?
Mission Control gives you the option to externalize one or more of its databases during an upgrade.
To externalize a database, when prompted with Perform a standard Installation? [Y/n]: , respond with "n" and then follow the prompts as described in Using External Databases.
To upgrade Mission Control that is run as a Debian installation, download the latest version and browse to its location on your file system.
Execute the following commands:
sudo su service mission-control stop tar -xvf jfmc-debian-<version>.tar.gz cd jfmc-debian-<version> ./installJFMC-debian.sh
Externalizing a Database?
Mission Control gives you the option to externalize one or more of its databases during an upgrade.
To externalize a database, when prompted with Perform a standard Installation? [Y/n]: , respond with "n" and then follow the prompts as described in Using External Databases.
Following an upgrade from a version 1.x to 2.0 and above, if you want to Mission Control to continue providing historical data you collected with version 1.x, you need to migrate your data. For details, please refer to Migrating Data from InfluxDB to Elastic Search.