Last modified by Hera Guo on 2024/11/11 16:48
From version 6.1
edited by Hera Guo
on 2024/11/07 17:21
Change comment: There is no comment for this version
To version 7.1
edited by Hera Guo
on 2024/11/11 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -546,7 +546,6 @@
546 546  |DEG|1|(% style="width:1639px" %)Convert the angle measured in radians to an approximate equivalent angle measured in degrees|(% style="width:82px" %)
547 547  |CUSTOM|1-16|(% style="width:1639px" %)Custom functions such as (x-32)/1.8 use this function to specify complex mathematical expressions|(% style="width:82px" %)
548 548  
549 -
550 550  According to the running results, there are two types of exits for this rule node: Success and Failure.
551 551  
552 552  A simple usage example is as follows:
... ... @@ -689,13 +689,107 @@
689 689  === 6.4.5 log ===
690 690  
691 691  
691 +This node is used to encode the outgoing message into a string and record it in the system's log file. Its configurable contents include:
692 692  
693 +**Name:** required field, indicating the name of the node;
693 693  
695 +**Function AKS String:** The format of logging can be defined through encoding. The input parameters of the function include msg (message body), metadata (message metadata), msgType (message type), and the return value of the function should be a string type;
694 694  
697 +**Explanation: **Non mandatory field, additional explanation;
698 +
699 +According to the execution status, the rule node has two exits, Success and Failure.
700 +
701 +
695 695  == 6.5 external ==
696 696  
697 697  === 6.5.1 kafka ===
698 698  
706 +
707 +
708 +
709 +
710 +This node can forward the message body of incoming messages to Kafka, essentially configuring a Kafka producer client. The configurable contents include:
711 +
712 +**Name:** required field, indicating the name of the node;
713 +
714 +**Topic pattern: **required field, specify the topic of message sending, use ${metadataKey} to obtain the value of the corresponding attribute in the metadata as the topic, and use $[messageKey] to obtain the value of the corresponding attribute in the message body as the topic;
715 +
716 +**Key pattern:** Non mandatory field, used to specify the Key of the message. Messages with the same Key will be assigned to the same partition;
717 +
718 +**Bootstrap servers:** required field, specify the address of Kafka service;
719 +
720 +**Automatically retry times if failures: **Non mandatory field, used to specify the number of retries when message sending fails, default is 0;
721 +
722 +**Produce batch size:** Non mandatory field, used to specify the batch size in bytes, default is 16384;
723 +
724 +**Time to buffer locally: **Non mandatory field, used to specify the maximum duration of the local buffer window, default is 0;
725 +
726 +**Client buffer max size: **Non mandatory field, used to specify the maximum buffer size (in bytes) for sending messages, default is 33554432;
727 +
728 +**Number of acknowledgments:** Required field, used to specify how many replicas in the partition receive the message, and the producer considers the message to have been successfully written. Setting it to 0 can ensure maximum throughput; Setting acks to -1 or all ensures the strongest reliability; A compromise solution between message reliability and throughput when tasks are set to 1;
729 +
730 +**Key serializer: **required field, default is org.apache.kafka.common.serialization StringSerializer；
731 +
732 +**Value serializer: **required field, default is org.apache.kafka.common.serialization StringSerializer；
733 +
734 +**Other properties:** Any other properties can be provided for Kafka client connections, added in the form of key value pairs, and multiple pairs can be added;
735 +
736 +**Add Message metadata key value pairs to Kafka record headers: **optional. When checked, the metadata of the message will be added to the headers of the Kafka client connection in the form of key value pairs;
737 +
738 +**Explanation: **Non mandatory field, additional explanation;
739 +
740 +According to the forwarding situation, the rule node has two exits, Success and Failure.
741 +
742 +A simple configuration example is as follows:
743 +
744 +
745 +
746 +[[image:1731314285322-562.png||height="1007" width="1796"]]
747 +
748 +[[image:1731314350091-205.png||height="1006" width="1792"]]
749 +
750 +
751 +
699 699  === 6.5.2 mqtt ===
700 700  
754 +
755 +
756 +
757 +
758 +This node can forward the message body of incoming messages to the Mqtt server. Its configurable contents include:
759 +
760 +**Name:** required field, indicating the name of the node;
761 +
762 +**Topic pattern:** required field, used to configure the topic, can be a static string, or can use message metadata properties through ${DeviceType};
763 +
764 +**Host:** required field, used to configure the Mqtt proxy server address;
765 +
766 +**Port: **required field, used to configure the Mqtt proxy server port, default is 1883;
767 +
768 +**Connection timeout: **required field, used to configure the timeout period (in seconds) for connecting to the Mqtt server, default is 10;
769 +
770 +**Client ID:** Non mandatory field, used to configure the client ID. If not specified, the default generated client ID will be used;
771 +
772 +**Add Service ID as suffix to Client ID: **optional, can only be checked after configuring the Client ID. Checking it will add the Service ID as a suffix to the Client ID;
773 +
774 +**Clean session: **optional, configurable whether to delete session, checked by default;
775 +
776 +**Retained: **optional, configurable whether to keep the message, not checked by default;
777 +
778 +**Enable SSL: **optional, used to enable/disable secure communication, not checked by default;
779 +
780 +**Credentials:** Mqtt connection credentials. The system provides three connection credential verification methods, namely Anonymous (unverified), Basic (username and password verification), and PEM (credential file verification);
781 +
782 +**Explanation: **Non mandatory field, additional explanation;
783 +
784 +According to the forwarding situation, the rule node has two exits, Success and Failure.
785 +
786 +A simple configuration example is as follows:
787 +
788 +
789 +
790 +[[image:1731314882091-776.png||height="917" width="1790"]]
791 +
792 +
793 +
701 701  === 6.5.3 rest api call ===
1731314285322-562.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +191.2 KB
Content
1731314350091-205.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +186.1 KB
Content
1731314882091-776.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.hera
Size
... ... @@ -1,0 +1,1 @@
1 +197.4 KB
Content