# Solace

Category: Platforms
|
Runtime: 2.1+
|
Available: Free

# Overview

Solace node will enable the publishing of message to a queue or a topic on Solace platform .

# Setup

# Prerequisites

For Solace node to work properly, you need to have a valid subscription of Solace account (opens new window). Ensure to have the necessary connection details and credentials for connecting the platform instance.

# Installation

To install the node from designer:

  1. Go to Add more nodes option on the palette section.
  2. Check for the Solace node and click install.
  3. Once installed, the designer is required to be restarted.

To install the node from CLI:

  1. Go to your project workspace where you can see your package.json file.
  2. Run the below give npm command.
    npm i @kumologica/kumologica-contrib-solace

# Technical Details

Properties

  • Hostname (Required)
    Hostname that will be used for Solace connection. Eg: dev0301.solace.cloud.
  • Port (Required)
    Port that will be used for Solace connection. Default port is 9443. The port may vary based on cloud or on-premise instance.
  • Username (Optional)
    Username for basic authentication of Solace node with the platform.
  • Password (Optional)
    Password for basic authentication of Solace node with the platform.
  • ContentType (Optional)
    The node supports the Text and Binary content type.
  • Topic name (Optional)
    Topic endpoint name of the topic to which message to be published.
  • Queue name (Optional)
    Name of the queue to which message to be send.
  • Payload (Optional)
    Request payload to be send to a queue or published to a topic.

Supported Operations

  • Queue
    Queue operation is used for sending the message to a solace queue.
  • Topic
    Topic operation is used for publishing the message to a solace topic.

Throws

Solace node throws the following exception.

  • SolaceBadRequestError
  • SolaceResourceNotFoundError
  • SolaceAuthenticationError
  • SolaceConnectionError

Returns

Payload is overwritten by the response from this node. The returned response can be accessed in the subsequent node using msg.payload expression.