Configuring MongoDB in Qlik Sense Enterprise for elastic deployments

Qlik Sense Enterprise for elastic deployments uses MongoDB as a database for persisting content for several services (excluding Qlik Sense app files).

By default, a pre-configured MongoDB Community Edition is added during the installation of Qlik Sense Enterprise for elastic deployments. This is only intended to be used for quick start, testing and evaluation purposes. If you use this version, your MongoDB data may be lost if the Kubernetes cluster is updated.

You can set up a production-ready MongoDB environment in the following ways:

  • Deploy a separate MongoDB server or cluster along-side Qlik Sense.
  • Use a MongoDB DBaaS provider (such as MongoDB Atlas or mlab)

Configuring the MongoDB connection

When installing Qlik Sense Enterprise for elastic deployments you can specify your MongoDB connection as follows:

  • A parameter in the helm install command.
  • Referencing the connecting settings in a values.yaml and using this in the helm install command.

Using CLI paramaters

You can extend the basic helm install command by setting the following properties:

  • Set the devMode.enabled value to false to disable development mode.
  • Set the mongodb.uri value with the connection string to MongoDB.

Example:  

helm upgrade \ --install qsefe qlik/qsefe \ --set mongodb.uri=<your-connection-string>,engine.acceptEULA="yes"

Referencing values.yaml

Create the values.yaml file and include the settings you want to reference in the helm install command.

  • Set the devMode.enabled value to false to disable development mode.
  • Set the mongodb.uri value with the connection string to MongoDB.

Example: values.yaml

engine: acceptEULA: "yes" devMode: enabled: false mongodb: uri: "<your-connection-string>" identity-providers: secrets: idpConfigs: - <your IdP configuration here>

The values.yaml file is then referenced in the helm install command:

helm upgrade \ --install qsefe qlik/qsefe \ -f values.yaml