--- title: "SolaceMQ Module" slug: "solacemq" updated: 2025-10-29T16:25:30Z published: 2025-10-29T16:25:30Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # SolaceMQ Module ## Overview The **SolaceMQ Module** provides Flow steps that can be used to integrate with [Solace PubSub+](https://docs.solace.com/Get-Started/Solace-PubSub-Platform.htm) event brokers. **Solace PubSub+** is an event streaming platform used to send and receive requests between two applications. The Module includes steps that can be used to start, stop, pull, or post messages from a configured **Solace Queue**. Decisions can also act as a consumer, processing messages through a [Message Handler Flow](/v9/docs/setting-up-messaging-overview). ## Prerequisites - [Install](/v9/docs/installing-modules-decisions)the**Solace****MQ Module.** - Add the SolaceMQ Module as a [project dependency](https://documentation.decisions.com/v9/docs/project-dependencies) ### Considerations Note for Third-Party Systems and SubscriptionsCustomers are responsible for securing and maintaining accounts with third-party systems and subscriptions. --- ## Setting up SolaceMQ PubSub+ Broker The **Solace PubSub+ Broker** can be installed locally onto a container. To install the broker onto a container, [Docker Desktop](https://www.docker.com/products/docker-desktop/) will need to be installed. Once **Docker**has been installed: 1. In an elevated **Command Prompt,** run the following command to create a container with the**PubSub+ Broker**. Ensure that port 8080 is available; otherwise, the container may not start. ```shell docker run -d -p 8080:8080 -p 55555:55555 -p 8008:8008 -p 1883:1883 -p 8000:8000 -p 5672:5672 -p 9000:9000 -p 2222:2222 --shm-size=2g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --name=solace solace/solace-pubsub-standard ``` 2. Once the container has been created, navigate to **http://localhost8080** to be brought to the web console for the message broker. Enter **admin** as both the username and password to access the web console.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666718639535.png) --- ## Creating a Queue 1. To create a queue, select **Queues** in the left-hand menu, then select the **Add Queue** button in the top right-hand corner.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666718893017.png) 2. A pop-up should open. Provide a name for the Queue. This name will also be used in the **Queue Name** field in Decisions. Once the name is entered, click **Create.**![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666719092544.png) 3. A new queue should appear with the defined queue name. 4. Selecting the Queue from this menu will display a summary of the Queue. Only the **Queue Name** will be needed when configuring a connection to the queue in Decisions![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666719450956.png) --- ## SolaceMQ Settings **SolaceMQ Settings** can be found under **System > Settings Solace MQSettings.** These settings configure the default connection to the message queue host. | Configuration Options | Description | | --- | --- | | Default Host IP or Name | The configured Host IP or Server name for the SolaceMQ broker. | | Default Virtual Router Name | An optional setting used to test how messages can be sent and received from a SolaceMQ message broker. | | Default User Name | The default user name is used to establish a connection to the SolaceMQ broker. | | Default Password | The password is used to establish a connection to the SolaceMQ broker. | | Skip Provisioning (v9.12+) | Enabling this setting will prevent CLIENT_CLIENT_CREATE_ENDPOINT_FAILED errors from appearing in SolaceMQ logs. | | Use Client Certificate for Authentication | Enables SSL connections to SolaceMQ. If enabled, the following fields will require inputs: **Filename of Client Certificate, Filename of PFX/P12/PKCS12 File To Sign with, Password for PFX/P12/PKCS12 File, and SSL Trust Store Directory.** | | | Filename of Client Certificate | The name of the file containing the SSL certificate. | | Filename of PFX/P12/PKCS12 File To Sign with | The name of the file holding the signatures for the SSL certificate. | | | Password for PFX/P12/PKCS12 File | The password to access the SSL certificate. | | SSL Trust Store Directory | The full file path to the SSL Trust Store Directory. If no trust store directory is specified and TCPS is enabled, the certificate will be retrieved from system certificates. If TCPS is not enabled, no Trust Store is used at all. | --- ## Adding a Solace Message Queue Once the settings have been configured to connect to a Solace MQ host machine: 1. Navigate to**System > Integration > Jobs and Events > Message Queues**. 2. Select **Add Solace Queue** from the action bar and define the values for the message queue. **Save**. | Properties | Description | | --- | --- | | Display Name | The name of the message queue as it will appear in Decisions. | | Queue Name | The name of the message queue. | | Override Host Info | If enabled, this setting provides a textbox used to override the **Host IP or Name** field defined in SolaceMQ Settings. | | Override Virtual Router Name | Optional input is used to override**the Virtual Router Name** field defined in SolaceMQ Settings. | | Override Client Certificate in Settings | If enabled, provides textbox controls used to override **Filename of Client Certificate, Filename of PFX/P12/PKCS12 File To Sign with, Password for PFX/P12/PKCS12 File,**and**SSL Trust Store Directory**fields defined in SolaceMQ Settings.**** | | Override Client Credentials | If enabled, this setting provides textbox controls used to override the **User Name** and **Password** fields defined in SolaceMQ Settings. | | Always Try to Reconnect | If enabled, attempt to reconnect to the queue after a set period of time. | | Time Between Reconnect Attempts (ms) | Defines the time between reconnects to the message queue. By default, this setting is set to 3000. | --- ## Available Steps The following table lists all the steps available in the Module. | Step Name | Description | | --- | --- | | [Disable Solace Queue](https://documentation.decisions.com/step-library/docs/disable-solace-queue) | The Disable Solace Queue step allows users to disable a Solace message queue through a Flow. | | [Enable Solace Queue](https://documentation.decisions.com/step-library/docs/enable-solace-queue) | The Enable Solace Queue step allows users to enable a Solace message queue through a Flow. | | [Get String Message from Solace Queue](https://documentation.decisions.com/step-library/docs/get-string-message-from-solace-queue) | The Get String Message from Solace Queue step allows a set number of messages to be pulled from a Solace message queue to be used in Decisions. | | [Publish Message to Solace Topic](https://documentation.decisions.com/step-library/docs/publish-message-to-solace-topic) | The Publish Message to Solace Topic step posts messages to a Solace Topic. The Topic must be added as a queue in Decisions for the step to be used. | | [Put Binary Message in Solace Queue](https://documentation.decisions.com/step-library/docs/put-binary-message-in-solace-queue) | The Put Binary Message in Solace Queue step is used to send a message to a Solace Queue. The message sent will be in binary format. | | [Put String Messages in Solace Queue](https://documentation.decisions.com/step-library/docs/put-string-messages-in-solace-queue) | The Put String Message in Solace Queue step is used to send a message to a Solace Queue. The message sent will be as text. | --- ## Feature Changes | Description | Version | Release Date | Developer Task | | --- | --- | --- | --- | | The "SSL Trust Store Directory" text box has been unlinked from the "Use Client Certificate for Authentication" and will always be visible. | [8.15](https://documentation.decisions.com/v99/docs/version-815x-release-notes) | October 2023 | [DT-038905] | | A hidden Module called Decisions.MessageQueues Module will be downloaded automatically when any message queue Module is installed. | [9.0](https://documentation.decisions.com/v99/docs/version-9) | May 2024 | [DT-039289] | | Added the Skip Provisioning setting. | [9.12](https://documentation.decisions.com/v99/docs/version-912x-release-notes) | June 2025 | [DT-044756] |