Configuring the Spring Cloud Stream Binder

Self-managed Micro-Integrations use Spring configuration options from the Spring Cloud Stream Binder for Solace and other common Spring Boot libraries.

Using the Spring Cloud Stream Binder for Solace

The Spring Cloud Stream Binder for Solace provides configuration options for the Micro-Integration, including:

endpointType, which is a consumer configuration option to configure the type of endpoint (queue or topic endpoint) that consumers read messages from
selector, which is a consumer configuration option to configure an endpoint's message selector
producer configuration options to publish messages within transacted sessions
authentication schemes to connect to a Solace event broker, such as basic authentication (default), client certificate, or OAuth 2.0

For more information about configuration options for the Spring Cloud Stream Binder for Solace, see Solace Binder Configuration Options. For the latest supported features, see the Spring Cloud Stream Binder for Solace release notes.

Micro-Integration Defaults That Override Binder Defaults

Self-managed Micro-Integrations use the Spring Cloud Stream Binder for Solace, but they apply Micro-Integration-specific defaults for some binder properties. If a Micro-Integration uses a default value that is different from the binder default, the behavior defined by the Micro-Integration takes precedence.

If you want your Micro-Integration to use the binder default for a property, you must set the property value explicitly.

The following table lists the Micro-Integration-specific defaults that differ from the Spring Cloud Stream Binder for Solace defaults.

Parameter Name Applies To Binder Default Micro-Integration Default Notes

Parameter Name	Applies To	Binder Default	Micro-Integration Default	Notes
`add-destination-as-subscription-to-queue`	Consumer	`true`	`false`	Indicates whether to add the destination as a subscription to the queue during provisioning. The Micro-Integration default is `false`, meaning that the Micro-Integration does not automatically subscribe the queue to the destination topic.
`provision-durable-queue`	Consumer and Producer	`true`	`false`	Indicates whether to provision durable queues for non-anonymous consumer groups or queue destinations. The Micro-Integration default is `false`, meaning that queues must be externally pre-provisioned on the message broker before the Micro-Integration starts.
`provision-error-queue`	Consumer	`true`	`false`	Indicates whether to provision durable error queues when `auto-bind-error-queue` is enabled. The Micro-Integration default is `false`, meaning that error queues must be externally pre-provisioned on the message broker before message processing failures occur (this applies only when `auto-bind-error-queue` is set to `true`).

add-destination-as-subscription-to-queue

Consumer

true

false

Indicates whether to add the destination as a subscription to the queue during provisioning.

The Micro-Integration default is false, meaning that the Micro-Integration does not automatically subscribe the queue to the destination topic.

provision-durable-queue

Consumer and Producer

true

false

Indicates whether to provision durable queues for non-anonymous consumer groups or queue destinations.

The Micro-Integration default is false, meaning that queues must be externally pre-provisioned on the message broker before the Micro-Integration starts.

provision-error-queue

Consumer

true

false

Indicates whether to provision durable error queues when auto-bind-error-queue is enabled.

The Micro-Integration default is false, meaning that error queues must be externally pre-provisioned on the message broker before message processing failures occur (this applies only when auto-bind-error-queue is set to true).

Using Other Spring Boot Libraries

You can also configure your Micro-Integration using the following Spring Boot libraries:

Provide feedback