Distributed Message Reply#
The Distributed Message Reply is responsible for sending a reply to a listener after receiving a request. Upon activation, the task constructs a reply message using the provided serviceName, id, and data, then sends it to the listener. It expects an immediate confirmation reply indicating that the message was successfully received.
Details#
| Fields | Details |
|---|---|
| Scope | Connect IoT Factory Automation Enterprise Integration Data Platform |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| Id | string | Unique identifier for the request being replied to. | |
| Data | Object | Payload of the request to be included in the reply. | |
| Is Success | Boolean | Indicates if the reply is successful | |
| Error Message | string | Describes any error if the reply is not successful. | |
| Enable/Disable | Any | Activates the task |
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| Success | Boolean | If there was no problem emits a true | |
| Error | Error | Error that occurred during the processing of this task |
Settings#
On the General Tab, you have the usual settings and the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Service Name | string | Specifies the name used in the message subject for identifying the service | ||
| Attempts | Integer | 100 | Defines the number of times the task will attempt to send a message if the initial attempt fails | |
| Sleep between attempts | Integer | 5000 | Sets the time in milliseconds that the task will wait before making another attempt after a failure | |
| Confirmation Timeout | Integer | 30 | Specifies the maximum time (in seconds) that the task will wait for a reply confirming the successful receipt of the message |
Behavior#
The tasks constructs a reply with the necessary data, and sends this reply back to the listener. It retries sending the message if the initial attempt fails, up to the defined number of attempts. The task expects an immediate confirmation upon sending the reply, and if it does not receive this confirmation within a specified timeout, it considers the operation failed.