Mongo Server Options

Displays the folder path where the MongoDB Server database resides.

 

Users can choose to relocate this folder and its data contents by stopping the MongoDB Service, moving the folder and its contents, updating the Mongo Server Configuration file to point to the new folder path and restart the MongoDB Service.

 

Click this button to open the configuration file in Notepad for editing.  Note that any changes to this file will not be used by the MongoDB Server until its Service is restarted.

Displays the current file path where the MongoDB Server configuration file resides.  Users should only have to edit this file when moving the installed location of the MongoDB Server database.  Click the button next to this text box to open the configuration file in Notepad for editing.  Note that any changes to this file will not be used by the MongoDB Server until its Service is restarted.

Click this button to launch the MongoDB Compass administration tool.  This tool provides all the tools necessary to maintain your MongoDB Server and its contained data.  Users should not use this tool to delete any Collections maintained by Control Architect as this could result in ghost references.  Control Architect provides its own functions to delete both Collections and Databases while assuring that referential integrity is maintained.  This tool is installed for those users that have advanced knowledge and training working with MongoDB database deployments.

 

Specify a User name for the Mongo Server account.

Specify a Password for the Mongo Server account.  This Password is saved to your local settings using Microsoft System Security Cryptography API, which significantly reduces the chances of your account credentials being hacked.  This Password is only valid for the user that is logged into the Windows account.  Other users with valid login accounts will also have to establish their own Mongo Server authentication account.

Choose this option to show the masked Password characters.

Click this button to create a new user account with administration rights for the currently connected physical MongoDB database.  Clicking this button will start and stop the Mongo Server multiple times during the account creation process.  The status of the Mongo Server will be displayed along with a progress indication while the new user account is being created.  Wait until the progress indicator is no longer visible and the Mongo Server status LED is showing a "good" green status indication, which indicates successful completion.

 

 

If you manage multiple physical MongoDB databases in your file system, you are required to create authentication accounts for each database.  Click the Create User button when connecting to a new physical MongoDB database to create the new user account.

 

When using the Mongo Compass application you will also be required to create a new connection that uses the same authentication credentials you specified here.

Click this drop-down list to view a list of recently used physical MongoDB database paths that can be selected for attachment to your Local MongoDB Server.  Select a physical database path from this list and then click the Change Database button to change the attached MongoDB server database.

Click the drop-down button to view a list of options to execute against your Local MongoDB Server.  Clicking the button itself will execute the default option to change the Local physical database path to the selection in the drop-down list.

 

Select a menu item from the drop-down list to execute.

 

Choose this option to enable authentication for your local Mongo Server logon.  Enterprise Atlas Mongo Cloud connections use these specified credentials to update the embedded "<admin> and <password>" text with secure string values during authentication.  Remote Intranet Mongo Servers will also use the specified User Name and Password to authenticate logins.

Click this button to create a deployable Package file of your local or remote MongoDB physical database.  You can choose what logical Databases are packaged.  Typically you will use this function to copy/move a local Host Mongo database to another physical location or to create a periodic backup.

 

This is the recommended way to both upgrade and/or deploy a copy of a local database to another local or remote installation.

 

Users can optionally copy a physical MongoDB database by:

 

Example MongoDump.exe and MongoRestore.exe Command Prompt usage:

 

Click this button to unpack a previously packaged MongoDB database to your local Host or Remote Mongo Server.  Users have the option to create a new physical Mongo database path while unpacking to a local Host Server only.

Choose this option to connect to a Remote intranet Mongo Server or Enterprise Atlas Cloud installation.

 

Provide the IP Address for your remote intranet Mongo Server installation or a Connection string for your Enterprise Atlas Cloud installation in the Address field.

Provide a Port address for your remote intranet Mongo Server installation only.

 

If authentication is required, then provide your UserName and Password credentials and choose the Use MongoServer Authentication option.

Provide the IP Address for your remote intranet Mongo Server installation or a Connection string for your Enterprise Atlas Cloud installation.

 

IT administrators will either provide you an IP address to connect to your Intranet server installation or provide a DNS host name that resolves to the IP address as specified in your system HOSTS file.

Connecting to an Enterprise Atlas Cloud installation will require a connection string that will be provided by your IT administrator that must be entered in this Address field. 

 

This is a typical connection string to use when connecting to a Mongo Atlas Cloud server:

 

The connection string above begins with the format "mongodb+srv://UserName:Password" where UserName is automatically replaced by the Username text value and "<password>" is automatically replaced by the decrypted Password text value while connecting.  Do not replace the text phrases <username> and <password> or an error will occur.

 

When connecting to a MongoDB Atlas cluster the required connection string is provided to you by accessing the "Connect" button on your Atlas home page and choosing to connect from an application using the driver: "C#/.NET" version: "2.13 or later".

 

Provide a Port address for your remote intranet Mongo Server installation only.  The default port of 27017 can be used in most cases.

Click this button to validate your remote MongoDB Server connection.  This will test your authentication credentials, connection string for Mongo Atlas deployments, and port usage for remote intranet deployments.

Specify the Watchdog period in seconds as to how often to periodically poll the remote server to verify MongoDB Server connectivity.

Click this button to view the current MongoDb Server Log content.  The Log content is retrieved from the Mongo Server memory cache. 

 

If the Mongo Server is local and the Server has stopped, then the log content is retrieved by reading the physical Mongo database log file.  If an attempt to retrieve the log for a remote server fails because the remote server is not reachable, then the physical log file must be retrieved from the Mongo Server's file system.

Click this button to print the content of the Mongo Server Log view.

Click the View Log button to view the connected Mongo Server log that is cached in memory.  If the Server is not reachable due to a bad connection or a failed MongoDB Service, then this function will attempt to retrieve the physical log file from the local Mongo Server connected database.  The physical log file of a remote Mongo Server cannot be retrieved using this function.

Click this button to return back to the main application view.