VAU
VAU (VMS Application Updater) is a service application that is used with System Manager, System Monitor, Spotter, and Spotter Viewer applications. VAU is used to automatically update the applications to the latest versions from the Main server system service (SMServer). VAU is installed during the application installation, and it is started first when the System Manager, System Monitor, Spotter, or Spotter Viewer is run.
VAU uses the Main server IP Address or hostname to contact the Main server system service (SMServer) using TCP port 5008. After VAU has established a connection to the Main server, it downloads the latest application version information. If the version information differs from the information detected during the previous application start-up, VAU downloads all needed update files. If the downloaded version information matches the local version information, only the configuration files will be downloaded. The configuration information includes, but is not limited to, the Main server address, which the application will contact at start-up.
After updating the version or downloading the configuration files, System Manager, System Monitor, Spotter, or Spotter Viewer will be started, and VAU will close.
System Manager
When the System Manager application is started, and the user is successfully logged in, the system data is retrieved from the Main server (TCP port 5008). The applications access the servers through TCP port 5009. Video, audio, and data streams requested through the applications use TCP port 5011.
The System Manager is the primary system management and configuration application. It contacts the Main server and accesses information pertaining to the VMS system. The application allows an administrator user to manage users and user groups, manage device profiles, add, modify, and remove servers, cameras, and other devices to the service, manage alarm conditions and actions, etc. Read more about System Manager from the Mirasys VMS Admin Guide.
Spotter For Windows
Spotter for Windows is the primary desktop monitoring application. Once the user has successfully logged in, their device profile data is downloaded from the Main server. The device profile data includes all information regarding the servers connected to the system and available for the user.
A Spotter client contacts the servers and accesses the devices connected to the servers. Through this, it accesses live and recorded surveillance data. Spotter can be used as a specialized video wall application, as well. Currently, only one instance of the SMServer service at a time can be accessed by the Spotter for Windows application. You can find more information about Spotter in the Spotter User Guide.
Spotter Web
Spotter Web is an HTML5-based client application that provides a subset of Spotter Desktop features for desktop and mobile browsers. The application can be used to view real-time streams, playback stored videos, export videos, receive alarm notifications, and view alarm trigger and action camera streams. The Spotter Web backend runs on IIS, communicating with the VMS system recorders and the System Management servers. The Spotter Web Guide provides more information on Spotter Web.
Spotter Viewer
Spotter Viewer is a client application for viewing the Spotter operator view. An operator can share their view from Spotter to a viewing station, so workers without surveillance rights or device access can view it in Spotter Viewer. More information about Spotter Viewer can be found in the Spotter Viewer documentation.
Spotter Player
Spotter Player is a single executable file and can be run without installing any other components on a Windows machine. Spotter Player can be used to open and playback archives, SEF, and ASF clips. Spotter Player is installed with Spotter and can be copied with exported clips.
System Monitor
System Monitor is a desktop application for system administrators to monitor the state of the VMS system. System Monitor has a configuration window (for username and password), a status window (system status, detailed information about issues, etc.), and a system log export (save as dialog, creates one zip file). System Monitor can be installed either on the main server or the recording servers.