PreEmptive Analytics Workbench User Guide

MongoDB Installation

The Workbench requires at least version 3.2.10 of MongoDB (or a later release in the 3.2.x series—MongoDB 2.x is no longer supported), which must be installed and running the MMAPv1 storage engine before the Workbench can be installed. The Workbench does not support SSL connections to MongoDB, as the MongoDB instance is restricted to connections from the local host.

Note: We recommend putting MongoDB's data on a separate drive. The steps assume the P:\ drive, but it can be any drive (aside from D:\ on an Azure VM); just replace P:\ with the drive you are using.

  1. Download MongoDB 3.2.x (x64) from

    • Select "Community Server".

    • From the Version drop-down, select "Windows Server 2008 R2 64-bit and later, without SSL support x64".

    • Click the "All Version Binaries" link.

    • Search for and download the ZIP archive win32/ or that of a later version.

  2. Extract the contents to the root folder, e.g. C:\. You should have a folder named something similar to C:\mongodb-win32-x86_64-2008plus-3.2.10.

  3. Rename the folder to C:\mongodb.

  4. Make a new folder for logs: C:\mongodb\log.

  5. Make a new folder for the database: P:\data\db.

  6. Make a configuration file for mongod.exe in the C:\mongodb folder. The configuration file is a text file (YAML format) named mongod.cfg that should contain lines to configure the database to use the MMAPv1 storage engine, set the logging and data locations, specify a slow operation threshold, and restrict access to the local host. For example:

    dbPath: P:\data\db
    engine: mmapv1
    destination: file
    path: C:\mongodb\log\mongo.log
    slowOpThresholdMs: 1000
    Important Note: The YAML format of the configuration above does not allow Tab characters. Use spaces instead.

  7. Install MongoDB as a Windows Service by running this command from an Administrator command prompt:

    C:\mongodb\bin\mongod.exe --config C:\mongodb\mongod.cfg --install

  8. Start the service from the command prompt using the following command:

    net start MongoDB

    If the service fails to start, check the log (C:\mongodb\log\mongo.log) for errors. Note that the service won't start if the logpath in the configuration file is pointing to a non-existent folder, or if the server can't access it. It may also fail to start if the configuration file is improperly formatted.

  9. Verify connectivity by running C:\mongodb\bin\mongo.exe which will display an error if it can’t connect to the MongoDB server. If the connection is successful, type the command exit to close the client.

  10. Per the MongoDB Production Notes, we recommend setting the Windows page file to the largest feasible multiple of 32 GB.

Workbench Version 1.2.0. Copyright © 2016 PreEmptive Solutions, LLC