SMServer
SMServer (System Management Server) is the Main server service. It is used to designate a server in the system as the Main server, which serves as the focal point for communication with client applications and other servers in the system. A VMS must have a server assigned as a Main server with SMServer on it connected to the system network.
SMServer listens on TCP port 5008 for the client applications. SMServer uses TCP port 5009 to connect to the system network’s other servers for time synchronization, settings changes, receiving event information, etc.
The service maintains the system state and system data, e.g. server information, system clock, users and device profiles.
SMServer maintains connections to all the watchdog services in the system and receives and logs monitoring events.
Upgrading the system servers and clients is done through SMServer.
Alarm events and the audit trail are recorded in the server database. In larger environments, a SQL Server database can be used to store alarm and audit trail databases.
Audit trails record user activities in the system.
A Main server with SMServer can support up to 150 recording VMS servers that are referred to as subservers. A subserver can be any server device with the DVRServer service installed and enabled.
The service must be installed on a computer or server with a supported OS (see more information here: Supported OS). The device can also be a virtual device running in Hyper-V and VMware virtual machine platforms.
DVRServer
DVRServer is the service installed on servers set up as recording devices in the VMS network.
This sets them up to store video data sent by the cameras.
They receive footage and save it on their hard drives with metadata saved on the common database.
The servers also perform VCA, motion detection and send out alarms, should pre-defined criteria for such be fulfilled.
Servers with DVRServer require two NICs on their hardware: one to communicate with IP camera networks, the other for server-server/server-client communication. Devices meant to capture footage from analogue cameras need to connect to IP encoders with the analogue cameras connected to.
It is advisable to keep IP cameras on a separate network from the recording servers.
DVRServer listens on TCP port 5009. Video, audio and data streams require TCP port 5011 to be open.
DVRServer never contacts the applications (Spotter for Windows and System Manager) or SMServer.
However, if IP cameras are installed in the system, servers contact the IP cameras using TCP or UDP, depending on the camera model and the camera configuration.
The service must be installed on a computer or server with a supported OS. The device can also be a virtual device running in Hyper-V and VMware virtual machine platforms.
WDServer
WDServer is the Watchdog server service that functions as the system monitor. It monitors local DVRServer and SMServer services and is responsible for seeing that both services are running and operating normally.
During normal monitoring, it will save events to a local event buffer (max. 1000 individual events).
These events can be used to trigger digital outputs in DVRServer. WDServer can also be configured to send emails.
Even if neither is configured, WDServer will always log the events in a log .txt file, with C:\Users\[Window user]\AppData\Roaming\DVMS\DVR Application\Logs folder being the default.
In severe situations such as a system malfunction or hard drive failure, Watchdog can do several preset tasks, e.g. restart the affected computer or send e-mail messages containing information about the malfunction.
If the system's Main server is down, the error situations will be notified once the SMServer service is up again.
Error situations will not cause the watchdog to initiate a reboot loop.
Any reboots by WDServer will be followed by changing the faulty component to an error-tolerant state (e.g., disabling a faulty channel).
Rebooting will never be done more than once per 6-hour cycle.
If other faults or errors normally resulting in a reboot occur, these will be logged but not acted upon.
WDServer is automatically installed with SMServer and DVRServer.
WDServer takes care of the connections and operational reliability of the VMS system through TCP port 5010.
The Watchdog records other system service up/down events if they’re installed on the same device as the Watchdog. If these services go down, the application restarts them.
The service must be installed on a computer or server with a supported OS. The device can also be a virtual device running in Hyper-V and VMware virtual machine platforms.
Gateway
The optional Gateway service must be installed on a computer or server with a supported OS. The device can also be a virtual device running in Hyper-V and VMware virtual machine platforms.
The computer must have HTTP software installed. Mirasys VMS software is not required on the server.
The Gateway service contacts the Main server through TCP port 5008.
Gateway allows 3rd party to integrate with the VMS using the Gateway API that is hosted on TCP port 9000. The TCP port can be changed by editing the ServiceLauncher.exe.config configuration file in the service’s installation folder (default C:\Program Files\DVMS\Gateway).
Storage Locker
The Storage Locker service is installed with the SMServer and accessed by the Spotter application from the Spotter Storage Locker plugin for accessing storage locker content. Storage Locker can be used to search, edit, or delete a stored item, open a selected picture, video clip, or camera audit report PDF file for viewing, or save a file of a similar type to the disk. Files stored in the Storage Locker can be saved by Spotter, Media Exporter, and Export service. Metadata for the saved data is stored in the Storage Locker service database. The actual data files are stored on a local or network disk. This service communicates only over HTTP.
Incident Reporting
The Incident Reporting service is installed with the SMServer and accessed by the Spotter application from the Incident Reporting Spotter plugin for accessing and storing incident report data in the incident report database. This service communicates only over HTTP.
Export service
The Export service is installed with the SMServer and used by Spotter Web to create video exports. Export tasks are received and individually processed by the Export service. When the export is ready, the exported data is sent to the Storage Locker service, where the data is stored. The Export service has an HTTP API to create, get, and delete export tasks. Export service doesn't keep any exported material; it only contains information about export tasks that are added, currently running, or already completed but were not deleted.