Enterprise JMS ETL Source

The Enterprise JMS data source facilitates seamless integration with Solace, a high-performance messaging platform. This channel enables efficient PubSub messaging for real-time data exchange.

Schema Type #

See the topic Provide Schema for ETL Source → to know how schema details can be provided for data sources.

After providing schema type details, the next step is to configure the data source.

Data Source Configuration #

Configure the data source parameters that are explained below.

Connection Name #

Connections are the service identifiers. A connection name can be selected from the list if you have created and saved connection details for Enterprise JMS earlier. Or create one as explained in the topic - Enterprise JMS Connection →

Queue Name #

Enter a unique identifier for the queue.

Number of Consumers #

Specify the quantity of consumer instances that will process messages from the queue concurrently.

Batch Size #

Define the number of records to be processed in a batch per trigger.

Access Type #

The access type for delivering messages to consumer flows bound to the queue.

If EXCLUSIVE option is selected then the exclusive delivery of messages to the first bound consumer flow is executed.

If NON EXCLUSIVE option is selected then non exclusive delivery of messages to bound consumer flows in a round-robin or a partitioned pattern. For round-robin flow the default partition count is 0 and for partitioned pattern the value is not 0.

Permission Level #

The permission level for all consumers of the queue excluding the owner. The available options are NONE, READ ONLY, CONSUME, MODIFY TOPIC and DELETE.

NONE: Disallows all access.

READ ONLY: Read only access to the messages.

CONSUME: Consume (read and remove) messages.

MODIFY TOPIC: Consume messages or modify the topic.

DELETE: Consume messages, modify the topic or delete the client created endpoint all together.

Connection Timeout #

Set the maximum time, in milliseconds, the system will wait for a connection to be established before considering it as a timeout.

Connection Retries #

Specify the number of times the system should attempt to reconnect in case of a connection failure.

Retry Interval #

Set the time, in milliseconds, between each retry attempt after a connection failure. Minimum value is 50000 milliseconds (50 seconds).

Notes #

Optionally, enter notes in the Notes → tab and save the configuration.