Need help with other JFrog products?
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
Run the installer
We strongly recommend invoking Mission Control scripts with the
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 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'sowninternal 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.
The log file for the installation will be in a file installJFMC-deb.<timestamp>.log.
A control file is created as part of the installation. Start Mission control using this file
ZIP File Installation
To install on Debian or Ubuntu 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:
|Service||Default Port||Environment Variable|
|ElasticSearch||9200||This port setting cannot be modified|
|Postgres||5432||This 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:
If the Mission Control services are running, stop them
$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
Start the Mission Control services