Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Data is sent from a forwarding workflow to a collection workflow in a ConsumeCycleUDR. Refer to to ConsumeCycleUDR(4.23) for further information.

    In the ConsumeCycleUDR there are also fields that enable broadcasting and load balancing. Broadcasting, i e sending the same UDR to several different workflows in the collecting workflow configuration, can be made to a configurable number of workflows. Load balancing enables you to configure to which workflow each UDR should be sent, based on criteria of your choice.

Note

...

Note!

If any other UDR than ConsumeCycleUDR is routed to the forwarding agent, the bridge will only support one collector, which means that it will not be possible to broadcast or load balance.

  • Each state of a forwarding workflow is sent in a separate WorkflowState UDR to the real-time collection agent. The batch forwarding workflow sends all states from initialize to deinitialize, while a real-time forwarding workflow only sends the initialize state. The deinitialize state is sent by the real-time collection workflow if the connection goes down between the collection workflow and a forwarding workflow (batch or real-time).

    For more information regarding the workflow execution states, see Workflow Monitor (4.23).

  • User defined action UDRs can be sent from the collection workflow to communicate actions back to the forwarding workflow. For further information, see see User Defined Action UDRs(4.23).

In the collecting workflow, the APL has to be configured to communicate responses for the UDRs to the Workflow Bridge collection agent. When both the forwarding and collecting workflows are real time workflows, only responses for WorkflowState UDRs have to be configured. However, when the forwarding workflow is a batch workflow, responses for ConsumeCycle UDRs have to be configured as well.

Responses for WorkflowState UDRs are always communicated back to the forwarding workflow. If you want to communicate responses for ConsumeCycle UDRs back to the forwarding workflow as well, the Send Reply Over Bridge option has to be selected in the Workflow Bridge profile, see see Workflow Bridge Profile (4.3) for further information.

...

By using a session context, arbitrary data can be stored and managed by the Workflow Bridge real-time collection agent during the whole transaction. This is achieved by populating the SessionContext field in the InitializeCycleUDR or BeginBatchCycleUDR with the data, which is then included in all subsequent UDRs after "initialize" or "begin batch". The field is cleared at "deinitialize", when the connection to the forwarding workflow goes down.

Note

Note!

The SessionContext field is only writable in the InitializeCycleUDR and BeginBatchUDR and the session context is only available in a collection workflow.

Refer to Workflow Bridge UDR Types(4.23) for more information about the Workflow Bridge UDR types.

...

The bulk is created by the Workflow Bridge forwarding agent after a configured number of UDRs has been reached, or after a configured timeout. This is specified in the Workflow Bridge profile, see Workflow Bridge Profile (4.23) for more information.

Bulking of data can only be performed for data being sent in the ConsumeCycleUDR and not for the states that are sent in the state specific UDRs.

...

For more information on the workflow execution states, see Workflow Monitor (4.23).

Broadcasting and Load Balancing

...

You have the option to select the best transport for your needs, Aeron or TCP/IP.

Option

Description

Transport

Select the transport protocol that you prefer for best performance. Aeron or TCP/IP.

This section contains the following subsections:

...