Endpoint Routing for Multiple TangoDBs

The Components Table widget supports routing different device rows to different TangoDB backends.

Use this format in each devices entry:

<endpoint-selector>://<device-path>

Examples:

  • 1://low-mccs/tile/s8-1-tpm01

  • 2://low-mccs/spsstation/s8-1

  • TANGO_SECONDARY_HTTP_URL://low-mccs/smartbox/s8-1-sb01

Supported selectors

The <endpoint-selector> can be:

  • A numeric selector such as 1, 2, 3

  • A named selector such as TANGO_SECONDARY_HTTP_URL

The selector value is passed as the GraphQL endpoint variable exactly as written.

Behavior

  • Prefix present: that row is queried/subscribed using the provided endpoint selector.

  • No prefix: the row uses the default TangoDB route (no endpoint variable is sent).

  • Mixed input is supported: prefixed and unprefixed rows can be used together.

  • Prefix is per device row: all configured attributes for that row use the same selector.

Notes

  • tango://host:port/device/path is treated as a Tango host-qualified path, not as an endpoint selector.

  • Use this routing model instead of the old mccs:// convention.