Integration component to interact with MongoDB databases. The component works with
the MongoDB versions 2.6
and above.
The technical notes page gives some technical details about MongoDB component like changelog.
The authenticate and connect with the MongoDB you must create credential with following entries:
mongodb://example.com:2017
or mongodb+srv://server.example.com:2017
.admin
, but your case can be different. Please check your records.URL
- URL used to connect with Mongo DB.
Example: mongodb://example.com:2017, mongodb+srv://server.example.com:2017 .User
- user for connection to Mongo DB.Password
- password for user to connect with Mongo DB.Authentication Database
- database that used for authentication user. Default: admin. If you connect to your database via the mongo shell with a command of the form mongo mongodb://example.com/myDatabase -u myUser -p myPassword
then you should place myDatabase
in this field. If you connect to your database via the mongo shell with a command of the form mongo mongodb://example.com/ -u myUser -p myPassword
then you should leave this field blank.The component has no required variables, however in some cases it would be beneficiary to use them. Here are the available variables:
MONGO_CONNECTION_TIMEOUT
- timeout in ms for connection to MongoDB. Default is 10000
.EIO_REQUIRED_RAM_MB
- Number of RAM megabytes provided to container. Additional memory may be needed in cases when incoming massage is big (up to 10MB).This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
Please check the dedicated page for action functions. Below are the existing action functions, each linked to the section where more explanation is given.
LDAP
, Kerberos
(GSSAPI
) and X.509
ObjectId
criteria is not supported in Lookup By Unique Criteria action, Lookup by ID action should be used in this case2.6+
Click here to learn more about the elastic.io iPaaS