RabbitMQ connection
The RabbitMQ connection represents a single RabbitMQ account, including sign-in credentials.
If you have multiple accounts, use a separate connection for each account and configure the connector accordingly. Pair a single connection with a different RabbitMQ operation to perform unique actions on a RabbitMQ server.
Connection tab
The RabbitMQ connector uses the AMQP 0-9-1 protocol for authentication and authorization and provides basic authentication (user name and password).
All RabbitMQ connection fields are required.
User Name - The associated user name with the RabbitMQ account. The user name specified in the connection also identifies the publisher of a message.
Password - The password of the RabbitMQ account is associated with the user name.
Host - Enter the IP address or domain name of the server that hosts the instance of RabbitMQ.
Port - Enter the port number that hosts the instance of the RabbitMQ service.
Virtual Host - The name of the RabbitMQ virtual host. To view a list of available Virtual Hosts on the RabbitMQ server, enable the RabbitMQ Management plug-in and navigate to the Admin menu.
Use TLS - Select if you are using the TLS (Transport Layer Security) protocol. It encrypts all data exchanged between and the server with a digital security certificate, which makes it difficult to steal your user name and password. You must import this certificate into . For more information, see the linked Certificate components topic.
Frame Max Size - Defines the maximum frame size (in bytes) for communication with the RabbitMQ server.
- Default is 16 KB, applied if the field is left blank or set to 0.
- Values below 4 KB trigger a runtime error.
- The connector imposes a maximum limit of 128 KB on the
Frame_maxsize connection property. Regardless of the server's configured value, any connection specification exceeding this threshold will be constrained to 128 KB. - This property is editable at design time and must be greater than 0 if specified.
Test Connection
You can test your connection settings before you use or save the connection in a process. The Test Connection ensures that your specified settings are correct, valid, and accessible. If the test connection is successful, you can save the connection. Otherwise, review and correct any incorrect settings, then test again.
You can only run the Test Connection against containers associated with your account (local runtimes, runtime clusters, and runtime clouds).