RabbitMQ Source

Step 4 - Connection and Message Settings

Connection URI

The Connection URI is the address used to establish a connection with an AMQP server.

e.g. amqp://guest:guest

e.g. amqp://guest:guest@localhost:2354.

Default Value
Possible Data Type

STRING

Heartbeat Interval

The Heartbeat Interval specifies the duration in seconds after which the RabbitMQ server and client libraries should assume the peer TCP connection to be unresponsive or down.

Default Value
Possible Data Type

60

INTEGER

Exchange Name

The Exchange Name is an identifier for the exchange, which determines how to handle messages it receives.

If an exchange with the same name already exists in the RabbitMQ server, it will be used instead of creating a new one.

Default Value
Possible Data Type

STRING

Exchange Type

The Exchange Type defines the category of the exchange. The available options include Direct, Fanout, Topic, and Headers.

Exchange Type Descriptions

  • Direct Exchange: Messages are routed to queues based on the message's routing key. It's a straightforward and precise method where the message goes to the queues whose binding key exactly matches the routing key of the message. Ideal for scenarios where direct and selective routing of messages is needed.

  • Fanout Exchange: Routes messages to all of the queues bound to it, without considering any routing keys. It's like a broadcast mechanism that efficiently disseminates messages to multiple destinations simultaneously. This type is useful in situations where the same message needs to be delivered to multiple queues.

  • Topic Exchange: Routes messages to one or many queues based on matching between a message routing key and the pattern that the queues are bound with. This type supports routing based on multiple criteria and wildcards, offering a flexible and powerful routing mechanism. It's well-suited for complex routing scenarios where messages are categorized into multiple criteria.

  • Headers Exchange: Headers Exchanges use the message header attributes for routing, ignoring the routing key. Unlike Direct and Topic exchanges, it routes based on header values and can use multiple attributes as criteria for routing. This type is particularly useful for routing decisions based on a rich set of message attributes, offering a high degree of routing flexibility.

Default Value
Possible Data Type

Direct

STRING

Routing Key

The Routing Key is like an address that the exchange uses to decide how to route messages to queues. It is essential to provide a routing key when the exchange type is set to Direct or Topic.

Default Value
Possible Data Type

STRING

...X

Step 5 - Exhange, Queue Durability and Deletion

Durable Exchange

When Durable Exchange is enabled by setting it to ON, the declared exchange will persist even after the broker is restarted.

Default Value
Possible Data Type

OFF

Auto Delete Exchange

The Auto-Delete Exchange option, when enabled, causes the exchange to be automatically removed when it is no longer in use.

Default Value
Possible Data Type

OFF

Durable Queue

When the Durable Queue option is set to true, the declared queue will persist through broker restarts.

Default Value
Possible Data Type

OFF

Exclusive Queue

The Exclusive Queue setting, when enabled, makes the queue exclusively available for the current connection. If disabled, the queue can be used by other connections.

Default Value
Possible Data Type

OFF

Auto Delete Queue

The Auto-Delete Queue option, when enabled, causes the queue to be automatically removed when it is no longer in use.

Default Value
Possible Data Type

OFF

Step 6 - Secure Communication

Enable TLS Encryption

TLS Encryption indicates if an encrypted communication channel should be established. Unless a Runner-level Vault is activated for the Node; a set of randomly generated JVM Secrets (Truststore and Keystore Passowords) will be utilized.

Default Value
Possible Data Type

ON

Certificates

You can upload utilize that are already uploaded in Certificates or upload a new one from below.

TLS Version

TLS Version specifies the version of TLS/SSL to be used for the secure communication.

Default Value
Possible Data Type

SSL

...X

Step 7 - Message Handling and Performance

Message Acknowledgment

When the Message Acknowledgment is set to OFF, the server expects explicit acknowledgments for delivered messages.

Default Value
Possible Data Type

ON

STRING

Consumer Thread Pool Size

The Consumer Thread Pool Size defines the number of consumer threads that will be registered.

Default Value
Possible Data Type

1

INTEGER

Step 8 - Preview

In Preview Step, you're provided with a concise summary of all the changes you've made to the RabbitMQ Source Node. This step is pivotal for reviewing and ensuring that your configurations are as intended before completing node setup.

  • Viewing Configurations: Preview Step presents a consolidated view of your node setup.

  • Saving and Exiting: Use the Complete button to save your changes and exit the node and return back to Canvas.

  • Revisions: Use the Back button to return to any Step of modify node setup.

The Preview Step offers a user-friendly summary to manage and finalize node settings in Cortex.

PreviousKafka SourceNextgRPC Source

Last updated