Installing Mission Control

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.

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:

• • RPM for CentOS or Red Hat  
  • DEB for Debian or Ubuntu
  • Standalone ZIP for Linux 

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

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:

• Docker installation
• ZIP installation
• RPM installation
• Debian installation   

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

/opt/jfrog/mission-control/scripts/jfmc.sh status

ZIP Installation

$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. 

/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:

$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

Accessing Mission Control

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

http://SERVER_DOMAIN:<server port>