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
Externalizing ElasticSearch
To externalize the ElasticSearch database, respond to the prompts as described below:
Prompt | Response |
---|---|
Install Elasticsearch? [Y/n]:n | "n" |
Please enter the Elasticsearch URL [http://docker.for.mac.localhost:9200]: | Provide the URL to your ElasticSearch database or accept the default if that is correct. Please ensure you provide http or https protocol in the url. |
After the installation completes, update the following properties in the file: mission-control.properties with appropriate values
- elastic.username
- elastic.password
Externalizing MongoDB (from 2.x to 3.3.x only)
To externalize the MongoDB database, respond to the prompts as described below:
Prompt | Response |
---|---|
Install MongoDB? [Y/n]:n | "n" |
Please enter the MongoDB Host [docker.for.mac.localhost]: | Enter the host that MongoDB is available on. (Usually, `localhost`). NOTE: Do NOT include a protocol. |
Please enter the MongoDB Port [27017]: | Enter the port that Mission Control can use to access MongoDB. (Usually, 27017) |
Docker installation does not try to automatically seed the database In a Docker installation, the installer does not attempt to seed the external MongoDB database. Instead, it copies the files needed for manual seeding as described in Manually Seeding MongoDB below and the automatic installation process ends here. Attempt to seed MongoDB? [y/N]: | To have the installer seed your MongoDB automatically, respond with "y" MongoDB must be on the same machine for automatic seeding The installer can only seed a MongoDB database automatically if it is on the same machine as the installer. If your MongoDB is installed on another machine, respond with "N". If you respond with "N", the installer copies the files you will need to manually seed the database and ends the installation process. If you respond with "y" the installer continue and prompt you with the following questions. |
Is this a fresh installation with no users? (If you choose 'y', the installer will create an admin user): |
|
| Provide an admin user ID and password The installer will attempt to perform the following actions to seed the MongoDB automatically:
|
Manually Seeding MongoDB (from 2.x to 3.3.x only)
Seed the database before starting JFrog Mission Control
MongoDB is used to store metadata about Mission Control's microservices, so the script attempts to create the necessary databases and users. If you are familiar with MongoDB or do not have access to the Mongo instance, you can review the createMongoUsers.js
file and create these yourself using the appropriate database client. If not and if you have access to the instance where MongoDB is installed, follow the instructions below:
- Copy the files
createMongoUsers.sh
andcreateMongoUsers.js
to the system where MongoDB is running. - Make the shell file executable (
chmod +x createMongoUsers.sh
) - Execute the file
./createMongoUsers.sh
and follow the prompts on screen.
Externalizing PostgreSQL
To externalize the PostgreSQL database, respond to the prompts as described below:
Prompt | Response |
---|---|
Install Postgres? [Y/n]:n | "n" |
Please enter the Postgres Host [docker.for.mac.localhost]: | Enter the host that Postgres is available on. NOTE: Do NOT include a protocol. |
Please enter the Postgres Port [5432]: | Enter the port that Mission Control can use to access Postgres. (Usually, 5432) |
Manually Seeding PostgreSQL
Seed the database before starting JFrog Mission Control
If you choose to seed your database manually, make sure you do so BEFORE starting up JFrog Mission Control.
Running the seeding steps manually
PostgreSQL is used to store metadata about Mission Control's microservices, so the script attempts to create the necessary database, users and schema. If you are familiar with PostgreSQL or do not have access to the postgres instance, you can review the createPostgresUsers.sh file and create these yourself using the appropriate database client. If not and if you have access to the instance where PostgreSQL is installed, follow the instructions below:
- Copy createPostgresUsers.sh to the system where PostgreSQL is running.
- Make the shell file executable (
chmod +x createPostgresUsers.sh
) - Review the default values used. If you change any values, make sure to change the corresponding environment variables in the installer.
- Execute the file
./createPostgresUsers.sh
.
Externalizing Databases on an Existing Installation
You can externalize the databases Mission Control uses on an existing installation at any time by simply running the installer again.
When prompted with Perform a standard upgrade? [Y/n]
,
select
"N".
Now just continue with the process in the same way you would during a new installation
Changing Externalized Databases
Mission Control offers you the flexibility to decide when to externalize its databases, and even to switch externalized databases in case you have more than one instance of any particular database installed in your system.