Loading ...
Loading ...
Loading ...
l
nssm install NGINX “C:\nginx\nginx.exe”
l
nssm set NGINX AppDirectory C:\nginx
l
nssm set NGINX DisplayName “NGINX Web Server”
l
nssm set NGINX Description “NGINX Web Server”
l
nssm set NGINX Start SERVICE_AUTO_START
In the examples below, replace the string www.example.com with the address of the
load balancer.
For example: Load balancer = LB01.briefcam.com.
12. On any host that is running the application (browser), make sure the domains (or host name) can be
resolved by the DNS. If no DNS is available, you can edit the hosts file and add the IP address of the
load balancer using the following syntax:
• 10.x.x.x www.example.com
For example: 10.0.0.143 www.example.com
13. Restart the load balancer computer, open services.msc and try to start the newly created NGINX Web
Server service.
l
If the service does not start, there may be an issue with its path. To try and solve this issue, run
NSSM install on the same folder as described under step 8 and define the service via the NSSM
GUI (making sure to specify the parameters properly).
14. Edit both web config .js files on the BriefCam server (located at C:\Program
Files\BriefCam\WebServices\ProWebClient\webConfig.js and C:\Program
Files\BriefCam\WebServices\ProWebAdminClient\web.config.js) using the syntax below. This syntax
refers to the load balancer address. The endpoints in both files must point to the load balancer.
• //www.example.com/ProWebApi/
• //www.example.com/AdminApi/
15. In the BriefCam Administrator Console, set the environment settings with the following values:
• DB.LocalStorageAddress : “//www.example.com/ProWebApiStorage"
• BaseVideoUrl: “https://www.example.com/vsg”
• ClientNotificationEndPoint: “//www.example.com/signalr" (without port 7080)
VideoProcessingGatewayUrl in https is not supported.
Installation and deployment guide | XProtect® Rapid REVIEW
41 | Installation and deployment steps
Loading ...
Loading ...
Loading ...