Atlas Knowledge Base
Dashboard
Managing instances

Managing instances


The Virtual Receiver Instance Dashboard is the one console for every virtual receiver on a machine. It runs as its own service, sbn-virtual-receiver-dashboard, listens on https://127.0.0.1:7080, and stays up while individual receivers are stopped, upgraded or removed. Each virtual receiver instance is opened through it.

[Image: the Instances view with the default instance listed]

Signing in

Sign in with admin. The out-of-the-box password is ibsibs; change it from the Change password button in the header. One sign-in covers the dashboard and every receiver it lists.

The Instances view

Every virtual receiver installed on the machine is a row: name, service (sbn-virtual-receiver-<name>), state, start type, PID, the bind address of the receiver's own console (port 7100 for the first instance, the next free port for each new one), version, and whether it is registered and reachable.

The buttons on each row: Open shows the receiver's console in place; Start, Stop and Restart control its service; Remove (the bin icon) uninstalls it after you type its name to confirm.

[Image: a row with its Start, Stop, Restart and Remove buttons]

Opening a receiver

Click the name or Open. The receiver's console — connections, links, signals, campaigns and log, described on Connections — replaces the list, with a Back to instances button above it.

To keep a receiver in its own browser tab, open https://127.0.0.1:7080/i/<name>/ directly, for example https://127.0.0.1:7080/i/default/. The same sign-in applies.

[Image: a receiver console open inside the dashboard]

Adding and removing receivers

Add instance runs the product's installer for a new named receiver: enter the Instance name, accept the suggested Dashboard bind or set your own, pick the Start mode (Auto or Manual) and click Install. The Operation view follows the installer and the new receiver appears in the list when it finishes. A second receiver is only needed to hold a separate configuration; one receiver already runs any number of connections at once.

Remove runs the uninstaller for that receiver. The dashboard service itself is never removed this way.

[Image: the Add instance form]

Users, API keys and audit

The Users view holds the accounts. An Administrator holds every right on every receiver; any other user holds only the rights granted per receiver — seeing it, starting and stopping it, adding and removing receivers, reading its log, sending signals, changing its settings — and sees only the receivers they have a right on. A user can never grant more than they hold.

The API Keys view creates keys for scripts: a name, an expiry of at most 365 days, grants, and your account password to confirm. The value is shown once with a Copy button; send it as Authorization: Bearer <key>. Keys can be rotated and deleted.

Every call made through the dashboard — user, receiver, action, outcome — streams into the log pane under the Instances list, each line tagged with its receiver's name in that receiver's own colour. The pane carries Find, the Info, Warn and Err level filters, Autoscroll, Clear view and Pause; Find starts empty and Autoscroll starts on, every visit. Which receivers appear is the eye on each row, remembered in this browser, and adding, removing or renaming a receiver turns its eye on.

Each row also carries a Help icon, which opens this page.

[Image: the Users view]

[Image: the dashboard log with two receivers under coloured tags]

The service

The dashboard is installed by the Virtual Receiver installer alongside the first receiver and upgraded with it. Its logs are under dashboard\logs in the installation root. Stopping the dashboard service does not affect a running receiver.



Was this helpful?