The Mission Control data folder (usually,
/var/opt/jfrog/mission-control) will contain files created and used by each of the micro-services.
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.
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:
After downloading and extracting the installer, the following file structure is created under the installation folder
|The installation script for specific Linux flavor (Debian/Centos)|
|A folder containing files necessary to configure 3rd party services like MongoDB etc.|
|A folder containing the actual packages to install (deb or rpm files)|
|A folder containing scripts necessary to seed users/data into 3rd party services|
|A folder containing scripts necessary to migrate from earlier versions of Mission control|
|A file containing the version of the JFMC|
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:
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.
To uninstall Mission Control, follow the steps below according to your installation type.
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.
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:
$MC_HOME/bin/jfmc.sh stop rm -fr $MC_HOME
JFrog Mission Control supports secure access with SSL. The following example shows how to enable access with SSL using a JKS keystore:
Modify your mission-control.properties file as follows:
Docker: $MC_HOME/jfmc/etc/mission-control.properties (default : $HOME/.jfrog/jfmc/jfmc/etc/mission-control.properties)
Set (or modify) the port property to :
Set the path to your keystore in the
server.ssl.key.store property. For example:
Set the keystore password property:
Set the keystore type property:
Save the changes to your
Start JFrog Mission Control
Once you have completed this configuration, you can access JFrog Mission Control through the server port specified in the
For example, using the above configuration, you could access Mission Control via SSL using the following URL:
Once installation is complete, Mission Control has a default user with admin privileges predefined in the system:
We strongly recommend changing the admin password when you run the Onboarding Wizard.
Mission Control can be accessed through your browser using the following URL: