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, use 443 if TLS is enabled;
Database name: Name of your target database;
Certificates path: (optional) File browser to let you upload your certificates (.pem required, with both private key and certificate);

Specific configuration

This agent supports the following configuration properties:

Minimum batch size: Minimum number of documents to be sent in a batch, defaults to 500. Anything below that trashold will be sent with the default operation APIs;

Setup via Rest APIs

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

Connect the agent

curl --location --request PUT 'http://core-hub-ip-address/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",
        "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.