Installation steps

Gluesync SQL to NoSQL for Solace PubSub+

Prerequisites

In order to have Gluesync working on your Solace PubSub+ instance you will need to have:

as many topics created one per each of the entities you’re looking to source changes from;
valid user credentials with permissions to post to the above mentioned topics;
valid certificate in case of SASL authentication.

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 parameter when launching the app, with the -f or --file tokens. The file should be composed by union of common configuration file (see here Installation steps) and source specific configuration:

{
  ...
  // (source section omitted)
  ...
  "targetHost": "SOLACEIPADDRESS",
  "targetPort": "55555",
  "targetName": "vpn-name",
  "targetUsername": "Username",
  "targetPassword": "Password",
  ...

  "solace": {
    "topicPrefix": "MYTOPICPREFIX_",
    "usePersistedMessages": true,
    "certificatesPath": "/path/to/certificate.pem"
  },
}

These following are the parameteres used to configure your PubSub+ target:

targetHost: the host address of your PubSub+ cluster;
targetPort: the port exposed by your PubSub+ cluster;
targetName: the Message VPN name;
targetUsername: username to use to connect against PubSub+;
targetPassword: password to use to connect against PubSub+.

Solace PubSub+ specific configurations are listed under the solace property:

topicPrefix (optional): string value that defines a prefix used in conjunction with the entity name in order to build the Kafka topic name;
usePersistedMessages (optional): defaults to false. If set to true it enables the usage of PubSub+ Persisted message publishing, look at this documentation in order to know more about it;
certificatesPath (required if auth in place): defaults to null, the path to your certificates;