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

Skip to end of metadata
Go to start of metadata

Overview

This page helps you get started using Mission Control. Assuming you comply with the System Requirements specified below, after going through this page, you should have your instance of Mission Control configured with at least one Artifactory service.

From version 3.1, the Mission Control installation file is available for download as an archive in three flavors: standalone ZIP file for Linux, RPM and Debian.

License

Mission Control itself is provided for free and has no license requirements. However, while you may view any Artifactory service from Mission Control, you may only configure and see relationships between services that are activated with Artifactory Enterprise, Enterprise+, and Artifactory Edge licenses.

Viewing Artifactory OSS, Artifactory Pro and Artifactory SaaS

You may add services of Artifactory OSS, Artifactory Pro to Mission Control, but for these instances, you can only view basic information. You cannot perform any actions on these services through Mission Control.

As a shared managed service, Artifactory SaaS is maintained for you by JFrog and can not be managed by Mission Control.

However, if you are running a Artifactory SaaS as a dedicated server, this can be fully managed by Mission Control

Download

The latest version of Mission Control is available for download from the Mission Control Download Page.

Installation

No spaces

Mission Control offers a variety of options for installation on different platforms.

In all cases, make sure that the full path to the installation folder does not contain any space characters.

Using non-interactive automated scripts to install Mission Control

To install/upgrade Mission Control using automation, pass the following option (according to your installation type) when running the installation/upgrade:

Docker: ./mission-control --use-defaults install

RPM: ./installJFMC-rpm.sh --use-defaults

DEB: ./installJFMC-deb.sh --use-defaults

Existing parameters will be used in the automation process.


Data Folder

The Mission Control data folder (usually, /var/opt/jfrog/mission-control) will contain files created and used by each of the micro-services.

 

Log Location

Logs are written into data folder (usually at /var/opt/jfrog/mission-control/logs) and log rotation is not enabled. It is recommended to turn on log rotation.


Supported Installers

Mission Control is available for download as a Docker image to be run as a container. For full details, please refer to Installing with Docker

Mission Control is also available for installation on Kubernetes. For full details, please refer to Installing on Kubernetes.

Mission Control can also be installed on the following Linux flavors:

 

Installation File Structure

After downloading and extracting the installer, the following file structure is created under the installation folder

install-rpm.sh or
install-deb.sh
The installation script for specific Linux flavor (Debian/Centos)
config
A folder containing files necessary to configure 3rd party services like MongoDB etc.
packages
A folder containing the actual packages to install (deb or rpm files)
seed_data
A folder containing scripts necessary to seed users/data into 3rd party services
migration
A folder containing scripts necessary to migrate from earlier versions of Mission control
version.sh
A file containing the version of the JFMC

Changing Port Settings

If the various services installed with Mission Control create an port conflicts, you can change the corresponding port settings. For details please refer to Changing Port Settings for a:


Status of Installation

Use the following command to check the installation status. Once installation is complete, the same command will provide the status of the services as well.

RPM or Debian Installation
Mission Control services status
/opt/jfrog/mission-control/scripts/jfmc.sh status
ZIP Installation
Mission Control services status
$MC_HOME/bin/jfmc.sh status

Uninstalling

To uninstall Mission Control, follow the steps below according to your installation type.

RPM or Debian Installation

Use the control file to initiate uninstalling JFrog Mission Control as follows:

Please note that this will not uninstall third-party components installed as part of installation. They will have to be uninstalled manually. 

Removing the Mission Control services
/opt/jfrog/mission-control/scripts/jfmc.sh removeServices
ZIP Installation

JFrog Mission Control service related data, logs and configuration will be in the $MC_HOME folder. To uninstall a ZIP installation of Mission Control, use the following commands:

Removing the Mission Control services
$MC_HOME/bin/jfmc.sh stop
rm -fr $MC_HOME

Secure Access With SSL

JFrog Mission Control supports secure access with SSL. The following example shows how to enable access with SSL using a JKS keystore:

  1. Stop JFrog Mission Control
  2. Consult your Certificate Authority and generate a certificate for your instance of Mission Control
  3. Modify your mission-control.properties file as follows:
          

    mission-control.properties location

    Docker: $MC_HOME/jfmc/etc/mission-control.properties (default : $HOME/.jfrog/jfmc/jfmc/etc/mission-control.properties)
    RPM/Debian: $MC_DATA/etc/mission-control.properties (default : /var/opt/jfrog/mission-control/etc/mission-control.properties)
    ZIP: $MC_HOME/etc/mission-control.properties

    1. Set (or modify) the port property to :

      server.port=8443
    2. Set the path to your keystore in the server.ssl.key.store property. For example:

      server.ssl.key-store=path/to/keystore.jks
    3. Set the keystore password property:

      server.ssl.key-store-password=<Keystore password>
    4. Set the keystore type property:

      server.ssl.key-store-type=JKS
    5. Save the changes to your mission-control.properties file.

  4. Start JFrog Mission Control

Once you have completed this configuration, you can access JFrog Mission Control through the server port specified in the mission-control.properties file. 

For example, using the above configuration, you could access Mission Control via SSL using the following URL:

https://<mission-control-server-ip>:8443

Default Admin User

Once installation is complete, Mission Control has a default user with admin privileges predefined in the system:

User: admin

Password: password

Change the admin password

We strongly recommend changing the admin password when you run the Onboarding Wizard.


Accessing Mission Control

Mission Control can be accessed through your browser using the following URL:

http://SERVER_DOMAIN:<server port>