Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision |
data_core:tcp [2022/04/18 10:39] – [Resilient Data Transfer] su | data_core:tcp [2022/04/18 10:53] (current) – [Fire & Forget] su |
---|
| |
| |
===== Resilient Data Transfer ===== | ===== Resilient Data Transfer ===== |
| |
The TCP Event Source and Sink supports resilient data transfer. | The TCP Event Source and Sink supports resilient data transfer. |
{{ :data_core:tcp_04.png?700 |}} | {{ :data_core:tcp_04.png?700 |}} |
| |
Local data collection and Ack verification //may// introduce a slight lag on the data relay process. If a super fast flow is required, paralel TCP components can be connected directly to the datasource (before local collection) and configured to "fire-and-forget" by setting the "Check Reponse" property to false. Each event will pass through both flows and are consolidated at their final Alarm Analysis destination. | ===== Fire & Forget ===== |
| |
| The above "Resilient Data Transfer" method using TCP and MSMQ is not expected to introduce any overhead, however if a faster flow was required, paralel TCP components can be chained directly and configured to "fire-and-forget" by setting the "Check Reponse" property to false. Each event will pass through both fast and resilient flows and are consolidated at their final Alarm Analysis destination. |
| |
| {{ :data_core:tcp_05.png?700 |}} |
| |
| |