Static RavenDB agent

Targeting RavenDB

Prerequisites

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

  • Valid user credentials with permission to read, and write to the target.

Setup via Web UI

  • Hostname / IP Address: DNS record or IP Address of your server;

  • Port: Optional, defaults to 8080;

  • Database name: Name of your target database;

  • Username: Username with read & write access to the target;

  • Password: Password belonging to the given username.

  • Certificates path: (optional) File browser to let you upload your certificates;

  • Certificates password: (optional) If a certificate path is specified, then this value is passed as a keystore password.

Specific configuration

This agent has no specific configuration properties.

Setup via Rest APIs

Here following an example of calling the CoreHub’s Rest API via curl to setup the connection for this Agent.

Connect the agent

curl --location --request PUT 'http://core-hub-ip-address:1717/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
        "hostCredentials": {
        "connectionName": "myAgentNickName",
        "host": "host-address",
        "port": 8080,
        "databaseName": "db_name",
        "username": "",
        "password": "",
        "maxConnectionsCount": 100,
        "enableTls": true,
        "certificatePath": "/myPath/cert.pem"
      }
}'

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.