Solace Transform Processor
You can only configure Solace Transform Processor as a target. This Micro-Integration takes events already in a queue or topic endpoint on an event broker service, optionally applies transformations, and then publishes them to a new topic.
For detailed information about the parameters you can specify for connecting to your event broker service, see Event Broker Service Connection Parameters.
You must also define at least one Micro-Integration Flow that specifies:
-
the endpoints where data is consumed from and published to. For more information, see Micro-Integration Flow Parameters.
-
how the header and payload fields should be mapped. For more information, see Mapping Headers and Payloads
For message headers, see Solace Transform Processor Message Headers.
Micro-Integration Flow Parameters
You must configure the endpoint parameters for each Flow. Each Flow can have different settings, but they all share the connection details of the parent Micro-Integration.
Event Broker Service Source Parameters
The following table describes the source parameters of the event broker service.
| Field | Description |
|---|---|
| Endpoint Type |
Select TOPIC_ENDPOINT or QUEUE to specify the type of endpoint receive from. |
| Queue Name |
The name of the queue to receive from. Endpoint Type must be QUEUE. |
| Topic Name |
The name of the topic endpoint to consume from. Endpoint Type must be TOPIC_ENDPOINT. |
| Message Selector | For the event broker service as the source, enables message filtering per endpoint. |
Event Broker Service Target Parameters
The following table describes the target parameters of the event broker service.
| 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 |
| Topic Name | The topic endpoint to publish to. Destination Type must be TOPIC. |
| Queue Name |
The name of the queue to publish to. Destination Type must be QUEUE. |
| 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. 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. |