The Workflow Bridge agents act as a bridge for communication between real-time workflows, or between a batch and a real-time workflow, within the same systemsame system.
The Workflow Bridge agents do not use any storage server to manage the data. Data is instead stored in memory cache when executing on the same EC/ECSA, or streamed directly from one agent to another, over TCP/IP, when executing on different EC/ECSAs. This provides efficient transfer of data, especially from batch to real-time workflows.
...
The same UDR can be sent to multiple workflow instances in the collection workflow using broadcasting. If the forwarding workflow has many workflow instances as well, all the UDRs sent from these instances can also be sent to all the instances in the collecting workflow.
Load balancing can be used to direct different UDRs to different workflow instances using static load balancing strategy (see Workflow Bridge Profile Configuration General Tab). Each workflow instance in the collection workflow is assigned a LoadId by adding this field to the workflow instance table in the Workflow Properties, and then entering specific Ids for each instance. In the APL code it is possible to determine specific UDRs that can have the forwarding workflow routed to a designated LoadId.
You configure the number of workflow instances you want to send UDRs to in the Workflow Bridge profile.
...
| Option | Description |
|---|---|
| Transport | Select the transport protocol that you prefer for best performance. |
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||