Ops Link Server

Introduction

To use full on-premise integrations you must be at an appropriate pricing tier and provide an on-premise Device Server to run the integrations on, known as an "Ops Link Server".

The purpose of the server is to facilitate running on-premise integrations, passing video and alarms to SureView Ops for operators to interact with.

NOTE: if you only require RTSP video rather than full on-premise integrations you can use an Ops Link Mini instead

SureView staff will assist with installing SureView components and integrations onto your server.

Minimum Requirements

The customer supplied Device Server must meet or exceed the following requirements:

• Type: Virtual or Physical (Virtual recommended to allow simple resource increases)
• OS: Windows Server 2016 Standard edition or higher *1
• CPU: 20GHz total *2
• RAM: 16GB total *2
• HDD: 100GB
• Redundant Hardware: all hardware of the physical server (whether the type is Virtual or Physical) must be redundant to ensure fault tolerance, including PSUs, NICs, and HDDs
• Network Access: the following permanent network access is required from the server...
  
  1. To SureView Ops to "wss://cloudlink.sureviewops.com" (HTTPS WebSocket to port 443)
  2. To SureView Downloads at "https://download.sureviewsystems.com" (HTTPS to port 443)
  3. To the On-Premise Systems being integrated with on the local network via the ports used by the particular integration from its support page
• Prerequisite Software: the following third-party prerequisites will automatically be downloaded and installed at install time to ensure the server has everything needed to function properly *3
  
  • .NET 8.0 Desktop Runtime x64
  • .NET Framework v4.7.2 or higher
  • C++ 2015-2022 x86 Runtime
  • C++ 2013 x86 Runtime (optional - required by some manufacturer integration SDKs)
  • Chrome (optional - useful for local testing)
• Server access: it must be possible to provide access (via screen share etc) to the server for SureView support staff to install and maintain integrations on
• Anti-virus exclusions: Any anti-virus software on the server must not interfere with the operation of the SureView components. We recommend adding the SureView Program Files folder to the exclusion list to ensure this.

*1 Linux cannot be used as most manufacturer integration SDKs are Windows-based

*2 These are baseline values to give an idea of what might be required - please contact your account manager to discuss your specific requirements

*3 In advanced situations where the prerequisites cannot be downloaded then an offline install can be performed

Service Running Note

The "SureView CloudLink" service is a critical component and must always be running. As a result...

1. ...the service must never be changed from being set to "Restart on Failure" which is done on installation and means that if the process was ever to fail or be killed then the OS will restart it automatically
2. ...the service must never be stopped, whether by a user or automated/scheduled action (including by incorrectly being controlled by Windows Failover Clustering or any other installed software), meaning it will remain stopped until manually started again. The following Windows log entries can help ascertain when a service was stopped:
   1. In the "System" log, the "Service Control Manager" logs Event ID "7036" when a service is stopped or started. NOTE: When a service is restarted you will see two 7036 entries for the Stop and Start following each other, so if there is a Stop entry that is not shortly followed by a Start entry for the same service name then it has been stopped.
   2. In the "Application" log, the "CloudLink.Client" logs Event ID "18" when it is stopping and Event ID "11" when it is starting. NOTE: When the service is restarted you will see both entries following each other, so if there is a Stop entry that is not shortly followed by a Start entry then it has been stopped.

Service which is correctly running and set to restart on failure: