Deploying MongoDB Ops Manager with the web console

Before you deploy the MongoDB database service, you need to deploy the MongoDB Ops Manager administration tool to manage and monitor your databases.

About this task

One Ops Manager instance can be used for multiple MongoDB databases.

Procedure

From the Cloud Pak for Data services catalog, click MongoDB Ops Manager.
From the MongoDB Ops Manager page, click New Instance.
On the New Instance page, enter a name for the Ops Manager instance, select the namespace where you want to deploy the instance, and click Next.
On the Ops Manager configuration page, specify the following options for Ops Manager on the OpenShift® cluster:
- Number of replicas: Replica is the same as pod. Typically you would want at least two replicas so that if Ops Manager goes down the interface is still available on the other replica.
- Cores per replica
- Memory (GiB) per replica
- Whether to Deploy on dedicated nodes. For more information, see Setting up dedicated nodes for your MongoDB deployment.
- Whether to Remove pvcs and secrets upon deletion. If this is enabled, the pvcs and secrets will automatically be removed when you delete an instance. Deletion is permanent.
Select from the storage classes that are available on the cluster, and then specify the size and unit for the storage class. Click Next.
On the Metadata configuration page, specify Number of replicas, Cores per node, and Memory (Gib) per node.

This page configures the back end database that Ops Manager uses to store metadata. The amounts that you specify on this page should match the number of databases that you intend to deploy.
Select from the storage classes that are available on the cluster, specify the size, and then click Next.
On the credential page, specify a user name and password for accessing Ops Manager.

Note:
Passwords must be at least 8 characters long and contain at least one letter, one digit, and one special character.
Check over the review page and then click Create.
It might take up to five minutes for the instance to be ready. You can run the following command to get the status:
```
oc describe cpdmongodbopsmanager opsManagerInstanceName -n ${PROJECT_CPD_INSTANCE}
```
Where namespace is the OpenShift project (namespace) where Cloud Pak for Data was installed.

The status results should look similar to the following example:
```
Status:
 Conditions:
   Last Transition Time:  2021-06-14T17:41:38Z
   Message:               Running reconciliation
   Reason:                Running
   Status:                True
   Type:                  Running
 Mongodb Status:          InProgress
```
When Mongodb Status: changes to Completed, you are ready to use the instance.
You can access Ops Manager by looking up the route with the following command:
```
oc get routes -n ${PROJECT_CPD_INSTANCE}
```
You should see a route that is based on the name of your Ops Manager instance. You could also again describe the instance as you did for the status and look for the opsmanagerURL key under Status that contains the URL for Ops Manager.