Mission Control Installation

📘

Subscription Information

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

JFrog Mission Control is a topology management microservice built into JFrog Artifactory (available from Artifactory 7.27+, supported exclusively as a microservice from 7.49+). It enables centralized management of multiple JFrog Platform Deployments (JPDs) and requires an Enterprise X or Enterprise+ license to activate. Mission Control is disabled by default.

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

Prerequisites

📘

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 a microservice starting from release 7.49. Contact JFrog to learn more about migrating 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:

   YAML

   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.

   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 on all nodes to enable Mission Control.

⚠️

Enable Mission Control in non-PostgreSQL Installation from Artifactory 7.84.10

If you run Artifactory with a non-PostgreSQL database and Mission Control was not enabled before upgrading to Artifactory 7.84.10, add shared.database.allowNonPostgresql: true to enable it after the upgrade.

Bootstrap Custom Configurations

Mission Control supports custom application configurations via a bootstrap directory. Any YAML file placed in this directory is ingested automatically on every Mission Control startup, letting you override default application settings without modifying core configuration files.

Bootstrap directory (all install types): /var/opt/jfrog/mc/bootstrap/mc/

To apply custom configurations:

1. Copy the existing application.yaml.template file in the bootstrap directory as application.yaml :

   Text

   /var/opt/jfrog/mc/bootstrap/mc/application.yaml

2. Uncomment lines matching properties you want to change, and update their values in application.yaml.

3. Restart Mission Control (or restart Artifactory if running Mission Control as a microservice).

The bootstrap file is re-read on every startup, so changes take effect after each restart.

Available configuration keys:

clients:
  # Time (seconds) to wait when resolving the server host.
  connectionTimeout: 5
  # Time (seconds) to wait for a server response before timing out.
  socketTimeout: 45
  accessJoin:
    maxRetry: 300

# Polling intervals for the Mission Control monitoring screen.
# Values use duration strings: seconds (s), minutes (m), hours (h).
monitoring:
  license:
    polling: 1m
  remoteTopology:
    polling: 30s
  localTopology:
    polling: 5s
  proxy:
    polling: 5m
  customJpdUrl:
    polling: 5m
  version:
    polling: 5m
  platformSecurity:
    polling: 5m
  pdnUsage:
    polling: 60m
  edgeStatus:
    polling: 1m
  storageinfo:
    polling: 5m
  lifecycleLink:
    polling: 5m
  entitlement:
    polling: 5m
  replication:
    polling: 5m
    pollingJobsSince: 1d
  projects:
    updateSchedule: fixedRate:60000/60000

📘

Override only what you need

You do not need to include every key in your bootstrap file. Mission Control merges your overrides with the defaults — only the keys you specify are changed.

Frequently Asked Questions

❓Is Mission Control included in all JFrog license tiers?

A: No. Mission Control requires an Enterprise X or Enterprise+ license on the Self-Hosted platform. It is not available on lower-tier licenses or on JFrog Cloud deployments.

❓Can Mission Control manage multiple JFrog Platform Deployments (JPDs)?

A: Yes. Mission Control is designed to provide topology management across multiple JPDs. Once enabled, the Topology tab appears in the JFrog Platform Administration module, allowing you to view and manage connected JPDs.

❓How do I verify that Mission Control is running after enabling it?

A: After restarting Artifactory, navigate to Administration > Topology in the JFrog Platform UI. If Mission Control is running, the Topology tab is visible. You can also check service statuses at Monitoring Service Statuses.