Solace Transform Processor

You can only configure Solace Transform Processor as a target. The Micro-Integration provides a flexible and efficient way to transform data on queues and topic endpoints, or transform and move data between PubSub+ event brokers.

For message headers, see Solace Transform Processor Message Headers.

Solace Transform Processor Target Parameters

You can only configure Solace Transform Processor as a target. The Micro-Integration provides a flexible and efficient way to transform data on queues and topic endpoints, or transform and move data between PubSub+ event brokers.

The following table describes the parameters for configuring your PubSub+ event broker.

Field Description
Destination Type

The destination type to send messages to. Select TOPIC or QUEUE for the topic destination or the name of the queue, respectively.

Create the required queue on your event broker service if you haven't done so already. For more information, see Creating Event Broker Services).

Topic Name The topic endpoint to publish to. This field is available only when you select TOPIC as the Destination Type.
Queue Name

The name of the queue to publish to. This field is available only when you select QUEUE as the Destination Type.
Transacted

This option specifies whether to use a transacted session (local transaction) to publish a batch of messages to the target destination. When disabled (default), the producer sequentially publishes messages within a batch. If a publishing error occurs, the entire batch is returned to the source for reprocessing. Since the entire batch is reprocessed, messages in the batch that were already published are re-published resulting in potential duplicate messages.

When enabled, up to 255 messages are published in a single transaction (local transaction). Using a local transaction guarantees that either all messages in a batch are successfully published or none of the messages in the batch are published. For more information, see Using Local Transactions.

If you use transacted sessions, it reduces the possibility of duplicate messages published to your target but increases resource usage and overhead on the event broker.