DB - MongoDB

1 min

review the docid\ p148zbzlcmhqj1qizhm43 overview mongodb integration enables an edge system to connect with a mongodb database supported versions mongodb 2 x mongodb 3 2 supported communication outbound (edge to database) yes inbound (database to edge) no configurations variable detail required name enter a name for the connector yes hostname ip address or hostname of mongodb server (must be reachable from the edge system) yes port mongodb server port yes username user name no password user password no auth database authentication database name no auth mechanism authentication mechanism (can be one of "scram sha 1", "mongodb cr", "mongo cr", "plain", "mongodb x509") no database database name if database does not exist it is created yes collection collection name if collection does not exist it is created yes show mapping data from a predefined table could be mapped into a custom one example {"from" "to"} where "from" is a column from predefined table, and "to" is a column from destination table see docid\ fi9mbiprrrixufdihwql9 to learn more commit timeout transaction commit timeout (ms) no max transaction size maximum number of messages before a transaction is committed regardless of timeout no throttling limit set a limit on the number of outbound messages per second if sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost no queue mode select the sequence of data transfer fifo or lifo selecting fifo (first in first out) will send the earliest message first selecting lifo (last in first out) will send the latest message first no persistent storage if enabled, messages in the outbound queue are stored on disk if there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored no