Switching enables a Subscriber to change the relationships between Sources and Outputs.

Where a Source represents the input streams for which the Subscriber has permission, an Output represents the hand-off to the Subscriber. An Output can specify the type of protocol used to deliver the stream and its Destination.

Switching enables the user to change which Source is sent to which Output. As an activity that has significant consequences for downstream workflows, Switching has a guard button which must be toggled on before switching can take place. Once Switching has been turned on, the user can select a Source and then a suitable Output before confirming the selection. The user may wish to think the other way round, and choose an Output which needs a different Source. The mechanism for choosing is the same.

Currently, the Switch activity is not instantaneous and a user must wait for any changes to take effect. Pipes show the required relationship configuration, and a spinning disc on the Output signifies that the change is underway.

A dotted line within the pipe indicates that the configuration being used for an Event is running on the Source.

Switching Behaviour

• Only one Source and one Output can be selected at a time
• A Source can have a relationship with more than one Output
• Switching a Source to an Output with an existing relationship will remove that previous relationship
• It is possible to change relationships while Events are running