Step 7 · Go live

Next The shared bus is a sandbox: synthetic content, no production

service levels. When your house works, the next question is how SOM runs in your newsroom for real. When you go live, RND runs a private bus for your newsroom, built from the house you tested. It is yours alone: no other publisher's traffic, connections or data are on it. It is next in line, not available yet: ask RND when your house is ready.

What carries over

Everything you built in steps 1 to 6 is planned to carry over to production:

• your newsroom map, story ownership and naming;
• every product's SOM integration: SOM messages are the same on any bus;
• your house's routes: who publishes each message type, and whose filters receive it;
• your scenarios, run sheets and scorecards, as regression tests for upgrades.

What is expected to change is configuration: credentials, endpoints and, where they differ, system_ids. Make sure every product takes these from configuration, not code.

Export your house Available now

Owners and admins download the house as a bus config from the Routing map: the file your private bus will be built from, so you can read exactly what would go live. It holds your connections, their grants and filters, your story ownership setting and your house skills; never secrets, messages or verdicts; and it lists at the top anything it can't express yet. See Going live, and exporting your house.

Settle with RND

Ask RND when your house is ready. None of these is settled yet: each is to be agreed with RND before production.

Topic	Question
Identity	Your own identity provider for your apps, or credentials the bus issues?
Credentials	How every connection, yours and your vendors', gets production credentials
Receiving	Which systems read over the HTTPS pull API, and which read a queue directly
Service levels	Availability, support hours, how incidents are handled
Data	How long the replay archive keeps messages; logs never hold payloads
Change	How SOM 1.x upgrades are rolled out, and re-tested with your scenarios

Keep the sandbox

Keep your house after you go live:

• to bring a new vendor in and evaluate it before it touches production;
• to re-test a new product release or a new SOM version with your scenarios;
• to reproduce a production problem with synthetic content.

Back to the publisher track.