Using the latest JFrog products?
JFrog Platform User Guide
JFrog Mission Control 3.x Documentation
To get the latest version, go to the JFrog Unified Platform
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:
Extract the contents of the compressed file
Installing Mission Controltar -xvf jfmc-rpm-<version>.tar.gz
Run the installer
Installing Mission Controlcd jfmc-rpm-<version> ./installJFMC-rpm.sh
Bash recommended
When running scripts in Mission Control, we recommend using the
bash
interpreterUsing 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.
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. 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: 8089 8090 JFMC_INSIGHT_SERVER_PORT JFMC_INSIGHT_SERVER_SSL_PORT 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: If the Mission Control services are running, stop them Start the Mission Control servicesChanging Port Settings
Service Default Port Environment Variable Mission Control 8080 JFMC_PORT Insight server Insight scheduler 8085 JFMC_SCHEDULER_PORT Insight executor 8087 JFMC_EXECUTOR_PORT ElasticSearch 9200 This port setting cannot be modified Postgres 5432 This port setting cannot be modified /opt/jfrog/mission-control/scripts/jfmc.sh stop
$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/opt/jfrog/mission-control/scripts/jfmc.sh start