Using Managed MongoDB

When using managed or external mongoDB deployed out of the EFCX solution, below given paramters are required to be updated before the EFCX deployment.

Important Note when using Managed MongoDB in HA using replicaSet:

For Connections env:

In case the managed mongoDB is running in replicaSet configuration, please enable the relevant parameters for the replicaSet. the above URI shoudl reflect the full list of all the replicaset members in mongodb://mongo-mongodb-0.mongo-mongodb-headless.ef-external.svc.cluster.local:27017,mongo-mongodb-1.mongo-mongodb-headless.ef-external.svc.cluster.local:27017,mongo-mongodb-2.mongo-mongodb-headless.ef-external.svc.cluster.local:27017/?replicaSet=expertflow&tls=false&ssl=false&retrywrites=true format.

For file-engine and conversation-controller:

this is required only to verify that mongoDB is available and properly booted up as precondition to run. This can be only primary node’s URI instead of the full replicaSet URI.

For Reporting-Connector

this is a bit different. When using single node MongoDB , please use the same value of the URL for all the variables. However, in case of replicaSet deployment model of MongoDB, place each replicaset member starting with the initial primary assigned to mongo_host1 and then remaining in sequencial order to other variables.

for example for above given replicaSet configuration, it will be

mongo_host1=mongodb-0.mongo-mongodb-headless.ef-external.svc.cluster.local
mongo_host2=mongodb-1.mongo-mongodb-headless.ef-external.svc.cluster.local
mongo_host3=mongodb-2.mongo-mongodb-headless.ef-external.svc.cluster.local
mongo_host4=mongodb-3.mongo-mongodb-headless.ef-external.svc.cluster.local
mongo_host5=mongodb-4.mongo-mongodb-headless.ef-external.svc.cluster.local
mongo_host6=<empty>