Adding a store

The process for adding a MongoDB store to GeoServer is the same as for any other file or database store.

  1. From the GeoServer web interface, click Stores, then Add a new store.

  2. Click the entry for MongoDB.

  3. Fill out the following form: Enter the following parameters:

    • Workspace: Workspace that will contain the MongoDB store.

    • Data source name: Internal name of the store.

    • Description: Internal description of the store.

    • Enabled: Toggles whether the store is enabled (and all its layers published) or not.

    • data_store: Specifies the MongoDB instance and database to connect to.


      This field requires a MongoDB client URI as specified by the MongoDB Manual. A typical URI will be of the form: mongodb:// The URI must include a database, but the database will be created if it doesn’t yet exist. Write access is only required if the database needs to be created or if other write operations such as WFS Transactions are expected. If needed, credentials can be supplied with the MongoDB client URI, in the form: mongodb://

    • schema_store: Designates the storage for inferred and manually defined schemas.


      This field can accept either a mongodb or file URI. It must be an absolute path of the form file:///, so if using a Windows path, it will need to be converted to this form: file:///C:/data/schemas/database If Linux: file:///opt/schemas/database/. The directory will be created if it does not exist, in which case write permissions will be necessary.

      The database and collection names are optional. If missing, the database name will default to geotools and the collection name to schemas. The database and collection must be writable using the credentials provided with the URI. Schemas are stored as MongoDB documents or files adhering to the JSON schema format with the schema “Type Name” (typeName) as the key.


    MongoDB store parameters

  4. When finished, click Save.

The store will be created, and any compliant MongoDB document collections can now be exposed as layers through standard GeoServer processes.