MongoDB in the properties.json

MongoDB Properties

The MongoDB properties in the properties.json must be configured to connect to a single MongoDB server or a MongoDB replica set. Be sure to align your authentication and encryption settings with the configurations of the MongoDB you are connecting to.

Starting with the 2023.2 release, the ssl properties are deprecated and replaced with tls. See the Deprecation Notice here.

Minimal MongoDB Configuration

"mongoProps": {
  "db": "pronghorn",
  "url": "mongodb://localhost:27017"
}

Sample Production Configuration

"mongoProps": {
  "db": "pronghorn",
  "url": "mongodb://mongo01:27017,mongo02:27017,mongo03:27017?rs=rs1",
  "credentials": {
    "dbAuth": true,
    "user": "pronghorn",
    "passwd": "$ENC93f88824437dfe5784c7570f99d7251f878a2284aed6449259"
  },
  "tls": {
    "enabled": true,
    "tlsCAFile": "/etc/ssl/keys/mongo_ca_chain.cert",
    "tlsAllowInvalidCerts": false,
  }
}

Connection Pool Size in MongoDB

Connection pooling allows you to reuse connections rather than creating a new one every time IAP needs to establish a connection to the Mongo database. To configure the connection pool when connecting to MongoDB, use the maxPoolSize setting under mongoProps within the properties.json file.

This setting limits the ability of each application or adapter to add connections to the connection pool. In other words, it regulates (limits) the maximum number of pooled connections that can be opened for every application and adapter. When the maximum number of connections is reached, no additional connections can be created (opened) in the connection pool. Modification of maxPoolSize should be done with careful testing, as any changes to this value can impact IAP and workflow performance.

Sample Connection Pool Configuration

"mongoProps": {
  "db": "pronghorn",
  "url": "mongodb://localhost:27017",
  "maxPoolSize": 10
}

For more information on connection pooling, refer to:

• MongoDB Connection Pool
• Connection Pool Performance Tuning