The following parameters are supported for the RabbitMQ Outbound Endpoint:
Parameter |
Value |
Required |
---|---|---|
Name |
Name of the Service Endpoint. |
X |
RabbitMqMethod |
There are 2 options: Queue: this inbound endpoint connects to the existing queue specified in the 'Queue' field. Exchange: this inbound endpoint creates a temporary queue which connects to the existing exchange specified in the 'Exchange' field, depending on the exchange type: •Fanout: gets every message sent to the exchange. •Direct: gets every message sent to the exchange with a matching binding key. •Topic: gets every message sent to the exchange if the topic filter applies to the binding key.
|
X |
Type |
Type of the Service Endpoint. The value is preset with “RABBITMQ Outbound” and cannot be changed. |
X |
Description |
Description of the Service Endpoint. |
|
Hostname |
Refers to the network address or domain name of the RabbitMQ server or broker, e.g. localhost. |
X |
Port |
RabbitMQ port. Example: •5672: RabbitMQ main port •5671: TLS-encrypted AMQP |
|
Queue |
The named, durable, and persistent data structure where messages are temporarily stored until they are consumed by a consumer or subscriber. The queue must already exist on the RabbitMQ message broker. |
X |
Exchange |
The exchange receives messages from producers and determines how to route or forward these messages to one or more queues based on certain rules defined by the exchange type. Exchange is used with the Fanout, Direct and Topic methods. The exchange must already exist on the RabbitMQ message broker. |
X |
Binding Key |
For direct exchanges, the binding key is used for exact matching. When a message is published to a direct exchange, it carries a routing key. The exchange will then route the message to a queue that is bound to it with a binding key that exactly matches the message's routing key. Topic exchanges use pattern matching with the binding key to determine how messages are routed. The binding key can contain wildcards, which allows for more flexible routing. |
|
Persist message |
If a message is marked as persistent, RabbitMQ ensures that the message is saved to disk before it is acknowledged as "published". Persistent messages survive system failures, such as RabbitMQ server restarts. There are 2 options available: •True •False |
X |
Publisher confirmation timeout |
If specified, the endpoint waits this maximal time period in milliseconds for RabbitMQ to acknowledge that the message has been successfully persisted to disk. |
|
Virtual host |
RabbitMQ is a multi-tenant system: connections, exchanges, queues, bindings, user permissions, policies and some other things belong to virtual hosts, logical groups of entities. |
|
SASL Config |
RabbitMQ supports multiple SASL authentication mechanisms: •PLAIN: SASL PLAIN authentication. This is enabled by default in the RabbitMQ server and clients, and is the default for most other clients. •EXTERNAL: authentication happens using an out-of-band mechanism such as x509 certificate peer verification, client IP address range, or similar. Such mechanisms are usually provided by RabbitMQ plugins. |
X |
Username |
Username for connection to the host. |
|
Password |
Password for connection to the host. |
|
XSL Parameter |
Comma-separated list of parameters that are made available in the XSL transformation. Example: PARA1=VALUE1,PARA2=VALUE2 These parameters can be accessed in the XSL Transformation as xsl:param: <xsl:param name="PARA1" /> <xsl:param name="PARA2" /> |
|
Request XSL file |
The UT XML is transformed into outgoing XML to create/update/delete rows in the database table. |
|
Message format |
Format of the messages that leave this service-endpoint (e.g. Json or Xml). |
X |
Secure Connection |
There are 2 options: •No SSL (default): Doesn’t use secure connection. •Use SSL: Uses secure connection. |
X |
SSL protocol |
One of the two values can be selected: TLSv1.2 or TLSv1.3. If there is another value required by the RabbitMQ-administrator, it can be typed in manually. |
|
Keystore password |
Password for rabbitmq_keystore. |
|
Truststore password |
Password for rabbitmq_truststore. |
|
Hostname verification |
There are 2 options: •No verification (default): Doesn’t verify hostname. •Verify host: Verifies hostname. |
|