Skip to content

Installing SiteManager

Install SiteManager on a computer that is connected to the touch network the displays are on, and that stays on. On a video wall this is usually the wall's application computer. The service runs there all the time.

By default SiteManager works on this computer only: you open its web interface in a browser on the same computer, at http://127.0.0.1:8790/, and nothing needs to be set up. If you want to use it from other computers too, you can open it to the network (see Opening SiteManager to the network). You do not need to install anything on the computers you browse from.

Before you secure displays: upgrade every SiteManager

Securing a display locks out older SiteManager versions, SiteManager 2.x and other tools until it is released. Upgrade every SiteManager on a site before securing displays. See Secure your displays.

Choose your platform

Platform What you download How it runs
Windows A setup program (.exe) for 64-bit Windows 10 or later Installs the SiteManager Windows service, which starts with the computer
Linux A Debian package (.deb) for Ubuntu 24.04 on 64-bit Intel or AMD processors Installs the sitemanagerd systemd service, which starts with the computer
macOS A .tar.gz archive for Apple silicon or Intel No installer and no service. You run sitemanagerd yourself. Meant for the command line and for use on a laptop

Download the file from the Downloads page. File names start with sitemanager-.

Windows and Linux are the platforms for a permanent installation. The macOS archive is for working from a laptop, for example to run the command line against a service somewhere else.

What the installation contains

Every platform installs the same two programs:

  • sitemanagerd, the service with the web interface;
  • sitemanager, the command line.

The Windows and Linux installers also start the service for you and keep it running. They enable it to start with the computer. Both start it in local mode, which listens on this computer only.

The Cornerstone user

SiteManager can write the Cornerstone files of a video wall: screen.xml, config.txt and mt-canvus.ini. These files belong to the operating-system user that runs Canvus or Showcase on the wall computer, the Cornerstone user.

  • The Windows installer asks you for this user.
  • On Linux the package sets it to multi, the user of the MT Wall Image. You can change it in /etc/default/sitemanager.
  • On macOS the files of the user who runs sitemanagerd are used, unless you name another user.

If the user does not exist, SiteManager still starts. It shows displays, runs jobs, and generates the files for download. Writing the files to the computer is switched off, and the page says why.

Where things are

Windows Linux macOS
Programs C:\Program Files\MultiTaction\SiteManager /usr/bin/sitemanagerd and /usr/bin/sitemanager The folder you unpacked the archive into
State directory C:\ProgramData\MultiTaction\SiteManager /var/lib/sitemanager --state-dir, by default sitemanager-state in the folder you start the service from
Service options Stored with the service. Setup asks whether other computers may connect. /etc/default/sitemanager Command-line options
Service log sitemanagerd.log in the state directory, and the Windows Application event log for start-up failures sitemanagerd.log in the state directory, and the journal (journalctl -u sitemanagerd) sitemanagerd.log in the state directory, and the terminal
Command-line login (cli.json), network mode only %AppData%\sitemanager ~/.config/sitemanager ~/Library/Application Support/sitemanager

The state directory holds the list of displays and walls, history and alert settings, in network mode the users and the certificate, and, for displays you have secured, display-access.json with their access keys. Include the whole directory in your backups: the keys are kept nowhere else and are never exported. See Files, folders and logs and Back up the state directory.

Updating

Install the newer version over the old one. The site, users, history and certificate stay as they are.

Upgrade every SiteManager on a site first

Securing a display locks out older SiteManager versions, SiteManager 2.x and other tools until it is released. Upgrade every SiteManager on a site before securing displays. Nothing is secured by the upgrade itself. A display is secured only when you choose Secure (see Secure your displays), or if you turn on Secure new displays when they are added on the Security page, which is off by default.

  • On Windows the installer stops the service, replaces the files and starts the service again with the options it had. A service you disabled stays disabled. The installer keeps the mode the installed service has: an installation that was open to the network stays open, and a local one stays local.
  • On Linux apt install of the newer package restarts the service if it was running or enabled. A service you disabled stays disabled. The package keeps /etc/default/sitemanager, so the mode stays as it was. See Updating.
  • On macOS, stop sitemanagerd, unpack the new archive and start it again with the same --state-dir.

Uninstalling

Each platform page has an Uninstalling section. None of them deletes your site data unless you ask for it, so a later reinstall finds everything as you left it.

Next step

Start SiteManager for the first time. If you will open it to the network, also check Ports and firewall.