Installing Mission Control

JFrog Installation & Setup Documentation
Content Type
Installation & Setup

Subscription Information

This feature is supported on the Self-Hosted platform, with an Enterprise X or Enterprise+ license.

The Mission Control microservice can be enabled through native installations (such as Docker, Docker Compose, Windows, RPM, Linux, and Debian) or via Helm installation for Kubernetes. By default, this service is disabled.

Note

Do not enable the Mission Control service on Artifactory Edge nodes.

Note

Mission Control is an Artifactory Service: Mission Control was integrated into JFrog Artifactory as a microservice starting from release 7.27, and is supported only as microservice starting from release 7.49. Contact JFrog to learn more about how to migrate to the Mission Control microservice.

To enable the Mission Control microservice:

  1. Go to the $JFROG_HOME/artifactory/var/etc directory.

  2. Edit the system.yaml file as follows:

    mc:
  enabled: true

    For Helm Installations

    Add the above section to the custom values.yaml file and run the Helm Upgrade command.

  3. Restart Artifactory.

  4. Verify that the Mission Control microservice is running. See Monitoring Service Statuses.View the Service Statuses

    In the JFrog Platform user interface, select the Administration module. If the Mission Control service was successfully enabled, a new tab named Topology appears in the Main Menu.

  5. For High Availability installations, repeat this procedure to enable Mission Control in all nodes.

Enable Mission Control in non-PostgreSQL Installation from Artifactory 7.84.10

If you run Artifactory with a non-PostgreSQL database, add shared.database.allowNonPostgresql: true, if the JFrog Platform did not have Mission Control microservice enabled before upgrading to Artifactory 7.84.10 and you wish to enable it after the upgrade.