- This line was added.
- This line was removed.
- Formatting was changed.
With the release of Artifactory 7.27.3, Mission Control has become a microservice within Artifactory that provides the following features:
Manage Central License and Bucket License
Manage Platform Deployments (JPD)
- Access Federation UI
View JPD Health and Status Dashboard
You must migrate mission control data after you upgrade to Artifactory 7.27.3 or later to use Mission Control as a microservice.
From JFrog Artifactory version 7.27.3, Mission Control has been integrated directly into Artifactory as a microservice. You will no longer need to install Mission Control to use the features it provides, only to enable the microservice in Artifactory.
The metrics capabilities that were provided Mission Control will now be provided through JFrog Insight. To learn more about how to install Insight, see Installing Insight.
You must install JFrog Insights to use trends and charts after you migrate to Mission Control microservice. For more information, see Migrating from Mission Control to Insight.
Mission Control Deployment Options Matrix
While Mission Control will be in maintenance mode with minor fixes and security updates beyond version 4.7.x, you can still install it as an independent product and use it independently as in its previous versions. Since there are several ways in which you can use Mission Control within the JFrog Platform, the following table provides a matrix of the deployment options and their uses.
If you are using Projects and License Buckets, and are currently on Mission Control 4.6.x, verify that you upgrade to the latest version of Mission Control 4.7.15 and Artifactory 7.27.x or later, before you upgrade from standalone Mission Control to Insight. After the migrate, you will be using the Mission Control microservice in Artifactory.
Migrating the Mission Control Database to Artifactory
Perform the following steps if you want to use the Artifactory database for Mission Control:
Export the Mission Control database into a JSON file using the REST API.
Code Block language bash
curl -v -X PUT http://localhost:8082/mc/api/v1/system/backup/export -H "Authorization: Bearer $TOKEN"
After running the
curl, the files/key will be generated in the
/var/backup/mcfolder in Mission Control. The customer will need to create an mc folder in Artifactory under
/var/backup/and to then move the files.
- Rename the
import.json. Copy this file and the file
backup.keyto the Artifactory node inside the folder
- Stop the Mission Control service.
- Upgrade Artifactory to latest version. For more information, see Upgrading Artifactory.
Enable Mission Control in Artifactory by updating the Artifactory system.yaml file
mc*enabled=true(Mission Control is not enabled by default after installation).
Code Block language yml
## Mission control template mc: enabled: true
- Restart Artifactory to raise it with the newly-enabled microservice.
Import the JSON file into Artifactory with the import API that reads the JSON file:
Code Block language bash
curl -v -X PUT http://localhost:8082/mc/api/v1/system/backup/import -H "Authorization: Bearer $TOKEN"
If you use Mission Control in a high availability cluster, you need to run migration for only one node in the cluster since all nodes share the same database. But you must enable Mission Control microservice in all Artifactory nodes.
To learn more about generating the admin token, see Generating Admin Tokens.