Page History
Sv translation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Actions are used to define which action should be triggered when data arrive in the sender. Rules are used to define under which circumstances should these actions be triggered. Automated ActionsBy using automated actions, users choose what to do with the data. In other words, they choose what should be the output. There are 6 different actions available:
Users can choose one or more action. It is possible to use each action more than once (since IoT Data Collector 1.2). Adding an Automated ActionTo add an action, users have to click on New action, select which type of action they would like to use, and click on Continue. For some types of actions, further configuration is necessary (see below). Removing an Automated ActionTo remove an automated action, users have to click on the icon and confirm the removal. To finish the operation, users have to click on Apply to save the changes to the sender. BellaDati RESTThis action will send the data to a BellaDati Data Set via the REST API. To be able to use this action, the connection parameters and mapping have to be specified. General
Connection
Mapping
Import method
If the connection is not established at init (e.g. because BellaDati is not running), the action will try to reconnect when sending the data. Send data to BellaDati in BulksThis action will send the data to a BellaDati Module. To be able to use this action mapping have to be specified. General
Mapping
Import method
If the connection is not established, five attempts will be attempted, After that, sender will be paused. Send to a remote databaseThis action allows you to insert data directly to PostgreSQL database General
Mapping
All those informations can be found in Advanced settings of your dataset Save to FileThis action will save the output to a text file on the server. The path to the file is installation_dir/data/NameOfSender/NameOfReceiver/. General
MQTT PublishThis action is used to publish the data to an MQTT Broker. To be able to use this action, the connection parameters and the message have to be specified. General
Connection
This action will send the data via an email. To be able to use this action, the connection parameters and the message have to be specified. General
Connection
HTTP RequestBy using this option the data will be sent via HTTP with one of the standard methods (POST, GET, DELETE, PUT). This option is useful when the data should be transferred to another service or application. To be able to use this action, the connection parameters and the message have to be specified. General
Connection
TCP/IP PublishThis action is used to publish the data to a TCP/IP endpoint. To be able to use this action, the connection parameters and the message have to be specified. General
Connection
Action RulesAction rules can be used to filter outgoing data by using various type of data-driven conditions. Each action rule is defined by the Field, Operation and Value. To apply the action rule, the action has to be assigned to this rule. It is possible to add more than 1 rule and each rule can have more than 1 condition (fields). If one action has multiple rules assigned, it has to pass at least one of them (OR operation between the rules) to be executed:
If one action rule has multiple conditions (fields), the value has to match all conditions (AND operation).
Adding an Action RuleTo add a new action rule, users have to click on New filter rule. In the pop-up window, they have to fill in the name of the rule and then choose which actions should be associated with this rule (use CTRL to select/deselect multiple actions). Lastly, they need to specify at least one condition. Each condition consists of Field, Operation, and Value. Once they have the condition ready, users have to click on Add to save the rule and close the pop-up window.
As the last step, users have to click on Apply to save the changes to the sender. Editing an Action RuleTo edit an action rule, users need to click on the row. Removing an Action RuleTo remove an action rule, users have to click on the icon and confirm the action. To finish the operation, users have to click on Apply to save the changes to the sender. Action Rule OptionsFollowing operations are available:
For operation "not empty" and "empty", the compare value is not available. |
Sv translation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
アクションは、データがsenderに到着したときにトリガーするアクションを定義するために使用されます。ルールは、これらのアクションがトリガーされる状況を定義するために使用されます。 自動化アクション自動化されたアクションを使用することにより、ユーザーはデータをどのように処理するかを選択します。言い換えれば、それらは何を出力すべきかを選択します。利用可能な6つの異なるアクションがあります Actions are used to define which action should be triggered when data arrive in the sender. Rules are used to define under which circumstances should these actions be triggered. Automated ActionsBy using automated actions, users choose what to do with the data. In other words, they choose what should be the output. There are 5 different actions available:
ユーザーは1つ以上のアクションを選択できます。各アクションを複数回使用することができます(IoT Users can choose one or more action. It is possible to use each action more than once (since IoT Data Collector 1.2). Adding an Automated ActionTo add an action, users have to click on New action, select which type of action they would like to use, and click on Continue. For some types of actions, further configuration is necessary (see below). Removing an Automated ActionTo remove an automated action, users have to click on the icon and confirm the removal. To finish the operation, users have to click on Apply to save the changes to the sender. BellaDati RESTThis action will send the data to a BellaDati Data Set via the REST API. To be able to use this action, the connection parameters and mapping have to be specified. Connection2以降)。 自動化アクションの追加アクションを追加するには、ユーザーは[新しいアクション]をクリックし、使用するアクションのタイプを選択して、[続行]をクリックする必要があります。一部のタイプのアクションでは、さらに構成が必要です (以下を参照)。 自動化アクションの削除自動化されたアクションを削除するには、ユーザーはアイコンをクリックして削除を確認する必要があります。 操作を終了するには、ユーザーは[適用]をクリックして変更をsenderに保存する必要があります。 BellaDati RESTこのアクションは、REST APIを介してデータをBellaDatiデータセットに送信します。このアクションを使用できるようにするには、接続パラメーターとマッピングを指定する必要があります。 全般
接続
マッピング
If the connection is not established at init (e.g. because BellaDati is not running), the action will try to reconnect when sending the data. Save to FileThis action will save the output to a text file on the server. The path to the file is installation_dir/data/NameOfSender/NameOfReceiver/. MQTT Publishインポート方法
If the connection is not established at init (e.g. because BellaDati is not running), the action will try to reconnect when sending the data. Send data to BellaDati in BulksThis action will send the data to a BellaDati ModuleThis action is used to publish the data to an MQTT Broker. To be able to use this action , the connection parameters and the message mapping have to be specified. 全般
マッピング
インポート方法
If the connection is not established, five attempts will be attempted, After that, sender will be paused. Send to a remote databaseThis action allows you to insert data directly to PostgreSQL database 全般
マッピング
All those informations can be found in Advanced settings of your dataset Save to FileThis action will save the output to a text file on the server. The path to the file is installation_dir/data/NameOfSender/NameOfReceiver/. 全般
MQTT PublishThis action is used to publish the data to an MQTT Broker. To be able to use this action, the connection parameters and the message have to be specified. 全般
接続
EメールThis action will send the data via an email. To be able to use this action, the connection parameters and the message have to be specified. 全般
接続
HTTP リクエストBy using this option the data will be sent via HTTP with one of the standard methods (POST, GET, DELETE, PUT). This option is useful when the data should be transferred to another service or applicationThis action will send the data via an email. To be able to use this action, the connection parameters and the message have to be specified. 全般
接続
HTTP RequestBy using this option the data will be sent via HTTP with one of the standard methods (POST, GET, DELETE, PUT). This option is useful when the data should be transferred to another service or application. To be able to use this action, the connection parameters and the message have to be specified.
TCP/IP PublishThis action is used to publish the data to a TCP/IP endpoint. To be able to use this action, the connection parameters and the message have to be specified. 全般
接続
Action RulesAction rules can be used to filter outgoing data by using various type of data-driven conditions. Each action rule is defined by the Field, Operation and Value. To apply the action rule, the action has to be assigned to this rule. It is possible to add more than rule. In that case, the message has to match all the rules to be processed by the automated action. When the sender has more than one action, the rules are applied to all actions.to add more than 1 rule and each rule can have more than 1 condition (fields). If one action has multiple rules assigned, it has to pass at least one of them (OR operation between the rules) to be executed:
If one action rule has multiple conditions (fields), the value has to match all conditions (AND operation).
Adding an Action RuleTo add a new action rule, users have to click on New filter rule. In the pop-up window, they have to fill in the name of the field rule and then choose which operation they want to useactions should be associated with this rule (use CTRL to select/deselect multiple actions). Lastly, they need to specify the compare value. at least one condition. Each condition consists of Field, Operation, and Value. Once they have the condition ready, users have to click on Add to save the rule and close the pop-up window..
As the last step, users have to click on Apply to save the changes to the sender. Editing an Action RuleTo edit an action rule, users need to click on the row. Removing an Action RuleTo remove an action rule, users have to click on the icon and confirm the action. To finish the operation, users have to click on Apply to save the changes to the sender. Action Rule OptionsFollowing operations are available:
For operation "not empty" and "empty", the compare value is not available. |