Search docs.molo17.com
    A newer version of this documentation is available.
    View Latest (v2.3)

    Static Solace PubSub+ agent

    Target Solace PubSub+

    Prerequisites

    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 permission to post to the above-mentioned topics;

    • Valid certificate in case of SASL authentication.

    Setup via Web UI

    • Hostname / IP Address: The host address of your PubSub+ cluster;

    • Port: Optional, defaults to 55555;

    • Username: Username with read & write access role to the cluster;

    • Password: Password belonging to the given username;

    • Message VPN: The Message VPN name;

    Custom properties

    • topicPrefix: (optional, defaults to NULL) String value that defines a prefix used in conjunction with the entity name 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 to know more about it;

    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": "XYZ-123.solacecloud.com",
            "port": 55555,
            "username": "",
            "password": "",
            "maxConnectionsCount": 100,
            "enableTls": true,
            "certificatePath": "/myPath/cert.p8"
          },
          "customHostCredentials": {
            "messageVpn": "myMessageVpn"
          }
    }'