Atlas Knowledge Base
Dashboard
From Service Manager to the Dashboard

From Service Manager to the Dashboard


Through SBN v95, the SBN Services running on a server were managed with SBN Service Manager — a Windows desktop program installed on the server itself, used to install the services, start and stop them, and read their logs. From v96 onward, when SBN Services moved to semantic versions (1.x), that program was replaced by the SBN Services Dashboard: a browser-based dashboard that ships and installs in the same package as the services it manages.

What replaced what

Taskv95 and earlierCurrent line (1.x)
Install the servicesRun SBN Service Manager on the server and install each service from itRun the packaged installer once — it sets up the services and the Dashboard together
Start / stop a serviceService Manager window on the server desktopDashboard, from any browser that can reach the server
View logsLog pane in Service ManagerDashboard log viewer, with live tailing and history per service
Change settingsEdit the service's configuration through Service ManagerPer-service settings editor in the Dashboard
Remote accessRemote desktop into the serverBrowse to the Dashboard over HTTPS and sign in
AutomationNoneAPI keys, issued and scoped from the Dashboard
Operating systemWindows onlyWindows and Linux

What this means when upgrading

SBN Service Manager is not included in the current packages, and there is nothing to install separately in its place. The installer registers the Dashboard as its own service on the box, which starts automatically with the server and stays running whether or not anyone is signed in.

Management moves to a browser. On the server itself, browse to https://localhost:9096; from another machine on the network, use the server's name in place of localhost, for example https://sbn-server:9096. The port is chosen at install time and defaults to 9096. Sign in as admin with the password set during installation, then change that password from the Account page.

Each server runs its own Dashboard and manages only that server's services. On a site with several SBN servers, each one has its own address and its own sign-in.

The Dashboard is served over HTTPS. The installer generates a certificate if none is supplied; browsers show a warning for it the first time, which you can continue past. Supply your own certificate at install time if you want browsers to trust the Dashboard without the warning.



Was this helpful?