Installation steps

Gluesync SQL to NoSQL for RavenDB

Prerequisites

In order to have Gluesync working on your RavenDB instance you will need to have:

  • valid client-side certificate (if required by the server) to establish a secure connection to the target database;

    • certificate password.

Basic configuration example

This module can be customized by using a configuration file, in JSON format. The file name to use must be specified as a parameter when launching the app, with the -f or --file tokens. The file should be composed of a union of the common configuration files (see here Installation steps) and source/destination specific configuration:

{
  ...
  "ravenDB": {
    "certificatesPath": "/path/to/certs/dir/cert.crt",
    "certificatesPassword": "change_me",
    "timeoutSeconds": 60
  },
}

RavenDB-specific configurations are listed under the ravenDB property:

  • certificatesPath (optional): the path to the certificate that needs to be used when connecting to a RavenDB instance using a secure connection (TLS). If omitted, no certificate is used;

  • certificatesPassword (optional): if a certificate path is specified, then this value is passed as a keystore password;

  • timeoutSeconds (optional): number of seconds to set as timeout for operations involving communication with RavenDB. The default value is 60 seconds.

RavenDB collections

RavenDB uses collections to logically map documents belonging to a specific "group". By default Gluesync makes use of RavenDB’s collections setting the same 1:1 value as the source-originating table/collection.

Looking for data modeling features or other options?

For more detailed configuration options, including the ability to perform data modeling, please have a look at the dedicated Data modeling section when sourcing from an RDBMS.