Installing Mission Control

Java requirements

You must run Mission Control with JDK 8.

PHP requirements

Mission Control uses PHP to support its scripting functionality and requires PHP 5.6 on Debian and PHP 5.4 on Centos.

SELinux

Centos flavors may have issues starting MongoDB because of SELinux restrictions. Please refer to the  MongoDB documentation for instructions on configuring SELinux. 

Browsers

Mission Control has been tested with the latest versions (known at the time of release) of Google Chrome, Firefox and Safari.

Download

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

Installation

Docker Installation

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

apt-get install python-software-properties
add-apt-repository ppa:ondrej/php
apt-get update
apt-get install -y php5.6-fpm

JFrog Mission Control currently supports Red Hat 7.x.

Do not install Mission Control on a higher version of Red Hat as it has not been validated to work.

System library requirements

Mission control needs the following libraries to be present as run-time dependencies. Please ensure these are available before you begin installation.

• openssl 
• php-fpm
• net-tools

Installation Instructions

Once you have  downloaded Mission Control, installing it is very straightforward:

1. Extract the contents of the compressed file

   Installing Mission Control

   tar -xvf jfmc-redhat-<version>.tar.gz

2. Run the installer

   Installing Mission Control

   cd jfmc-redhat-<version>
   ./installJFMC-redhat.sh

   Using External Databases

   JFrog Mission Control uses several databases for different features of its operation. Until version 2.1, Mission Control installed an instance of all of these databases dedicated for its own use.

   From version 2.1, Mission Control gives you the option of using your own MongoDB, Postgres or Elasticsearch databases if you have these already installed and in use in your organization.

   When you run the installer, it will issue prompts asking if you want to install Mission Control using it's own internal databases, or if you prefer to use your own external databases.

   For details on how to respond to these prompts, please refer to Using External Databases.

3. A control file is created as part of the installation. Start Mission control using this file

   Starting Mission Control

   For v2.0.0 to v2.1.0,
   /opt/jfrog/jfmc/scripts/jfmc.sh start
   
   
   For v2.1.1,
   /opt/jfrog/mission-control/scripts/jfmc.sh start

Installation File Structure

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

Mission Control File structure

Home directory

The Mission Control home (/opt/jfrog/) directory will contain files necessary to start and stop all the micro-services associated with JFrog Mission Control

Microservices and Ports 

Docker Installation

Mission Control'sDocker installation only needs port 8080 to be exposed on the host to function.

If the port is occupied, Mission control will throw an error on start.

To change the port that the Docker installation uses, update the server.port property to another value (between 0 and 65535) in the $JFMC_HOME/jfmc/etc/mission-control.properties file.

Linux Installation

Mission Control runs a number of microservices with specific port allocations as described in the table below.

If a port is already in-use, the installer will display a warning, and in some cases, prompt for a different port.

Data

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

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.

For v2.0.0 to v2.1.0,
/opt/jfrog/jfmc/scripts/jfmc.sh status


For v2.1.1,
/opt/jfrog/mission-control/scripts/jfmc.sh status

Uninstalling

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. 

For v2.0.0 to v2.1.0,
/opt/jfrog/jfmc/scripts/jfmc.sh removeServices


For v2.1.1,
/opt/jfrog/mission-control/scripts/jfmc.sh removeServices

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 $MC_HOME/etc/mission-control.properties file as follows:
   
   

   1. Comment the line specifying 8080 as the server port (server.port=8080) and uncomment the line specifying 8443 as the server port. When done you should have:

      # server.port=8080 This line is commented
      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. Uncomment and set the keystore password property:

      server.ssl.key-store-password=<Keystore password>

   4. Uncomment and 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

Accessing Mission Control

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

http://SERVER_DOMAIN:<server port>

The default port used by Mission Control is 8080, so a default installation would be accessed at http://localhost:8080.