Skip to end of metadata
Go to start of metadata

Overview

Mission Control can be installed on a number of different Linux flavors. This page describes how to install Mission Control on CentOS or Red Hat.

Supported Versions

JFrog Mission Control currently supports CentOS 7.x and Red Hat 7.x.

Only install on supported versions

You should only install Mission Control on the supported versions of CentOS or Red Hat specified above as it has not been validated to work on higher versions.

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
  • net-tools
Page Contents

 

Installation Instructions

JFrog Mission Control can be installed using the Mission Control installer, or by extracting a ZIP file. The installer is completely self-contained and installs all the components that Mission Control needs while the ZIP file installation assumes that you have Elastic Search and MongoDB already installed and are managing those separately.

Installing with the Mission Control Installer

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-rpm-<version>.tar.gz
  2. Run the installer

    Installing Mission Control
    cd jfmc-rpm-<version>
    ./installJFMC-rpm.sh

    Bash recommended

    When running scripts in Mission Control, we recommend using the bash interpreter

    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 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 Mission Control to use 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
    /opt/jfrog/mission-control/scripts/jfmc.sh start

ZIP File Installation

To install on CentOS or Red Hat using the Mission Control standalone ZIP file installation, please refer to Linux ZIP File Installation

Changing Port Settings

The following table describes the different Mission Control services, the default port allocated to the service and the environment variable through which the port can be modified:

ServiceDefault PortEnvironment Variable
Mission Control8080JFMC_PORT
Insight server

8089

8090

JFMC_INSIGHT_SERVER_PORT

JFMC_INSIGHT_SERVER_SSL_PORT

Insight scheduler8085JFMC_SCHEDULER_PORT
Insight executor8087JFMC_EXECUTOR_PORT
ElasticSearch9200This port setting cannot be modified
Postgres5432This port setting cannot be modified

During the installation procedure, the installation script checks for port conflicts.

If port conflicts are detected, the installation script will prompt you to change the port allocated for the conflicting service and will update the corresponding environment variable specified in the table above.

If a conflict is detected after installation is complete, you can manually change a port allocation using the following procedure:

  1. If the Mission Control services are running, stop them

    /opt/jfrog/mission-control/scripts/jfmc.sh stop
  2. In $MC_DATA/setenv.sh (usually /var/opt/jfrog/mission-control/setenv.sh), modify the environment variable corresponding to the service with the port conflict as described in the table above
  3. Start the Mission Control services

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

  • No labels