Skip to main content
Version: 1.0

MongoDB Getting Started

MongoDB is a scalable, high-performance, open source NoSQL database written in C++.MongoDB, Inc. is the company behind the database for GIANT ideas, offering the best of traditional databases as well as the flexibility, scale and performance today’s applications require. We build MongoDB and the drivers, offer software and services, run MongoDB University (which has trained over 350,000 engineers in MongoDB), and sponsor the MongoDB community.

If you have installed Websoft9 MongoDB, the following steps is for your quick start


  1. Get the Internet IP of your Server on Cloud
  2. Check your Inbound of Security Group Rule of Cloud Console to ensure the TCP:27017,9091 is allowed
  3. Complete Five steps for Domain if you want to use Domain for MongoDB
  4. Get default username and password of MongoDB

MongoDB Initialization

Steps for you

You should verify the MongoDB when completed deployment:

Check MongoDB

  1. Use the SSH to connect Server, and run the command below to view the installation information and running status
    cd /data/apps/mongodb && sudo docker compose ls
  2. You can ge the message from SSH " STATUS: running(1) " when MongoDB is running

Connect MongoDB

  1. Use the SSH to connect Server, and run MongoDB shell (Don't have password?)

    $ docker exec -it mongodb mongo admin -u root -p YOURPASSWORD
    MongoDB shell version v5.0.10
    connecting to: mongodb://
    {"t":{"$date":"2022-08-10T03:05:34.194Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_option failed with std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available","message":"Protocol not available","category":"asio.system","value":92}}}
    Implicit session: session { "id" : UUID("030a4e0b-54cf-4f93-aa90-792b10c478f7") }
    MongoDB server version: 5.0.10
    Warning: the "mongo" shell has been superseded by "mongosh",
    which delivers improved usability and compatibility.The "mongo" shell has been deprecated and will be removed in
    an upcoming release.
    For installation instructions, see
  2. List all databases and users

    # list all databases
    show dbs

    # use admin, and list all users
    use admin
    show users

Having trouble?

Below is for you to solve problem, and you can contact Websoft9 Support or refer to Troubleshoot + FAQ to get more.

Does MongoDB enable account authentication by default?

YES, Mongodb authentication is enabled by default.

MongoDB QuickStart

To learn more about the use of mongodb, refer to the official document MongoDB Administration

MongoDB Setup

Enable MongoDB remote connection

  1. Use SSH to connect MongoDB server and modify the MongoDB configuration file

    #1 set authorization **disabled** to **enabled**
    authorization: enabled

    #2 set bindIP to
    port: 27017
    bindIp: means any Internet IP can connect your MongoDB

  2. Restart MongoDB service

    sudo docker restart mongodb
  3. Go to the Cloud Console and enable the TCP:27017 port of Security Group

Close MongoDB access authentication

Mongodb authentication is enabled by default, and can be closed according to the following process:

  1. Edit MongoDB configuration file, comment out the environment variable user and password.

    image: mongo:${APP_VERSION}
    restart: always
    container_name: ${APP_NAME}
    - ${APP_MONGO_PORT}:27017
  2. Recreate MongoDB container

    cd /data/apps/mongodb
    sudo docker compose up -d

MongoDB web GUI

Now, we will introduce how to use MongoDB compass


When completed the preparation, you can use the GUI now

  1. Open Chrome or Firefox on your local PC to visit URL http://Internet IP:9091, follow the prompts to enter the user name and password(Don't have password?)
  2. Click the MongoDB compass icon on the web desktop to enter MongoDB compass
  3. Fill in the correct items and connect MongoDB
    # example connect string
  4. Go go MongoDB Compass console when connect successfully

Planning data model

MongoDB as a kind of database, it is also similar to the traditional RDBMS, that is, planning the data model and establishing the database paradigm.
Only in this way can the performance of the database be better developed.

The main design points of data planning include:

  • Use data paradigm
  • Using embedded document anti paradigm
  • Use fixed sets
  • Consider document enlargement
  • Planning indexing, sharding, and replication
  • Planning data lifecycle

Useful MongoDB Command

show all database, create database, insert data

> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB


#2 create database test, if there have test, it's means switch to test, example
> use test
switched to db test

# show the current database
> db

# show the current database users
> show users


#3 Insert data into the database test, example
> db.test.insert({"name":"company"})
WriteResult({ "nInserted" : 1 })


Delete the database

> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
test 0.000GB
websoft9 0.000GB

> use test
switched to db test
> use test
> db.dropDatabase()
{ "dropped" : "test", "ok" : 1 }
> show dbs
admin 0.000GB
config 0.000GB
local 0.000GB
websoft9 0.000GB

Create administrator user

> mongo
> use admin
switched to db admin
> db.createUser( { user: "webs_admin", pwd: "websoft9", roles: ["userAdminAnyDatabase"] } )
Successfully added user: { "user" : "webs_admin", "roles" : [ "userAdminAnyDatabase" ] }

# Show account number
> show users
"_id" : "admin.webs_admin",
"user" : "webs_admin",
"db" : "admin",
"roles" : [
"role" : "userAdminAnyDatabase",
"db" : "admin"
"mechanisms" : [

Password management

Modify password

You can modify the password of root user which added on your MongoDB by the following command

$ docker exec -it mongodb mongo admin -u root -p YOURPASSWORD
MongoDB shell version v4.0.18
connecting to: mongodb://
> db = db.getSiblingDB('admin')
> db.changeUserPassword("root", "NEWPASSWORD")
> exit

Reset password

Reset password is the process of resetting a new password through special solutions in case the password has been forgotten.

  1. Edit MongoDB configuration file, comment out the environment variable user and password.

    image: mongo:${APP_VERSION}
    restart: always
    container_name: ${APP_NAME}
    - ${APP_MONGO_PORT}:27017
  2. Recreate MongoDB container

    cd /data/apps/mongodb
    sudo docker compose up -d
  3. Run the MongoDB command to set new password

    $ docker exec -it mongodb nongo
    > db = db.getSiblingDB('admin')
    > db.changeUserPassword("root", "NEWPASSWORD")
  4. Edit MongoDB configuration file, make the environment variable user and password effective

    image: mongo:${APP_VERSION}
    restart: always
    container_name: ${APP_NAME}
    - ${APP_MONGO_PORT}:27017
  5. Recreate MongoDB container, and the new password will take effect immediately

    cd /data/apps/mongodb
    sudo docker compose up -d

Reference sheet

The below items and General parameter sheet is maybe useful for you manage MongoDB

Run docker ps, view all containers when MongoDB is running:

CONTAINER ID   IMAGE                                                   COMMAND                  CREATED         STATUS                  PORTS                                                                                  NAMES
80130e1088b2 websoft9dev/mongocompass:v1.31 "/dockerstartup/kasm…" 2 minutes ago Up About a minute 4901/tcp, 5901/tcp,>6901/tcp, :::9091->6901/tcp mongocompass
c17d12157c01 mongo:latest "docker-entrypoint.s…" 4 minutes ago Up 4 minutes>27017/tcp, :::27017->27017/tcp mongodb


MongoDB install directory: /data/apps/mongodb
MongoDB data directory: /data/apps/mongodb/data/mongo_data
MongoDB configuration file: /data/apps/mongodb/src/mongod.conf
MongoDB compose file: /data/apps/mongodb/docker-compose.yml


9091HTTP access MongoDB CompassOptional
27017MongoDB ServerOptional


docker exec -i mongodb mongo --version


sudo docker start | stop | restart  mongodb
sudo docker start | stop | restart mongocompass



The service end of MongoDB is called mongod. After entering the container, you can accept a series of parameters through the mongod command or through the configuration file:

CLI Arguments

  -v [ --verbose ] [=arg(=v)]           be more verbose (include multiple times
for more verbosity e.g. -vvvvv)
--quiet quieter output
--port arg specify port number - 27017 by default
--logpath arg log file to send write to instead of
stdout - has to be a file, not
--syslog log to system's syslog facility instead
of file or stdout
--syslogFacility arg syslog facility used for mongodb syslog
--logappend append to logpath instead of
--logRotate arg set the log rotation behavior
--timeStampFormat arg Desired format for timestamps in log
messages. One of ctime, iso8601-utc or
--setParameter arg Set a configurable parameter
-h [ --help ] show this usage information
--version show version information
-f [ --config ] arg configuration file specifying
additional options
--bind_ip arg comma separated list of ip addresses to
listen on - localhost by default
--bind_ip_all bind to all ip addresses
--ipv6 enable IPv6 support (disabled by
--listenBacklog arg (=128) set socket listen backlog size
--maxConns arg max number of simultaneous connections
- 1000000 by default
--pidfilepath arg full path to pidfile (if not set, no
pidfile is created)
--timeZoneInfo arg full path to time zone info directory,
e.g. /usr/share/zoneinfo
--keyFile arg private key for cluster authentication
--noauth run without security
--transitionToAuth For rolling access control upgrade.
Attempt to authenticate over outgoing
connections and proceed regardless of
success. Accept incoming connections
with or without authentication.
--clusterAuthMode arg Authentication mode used for cluster
authentication. Alternatives are
--nounixsocket disable listening on unix sockets
--unixSocketPrefix arg alternative directory for UNIX domain
sockets (defaults to /tmp)
--filePermissions arg permissions to set on UNIX domain
socket file - 0700 by default
--fork fork server process
--slowms arg (=100) value of slow for profile and console
--slowOpSampleRate arg (=1) fraction of slow ops to include in the
profile and console log
--networkMessageCompressors [=arg(=disabled)] (=snappy)
Comma-separated list of compressors to
use for network messages
--auth run with security
--clusterIpSourceWhitelist arg Network CIDR specification of permitted
origin for `__system` access.
--profile arg 0=off 1=slow, 2=all
--cpu periodically show cpu and iowait
--sysinfo print some diagnostic system
--noIndexBuildRetry don't retry any index builds that were
interrupted by shutdown
--noscripting disable scripting engine
--notablescan do not allow table scans
--shutdown kill a running server (for init

Replication options:
--oplogSize arg size to use (in MB) for replication op
log. default is 5% of disk space (i.e.
large is good)
--master Master/slave replication no longer
--slave Master/slave replication no longer

Replica set options:
--replSet arg arg is <setname>[/<optionalseedhostlist
--replIndexPrefetch arg specify index prefetching behavior (if
secondary) [none|_id_only|all]
--enableMajorityReadConcern [=arg(=1)] (=1)
enables majority readConcern

Sharding options:
--configsvr declare this is a config db of a
cluster; default port 27019; default
dir /data/configdb
--shardsvr declare this is a shard db of a
cluster; default port 27018

SSL options:
--sslOnNormalPorts use ssl on configured ports
--sslMode arg set the SSL operation mode
--sslPEMKeyFile arg PEM file for ssl
--sslPEMKeyPassword arg PEM file password
--sslClusterFile arg Key file for internal SSL
--sslClusterPassword arg Internal authentication key file
--sslCAFile arg Certificate Authority file for SSL
--sslClusterCAFile arg CA used for verifying remotes during
outbound connections
--sslCRLFile arg Certificate Revocation List file for
--sslDisabledProtocols arg Comma separated list of TLS protocols
to disable [TLS1_0,TLS1_1,TLS1_2]
--sslWeakCertificateValidation allow client to connect without
presenting a certificate
allow client to connect without
presenting a certificate
--sslAllowInvalidHostnames Allow server certificates to provide
non-matching hostnames
--sslAllowInvalidCertificates allow connections to servers with
invalid certificates
--sslFIPSMode activate FIPS 140-2 mode at startup

Storage options:
--storageEngine arg what storage engine to use - defaults
to wiredTiger if no data files present
--dbpath arg directory for datafiles - defaults to
--directoryperdb each database will be stored in a
separate directory
--noprealloc disable data file preallocation - will
often hurt performance
--nssize arg (=16) .ns file size (in MB) for new databases
--quota limits each database to a certain
number of files (8 default)
--quotaFiles arg number of files allowed per db, implies
--smallfiles use a smaller default file size
--syncdelay arg (=60) seconds between disk syncs (0=never,
but not recommended)
--upgrade upgrade db if needed
--repair run repair on all dbs
--repairpath arg root directory for repair files -
defaults to dbpath
--journal enable journaling
--nojournal disable journaling (journaling is on by
default for 64 bit)
--journalOptions arg journal diagnostic options
--journalCommitInterval arg how often to group/batch commit (ms)

WiredTiger options:
--wiredTigerCacheSizeGB arg maximum amount of memory to allocate
for cache; defaults to 1/2 of physical
--wiredTigerJournalCompressor arg (=snappy)
use a compressor for log records
--wiredTigerDirectoryForIndexes Put indexes and data in different
--wiredTigerMaxCacheOverflowFileSizeGB arg (=0)
Maximum amount of disk space to use for
cache overflow; Defaults to 0
--wiredTigerCollectionBlockCompressor arg (=snappy)
block compression algorithm for
collection data [none|snappy|zlib]
--wiredTigerIndexPrefixCompression arg (=1)
use prefix compression on row-store
leaf pages

Free Monitoring options:
--enableFreeMonitoring arg Enable Cloud Free Monitoring
--freeMonitoringTag arg Cloud Free Monitoring Tags

Configuration File

There are some differences between the parameters used in the configuration file and the command line. Mongodb currently [configuration file] ,
the configuration group mainly includes:

  • systemLog Options
  • processManagement Options
  • cloud Options
  • net Options
  • security Options
  • setParameter Option
  • storage Options
  • operationProfiling Options
  • replication Options
  • sharding Options
  • auditLog Options
  • snmp Options

The following is a typical configuration file:

fork: true
bindIp: localhost
port: 27017
dbPath: /var/lib/mongo
destination: file
path: "/var/log/mongodb/mongod.log"
logAppend: true
enabled: true


MongoDB Shell is MongoDB's a built-in interactive JavaScript shell enables you to access, configure and manage mongodb databases, users, etc.
Using this shell, you can perform a variety of tasks, from setting up user accounts to creating databases, and then querying the contents of databases.

# log in Mongo Shell without authenticating

# log in Mongo Shell witt authenticating
mongo admin --username root -p

MongoDB shell version v4.0.18
connecting to: mongodb://
Implicit session: session { "id" : UUID("e808b886-30db-41dd-9464-40b52f041107") }
MongoDB server version: 4.0.18
> help help on db methods help on collection methods sharding helpers replica set helpers
help admin administrative help
help connect connecting to a db help
help keys key shortcuts
help misc misc things to know
help mr mapreduce

show dbs show database names
show collections show collections in current database
show users show users in current database
show profile show most recent system.profile entries with time >= 1ms
show logs show the accessible logger names
show log [name] prints out the last segment of log in memory, 'global' is default
use <db_name> set current database list objects in collection foo { a : 1 } ) list objects in foo where a == 1
it result of the last line evaluated; use to further iterate
DBQuery.shellBatchSize = x set default number of items to display on shell
exit quit the mongo shell

Mongodb shell has two ways to interact with the database:

  • Command line interactive operation
  • Run the command script stored in the file (for example: shell_script.js)


MongoDB Drivers API Documentation