Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata

Overview

The procedure to upgrade Mission Control depends on your installation type. We strongly recommend reading through this page before proceeding with your upgrade. Detailed upgrade instructions are provided below for the following installation types:

  • Docker 
  • Standalone ZIP file 
  • CentOS
  • Ubuntu
  • Red Hat
  • Debian
Page Contents


Download

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. 

Docker Upgrade

To upgrade Mission Control that is run as a Docker installation, please refer to Running with Docker

Standalone Upgrade

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:

  1. First upgrade to version 1.6 as a Docker installation.
  2. Then upgrade the Docker installation to the latest version

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:

  1. Backing up files
  2. Installing the new version
  3. Replacing backed-up files
  4. Reconnecting to managed instances
Backing Up Files

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.

Installing the New Version

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 :

  1. $MC_HOME/data

  2. $MC_HOME/etc

  3. $MC_HOME/logs

Replacing Backed-up Files

Replace the files you backed up in the upgraded installation.

Reconnecting to Services

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. 

Uploading Extensions

Add Services to Sites

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.

Centos Upgrade

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:

Centos Upgrade
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

Ubuntu Upgrade

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:

Ubuntu Upgrade
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

RedHat Upgrade

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:

Redhat Upgrade
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

Debian Upgrade

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:

Debian Upgrade
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


Migrating Your Data

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


  • No labels