AMQP is a protocol for messaging between applications or systems. In an IoT context, it's used for reliable and secure communication between devices and the cloud, supporting messaging patterns like queuing, routing, publish/subscribe.
Outputs
The AMQP node will output each device’s payload in the order that they are received.
How to Use
Implementation
In the Rayven Workflow Builder:
- Select Inputs.
- Drag the AMQP node to the canvas.
- Double click on the AMQP node to open the configuration window.
Configuration
|
Section: General |
||
|
This section contains basic configuration elements required for any AMQP implementation |
||
|
Field |
Requirement |
Comments |
|
Node Name |
Mandatory |
Enter a name for this node. This provides a handle to which you and others can refer, so it should be simple but meaningful and explain the node’s purpose. |
|
User Name |
Mandatory |
A username must be entered in the AMQP node. To ensure that data is received by the node, the same username must be entered on the hardware side. |
|
Password |
Mandatory |
The password set must be at least 8 characters long (include one lower case character, one upper case character and one special character). |
|
Host Server Port |
Mandatory |
Input a unique host server port. |
|
Host Name |
Mandatory |
Input a host name (usually will be in an URL format). Example: amqp://iotx12.rayven.io |
|
Virtual Host Name |
Mandatory |
Enter a virtual host name. |
|
Host Queue Name |
Mandatory |
Enter a host queue name. |
|
Device ID Field |
Mandatory |
Enter the field name that holds the Device ID. If this is not configured, the payload will be tied to the device __none__ by default which can be viewed using the debug node. |
|
Save Raw Data |
Optional |
When checked, the AMQP node will save the raw data from the payloads it received. Users are able to look at the raw data saved by the node by connecting a debug node. Check our documentation for the debug node. If this is unchecked, the node will not save the raw data. It will only save the recent payloads received by the node. |
|
Section: Payload Rate Limit |
||
|
Field |
Requirement |
Comments |
|
Field Name |
Optional |
Enter a field name that will allow the user to control the payload rate limit. |
|
Interval (Seconds) |
Optional |
Enter a numeric value that is greater than 0. |
|
Section: Payload Date Settings |
||
|
In the case that you would like the timestamp of the data to be based on the data coming from the device, and if the device is coordinated with a time zone, you will need to define the following three fields: |
||
|
Field |
Requirement |
Comments |
|
Date Field Name |
Optional |
Define the name of the date field coming in from your device. |
|
Date Format |
Optional |
Define the format of how the data will be coming through, for example: dd/MM/yyyy HH:mm:ss. If the date is coming through in 24 hour format, the hours need to be in capital letters, (ie. HH/mm/ss) |
|
Timezone |
Optional |
Define from a drop down list, the time zone that the device is recording the data. |
Activation
Once the node has been configured, click the Activate button and then click Save. The node is ready to receive data into the workflow.