- Name (required): Provide a clear and distinguishable Name for the new connection. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
- Connection type (required): Select MongoDB or accept the default value if youʼre editing a MongoDB connection.
- Mode (required): Select one of the following options:
- Cloud to connect to a publicly accessible server application
- On-premise to connect to a server that is publicly inaccessible and has integrator.io agent installed on it, such as a production server environment
- Agent (required, if On-premise selected for 3. Mode; otherwise disabled): Select an agent from the list. To connect to an on-premise application, integrator.io requires that an agent be installed on a networked computer. An agent is a small application that allows you to connect to data behind your firewall. When installing an agent, you will specify a unique access token, which then populates the Agent drop-down list. The installed agents connect to integrator.io and establish a reverse SSH tunnel, allowing secure communication without the need to whitelist integrator.io’s IP addresses in your firewall settings. A single agent can be used by multiple different connections.
- Host(s) (required): Enter the hostname or IP address for your MongoDB instance – for example: mongodb-instance1.com or 172.16.254.1.
By default, integrator.io will connect to port 27017. If you need to connect to a different port, then append :port to your hostname – for example: mongodb-instance1.com:12345 or 172.16.254.1:98765.
If you are connecting to a MongoDB cluster, then list all hostname:port combinations, separated by commas – for example: mongodb-instance1.com:12345,mongodb-instance2.com:12345,mongodb-instance3.com:12345.
- Database name (required): Enter the name of the database you would like to connect to. (No default database is assumed; you must specify a database to help safeguard against accidentally connecting to the wrong one.)
- Username (optional): If your MongoDB instance requires login credentials, enter the username for the account set up by the server administrator.
- Password (optional): Enter the password for this account, if required.
The following example reviews a MongoDB Atlas installation. First, click the Connect button on your cluster:
In the resulting Connect to... menu, click Connect your application.
Under Choose your driver version, select the following settings:
- Driver: Node.js
- Version: 2.2.12 or later
Important: Do not set Version to MongoDB 3.0+.
Before closing this dialog, under Connection string only click the Copy button. Then, paste the contents into a text editor. For example:
The properties we need from this string are derived as follows:
|Connection field||Connection string||Sample value|
|6. Database name||test||test|
- Test (optional): click to try connecting to MongoDB before saving your changes.
Click the Save button to test and commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow).