Routing map

In a house, many systems publish and many receive. The portal's Routing map answers "who publishes what, to whom" without reading every connection: for each message type, which producer connections may publish it, and which consumer connections receive it.

It reads as a list, one line per publisher, so it works on a phone:

When newsroom-ncs (Example News) publishes story.context, it goes to web-cms (Example News) and playout-graphics (Example Graphics).

Each connection shows its app and the organisation that owns it, including other organisations' apps connected to your workspace.

Open it

Sign in to the portal, choose your workspace and open Routing map. Every member of the workspace can read it, whatever their role. Choose a message type to see only its routes.

How it is worked out

The map comes from what your workspace's connections are set up to do, matched the same way the bus matches a message at delivery:

Part	From
Who publishes a message type	Each producer connection's granted message types. A family (telling.*) or * covers every message type the bus knows in it
Who receives it	Each consumer connection's filter: its message types, its sources and its topic prefix
Sources	A consumer that names a producer connection receives from that connection. One that names system_ids receives from the connections granted them; if it names only some of a publisher's system_ids, the map says which: only from ncs-02
Topic prefix	The topic is each message's own, so the map can't settle it in advance. A consumer with a prefix is listed with it: topics starting som.story.

Only active connections route: a revoked producer connection can't publish, and a revoked consumer connection is unsubscribed. A consumer connection whose filters no producer connection's grants reach is listed under Waiting for a publisher.

What it shows and doesn't

• It shows grants and filters, which every member of the workspace may see.
• It never shows messages, payloads or verdicts. For what happened to a message, see Activity and the story timeline.
• It shows who would receive a message, not what each system does with it: a consumer doesn't report back to the bus.

One message: the Playground

To see where one particular message would go, dry-run it in the Playground. When the gateway accepts it, the Playground lists Would be received by: the consumer connections whose filters match it, including its topic. Nothing is delivered.

Export it as a bus config

Owners and admins can download the house as a bus config from the Routing map: the file your private production bus will be built from (Next), which routes exactly as this map shows. See Going live, and exporting your house.

Change a route

• To change who receives a message type, edit the consumer connection's filters.
• Who may publish it is set by each producer connection's grants, chosen when its app is connected: see Credentials.