The General tab is displayed by default when creating or opening a Workflow Bridge profile.
Workflow Bridge profile
| Setting | Description |
|---|---|
Send Reply Over Bridge | Check this if the Collection workflow shall send a reply back to the Forwarding workflow each time a Note! This only applies for the There is no timeout handling for outstanding |
Force Serialization | The Force Serialization option is enabled by default and applies to situations where the Workflows are running on the same EC. It can be disabled for a performance increase, if it can be assured that no configurations will be changed during the running of these Workflows. Note! If this option is disabled, it is strongly recommended to NOT perform any configuration changes while the Workflows are running. |
Response Timeout (s) | This is the time (in seconds) that the Workflow Bridge Forwarding agent will wait for a response for a WorkflowState UDR from the Workflow Bridge Real-time Collection agent. After the specified time, the Workflow Bridge Forwarding agent will time out and abort the workflow. The default value is "60". |
Bulk Size | Bulk Size is configured if data should be bulked by the Workflow Bridge Forwarding agent before it is sent to the collection side. Configure the number of UDRs that should be bulked. The default value is "0", which means that the bulk functionality will not be used. |
Bulk Timeout (ms) | This is the time (in milliseconds) that the Workflow Bridge Forwarding agent will wait in case the bulk size criteria is not fulfilled. Default value is "0" which is an infinite timeout. |
Number of Collectors | If you want to configure broadcasting or load balancing, i e if you want several different Workflow Bridge collecting workflow instances to be able to receive data from the forwarding workflow, you enter the number of collecting workflows you want to use in this field. The number of collecting workflows connected to the workflow bridge must not exceed the limit set by this value. In case of a batch forwarding workflow, it must be started after the specified Number of Collectors are running or it will abort. Collecting workflows that are started after the limit has been reached will also abort. Real-time forwarding workflows do not require that any collectors running when started, and the Number of Collectors represents an upper limit only. Validation of this configuration will also be performed. |
| Transport | Select the transport protocol that you prefer for the best performance, Aeron or TCP/IP. It can be wise to perform some test runs with the sort of traffic you will use later and especially check which one gives the best characteristics in terms of throughput and latency. You can always switch between Aeron or TCP/IP even on a system that is in service, but you must restart the workflow when doing this. |
| Load Balancing Strategy | Select the Load Balance Strategy for prefered scalability and redundance. The Load Balancing Strategy will be used in case you set the number of collectors to more than 1. You have three different strategies to choice from: Static: LoadIds from the UDRs can be used for determining how data should be distributed via the workflow instances. See chapter 9.83.7.2 Workflow Bridge Example Real-Time to Real-Time Scenario with Load Balancing how to use this. Dynamic: The load will be distributed over all the available collectors. The LoaId from the UDR will be used virtually and is not connected to any HW at the collecting side. (The LoadId's settings at the workflow instances will be ignored.). The LoadID will be mapped to Virtual Destinations from the UDR, For instance is it is set to 1024, The UDR should use 1-1024 as LoadIDs. Deafault is set to 1024. Virtual Destinations for Dynamic: In most cases the default setting 1024 of Virtual Destinations is sufficient and will work fine. In case you want to change this, it should be set as a number that is the power of two, i.e. 512, 1024, 2048. Since you don't know the number of destinations, that may vary, the number should be set high enough to get a decent distribution. |
UDR Types | If you enter a UDR type into the list of UDR types then workflows are validated to only allow Workflow Bridge Cycle UDRs, and UDRs of that type, to be sent into the Workflow Bridge Forwarding Agent. Click the button to select the UDR types. If you leave this field blank any UDR type can be sent to the Workflow Bridge Forwarding Agent. Click the button to remove a UDR type. |
Note!
After a Workflow Bridge profile has been changed and saved, all running workflows that are connected to this profile must be restarted.