SiteManager manual
SiteManager 26.10 manages MultiTaction MT557D and MT556 displays from one computer on the same network as the displays, the touch network. You can set up displays, watch their health, update firmware and write the Cornerstone configuration files for a video wall without visiting each display.
It works with MT557D displays on firmware 2.0.6 and with MT556 displays. Features that need newer display firmware (operator PIN, menu orientation and hold time, SSH keys, the display's update server and encrypted access) are hidden or skipped on those displays. See Capabilities.
How SiteManager works
SiteManager has two programs:
sitemanagerdis the service. It runs all the time on the computer that sits on the touch network, usually the wall's application computer. It finds and watches the displays, runs jobs such as firmware updates, and serves the web interface.sitemanageris the command line. When it finds the service it talks to the service, so everything you do is logged and protected exactly like a change made in the web interface. Otherwise it talks straight to the displays, which is handy for a quick check from a laptop.
Local mode and network mode
SiteManager runs in one of two modes. The address it listens on decides which.
- Local mode is the default. The service listens on this computer only, at
http://127.0.0.1:8790/. There is no setup token, no login and no certificate warning. Everyone who can use this computer is the administrator, and every change is recorded in the audit log as/local. - Network mode is optional. The service listens for other computers too and serves HTTPS. It adds the first-run setup token, logins, the roles admin and viewer, and API tokens.
Start in local mode. Open SiteManager to the network only when people on other computers need it. See Opening SiteManager to the network.
The service keeps what it knows in a state directory: the list of displays and walls, users, history, alert settings and the certificate. See Files, folders and logs.
SiteManager works with the display software you already have. It does not change display firmware unless you start a firmware update, and it never restarts Canvus or Showcase.
Words used in this manual
Display : One MT557D or MT556 display. SiteManager identifies a display by its serial number, not its IP address, so a display that gets a new address from DHCP is still the same display.
Site : Everything one SiteManager service manages.
Wall : A named group of displays, usually a video wall. A wall can have a layout (columns, rows, where each display sits), and a profile.
Profile : A named set of display settings that displays should have. SiteManager can apply a profile and warn you when a display no longer matches it.
Job : A long operation that runs in the service, such as a reboot, a calibration or a firmware update. A job keeps running when you close the browser.
Selection : The displays a command acts on: some displays by serial number, a whole wall, or all displays.
Start here
New to SiteManager? Follow this path. Each step is a how-to page with a screenshot at every step.
- Install SiteManager on the computer that drives the wall, then open it: First start.
- Learn how SiteManager is laid out: A tour of SiteManager.
- Learn the difference between a wall and a room, and which files SiteManager writes: Walls, rooms and the Cornerstone files.
- Set up your installation: Set up a wall, Set up a projector room, or, if the wall already runs, Bring in an existing wall.
- Look after it: Day-to-day care and Update display firmware. Then protect it: Secure your displays, Manage SSH keys and Set where displays look for firmware.
- When something goes wrong: Logs and diagnostics, Troubleshooting and the FAQ.
Tips and tricks collects shortcuts that save time once you know your way around.
In this manual
Install and start
- Installing SiteManager: what to install on which computer.
- Windows, Linux and macOS: step-by-step installation and removal.
- First start: open the web interface on this computer, and open SiteManager to the network if you want to.
- Ports and firewall: what must be reachable.
Using SiteManager (how-to)
- A tour of SiteManager: what every page is for, and the order of work on your first day.
- Walls, rooms and the Cornerstone files: the ideas behind walls, rooms, windows and extra outputs.
- Set up a wall and Set up a projector room: step by step.
- Bring in an existing wall: from SiteManager 2.x or an existing
screen.xml. - Day-to-day care: watching the site, alerts, profiles, drift, settings and jobs.
- Update display firmware: the catalogue, signatures and rollouts.
- Secure your displays, Manage SSH keys and Set where displays look for firmware: access keys, SSH keys and the update server of a display.
- Logs and diagnostics: the service log, the support bundle and the audit log.
- Tips and tricks and the FAQ.
Use the web interface
- The web interface: the menu and finding your way around.
- Displays: find displays, read their status, change settings, run actions and jobs.
- Walls and Cornerstone files: lay out a wall and write
screen.xml,config.txtandmt-canvus.ini. - Profiles and drift: keep displays in line with a standard set of settings.
- Firmware: the firmware catalogue, the local cache and staged rollouts.
- Display security: access keys, the states a display can be in, SSH keys and the update server.
- Monitoring and history: how displays are watched, status history and the idle-wall check.
- Alerts: rules and delivery channels.
- Diagnostics and capabilities: the support bundle and what a display's firmware advertises.
- Users, roles and security: the audit log, and in network mode accounts, API tokens and the certificate.
Use the command line and the API
- The command line: service mode and direct mode, logging in to a network service, JSON output and exit codes.
- Command reference: every command and flag.
- Moving from SiteManager 2.x: what changed, and which old commands still work.
- The JSON API: for scripts and integrations.
Reference
- sitemanagerd reference: service options, files and logs.
- Troubleshooting: common problems and the messages that go with them.
Start with Installing SiteManager if you have not installed it yet.