BriefCam v5.4 Installation Guide

TRANSFORMING VIDEO SURVEILLANCE
INTO ACTIONABLE INTELLIGENCE
BriefCam® ® v5.4
BriefCam v5.4
Installation Guide
Installation Guide
April 2019
Contents
Introduction ...................................................................................................................................... 4
Prerequisites ..................................................................................................................................... 4
Site and Network Topology................................................................................................... 4
Installed Software ................................................................................................................. 4
Firewall Consideration and Local Ports Availability ............................................................. 5
Order of Installation ......................................................................................................................... 5
All-in-One or Distributed Deployment ............................................................................................ 6
Upgrade to 5.4 Instructions ............................................................................................................ 6
Oracle XE Installation..................................................................................................................... 10
Installing the Database for Network Storage .................................................................... 17
Setting Up the Data Drive on a Shared Network Drive .................................................... 17
Oracle SE Installation..................................................................................................................... 18
BriefCam Server Installation ......................................................................................................... 18
Required BriefCam Server Components ....................................................................................... 21
Using Specific IP for Rendering Service............................................................................. 27
BriefCam GPU Configuration Tool ................................................................................................. 28
BriefCam ODBC Plugin Installation (Optional) ............................................................................. 30
BriefCam Research Installation ..................................................................................................... 32
Creating a Virtual Proxy ...................................................................................................... 38
BriefCam Web Services Installation .............................................................................................. 39
K-Lite Installation ........................................................................................................................... 43
BriefCam VMS Integration Plugin Installation (for BriefCam Protect/Insights/Rapid Review). 49
Avigilon Integration ............................................................................................................. 50
Bosch Integration ................................................................................................................ 51
CASD Integration................................................................................................................. 52
Digifort Integration .............................................................................................................. 54
Exacq Integration ................................................................................................................ 55
Page 2 of 101 © BriefCam | 4/19/19

FLIR (Formerly DVTEL) Integration ................................................................................... 56

Genetec Integration ............................................................................................................ 58
GeoVision Integration ......................................................................................................... 67
Geutebruck Integration ....................................................................................................... 68
HikVision Integration ........................................................................................................... 69
IndigoVision Integration ..................................................................................................... 70
Milestone Integration .......................................................................................................... 72
OnSSI/SeeTec Integration .................................................................................................. 82
Qognify (Formerly Nice) Integration .................................................................................. 83
Salient Integration .............................................................................................................. 84
Teleste Integration .............................................................................................................. 86
Verint Integration ................................................................................................................ 87
Supported VMS Matrix ................................................................................................................... 89
Infodraw Integration Installation .................................................................................................. 91
Timespace X300 Integration Installation ..................................................................................... 92
How to Change Default Ports Configuration ................................................................................. 93
License Activation ........................................................................................................................... 94
Running BriefCam in Virtual Environments ................................................................................ 100

Introduction
This guide provides detailed information about installing BriefCam products including prerequisites, the
order of installation, and instructions about VMS-specific BriefCam integration plugins. These plugins
enable the BriefCam Server to connect to one or more VMS environments.
Prerequisites
Site and Network Topology
Make sure an adequate site survey was performed and the following requirements are met:
Servers Refer to BriefCam’s Hardware Deployment Sizing document and
ensure the recommended hardware is installed per the required
processing capacity
Drivers For the server with the GPU, make sure to download the latest
version of the Nvidia driver.
Network connectivity Ensure a minimum of 1 Gbps is available from the VMS to BriefCam’s
between BriefCam and the Processing Servers
VMS
Network connectivity Ensure a minimum of 1 Gbps is available between BriefCam’s
between BriefCam Processing Servers and Video Synopsis Server
components
Installed Software
The following software components must be installed prior to the BriefCam product installation:
o Windows 10 Pro or Windows Server 2016

o Windows updates – Make sure that every server has the latest Windows updates
installed.
o Google Chrome or Firefox

Firewall Consideration and Local Ports Availability

The following firewall ports should open automatically during the BriefCam installation:
Component Port #
VS Server 1112
Web Services 80
DB (Oracle) 1521
Research (BI) Ports:

Component Port #
HTTP 8090, 4248
HTTPS 4244, 443
API ports 4242, 4243
Additional ports* 4432, 4103, 4747, 4899, 4900, 4949
*The additional ports are used by the Research module and should be available on the Research machine.
Please note that HTTP and HTTPS ports need to be reachable from the user’s machines to the servers.
Note: Some ports can be changed if not allowed on the customer’s network. For detailed instructions, see
the How to Change Default Ports Configuration section.
Order of Installation
It is important to install the components in the following order, as there are dependencies
between the different components.
Oracle Database
BriefCam Server
o Configure the GPU via the BriefCam GPU Configuration Tool (optional)
BriefCam VMS integration plugins (with Protect/Insights/Rapid Review products)
ODBC Plugin (only needs to be installed if the BriefCam Research component will be installed
on a dedicated, stand-alone machine)
BriefCam Research module
o Create Virtual Proxy (optional)
BriefCam Web Services
K-Lite Mega Codec Pack – This item can be installed any time during the installation process.

Changing the server name after installing the BriefCam software will require additional
changes. If you need to change the server name, contact BriefCam Support.
All-in-One or Distributed Deployment

All BriefCam components can be installed on one machine or the components can be distributed across
several machines.
In general, to ensure a fast, real-time user experience with high capacity loads, use dedicated
machines for the following components: Rendering, Research, Database, Storage and Processing Servers.
For example, if your deployment is Research-focused, install the Research component on a separate
machine.
Upgrade to 5.4 Instructions

o Upgrading from V5.2 or V5.2.1 is not backwards compatible with the previous version.
All existing processed video data will be erased upon upgrading, so your videos will
need to be reprocessed. However, the following data will remain available: users,
groups, reports and bookmarks, permissions, and activated cameras.
o Starting with V5.2.1 UP1, upgrading is backwards compatible with the previous
version.
Moving from V4.3 to V5.x: Due to the architecture changes made in V5.x, when moving
from V4.3 to V5.x you need to uninstall V4.3 and install V5.x. All existing processed video
data will be deleted, and your videos will need to be reprocessed.
To upgrade to V5.4, follow the instructions below:

Make a note of the installed version. You will need to know this at a later stage.
It’s recommended to back up the existing Oracle database. You can do this by double-clicking
the exportDB.bat file located at: C:\Program Files\BriefCam\Scripts\. The backup will
be saved to C:\BriefCam\ServerData\Backups\.
It’s recommended to back up the existing Qlik database and Qlik shared folder. You can do
this by double-clicking the BI_Backup.bat file located at: C:\Program
Files\QLIK\Sense\bc\BackupScripts\. The backup will be saved to C:\BriefCam\.

Stop BriefCam services via the BriefCam Admin desktop application (see image below) and
close all BriefCam applications.
If upgrading Research is required, check which port is used for Qlik. If it’s not the default port
443, you will have to carry out additional steps before reinstalling the Research component
(see step 12).
Uninstall BriefCam and all of its components via add/remove programs in the Windows
control panel. (You can uninstall the components in any order.) Note that uninstalling and re-
installing the Oracle database and the Qlik database is not required. However, you will need to
reinstall the Research module (see step 11).
When upgrading, make sure to use the same user that was used when the system was
installed.
Install the BriefCam Server 5.4 (do not yet install additional BriefCam components).
When upgrading from V5.3 to V5.4, reconfigure the network path.
o This is necessary because in V5.3.0, the network path was configured from a JSON file.
In V5.4, the network is configured in the DB settings in the Web admin.
Find the Upgrade scripts folder located in the BriefCam Server folder. Its default location is:
C:\Program Files\BriefCam\BriefCam Server\DB\Upgrade.
Run the upgrade scripts by double-clicking the relevant bat file according the table below.
From Version Build Number Run Scripts
5.2 5_2_0_to_5_2_1.bat
5_2_1_to_5_2_1UP1.bat
5_2_1UP1_to_5_2_1UP2.bat
5_2_1UP2_to_5_3_0.bat
5_3_0_to_5_3_1.bat
5_3_1_to_5_4_0.bat
5.2.1 5.2.1.17109 1. 5_2_1_to_5_2_1UP1.bat
2. 5_2_1UP1_to_5_2_1UP2.bat
3. 5_2_1UP2_to_5_3_0.bat
4. 5_3_0_to_5_3_1.bat
5. 5_3_1_to_5_4_0.bat
5.2.1 UP1 5.2.1.17275 1. 5_2_1UP1_to_5_2_1UP2.bat
2. 5_2_1UP2_to_5_3_0.bat
3. 5_3_0_to_5_3_1.bat
4. 5_3_1_to_5_4_0.bat

From Version Build Number Run Scripts

5.2.1 UP2 5.2.1.17363 5_2_1UP2_to_5_3_0.bat
5_3_0_to_5_3_1.bat
5.2.1 UP3 5.2.1.17421
5_3_1_to_5_4_0.bat
5.3.0 5.3.0.17664 5_3_0_to_5_3_1.bat
5.3.0 UP1 5.3.0.17698 5_3_1_to_5_4_0.bat
5.3.0 UP2 5.3.0.17714
5.3.1 5_3_1_to_5_4_0.bat
If upgrading Research is required and the default port 443 was not used for Qlik, carry out the
following steps:
Make sure that port 443 is not being used by other apps.
Move Qlik back to port 443 via QMC.
Install the remaining 5.4 relevant components: Research, Web Services and then Plugins,
according to the installation instructions.
Note: When upgrading the Research component, you cannot change the user. You must use the same
user that you used in the original installation.
Once the installation is complete, launch the BriefCam Admin desktop application and start the
BriefCam services.
Restart the IIS services on the machine where the BriefCam Web Services are installed. (This
will activate the v5.4 license.) To restart the Default Web Site service via Windows IIS,
enter the Internet Information Services (IIS) Manager, search for the Default Web
Site service, then click Restart in the menu on the right.
If the Qlik default port was not 443 in the previous version of the Research installation, move
Qlik back to a custom HTTPS port.

If upgrading the Research module from v5.2 or v5.2.1:

Change the class filter (Dog, Cat, Bird and Horse to appear as Animals), you should
manually run the Qlik update QVD app. From v5.2.1 UP1, this step is not required.
Enter Qlik QMC by opening a browser and entering the following URL:
https://Research_Host_Name/QMC (for example, https://bc-poc/QMC)
Select the Apps menu.
Select the ResearchUpdateHistory app, click More actions, and then Reload
now.
To check that the update has run successfully, select the Tasks menu and verify
that the status of the task named Manually triggered reload of
ResearchUpdateHistory is Success.
The changes will take effect in the next Qlik run.

Oracle XE Installation
To run the Oracle XE Installation wizard, double-click BriefCamOracleXE_<Version
number>.exe. The installation checks for prerequisites. If anything is missing, you will be
prompted to install the missing prerequisites. Click Install.
Click Next.
Select the drive where you want to install Oracle XE.

Enter and confirm the Oracle SYSTEM password. The default SYSTEM password is
Qwerty123.
Click Next.
Select the data drive on which you want to install Oracle.

If you want to use a shared network drive or dedicated storage machine, select any local drive
on the data drive field, complete the Oracle XE installation and then refer to the How to Set
Up the Data Drive on a Shared Network Drive section.
Click Next.
In the next screen, by default, BriefCam will populate the BriefCam User field with BCUser.
Select whether to use an existing account or create a new account.

For an existing account, enter the password; for a new account, create and confirm the
password.
Use a password that is compliant with your password policy.

It is important that you remember the password since you will be prompted to use this password in the
following BriefCam component installations.
A password may fail for a variety of reasons:
o The password does not meet the password policy of the operating system and/or
organization.
o Domain accounts cannot be created by this dialog. Contact the relevant IT person if a
new domain account is needed.
o If the user is disabled, locked, or otherwise limited.
Click Next.
Click Install.

Once the Oracle installer is displayed, click Next.
To proceed with the installation, read and accept License Agreement terms.
Click Next to continue.
If the Oracle installation window is hidden behind the BriefCam installation window
during the database installation (it looks like the installation is stuck), drag the Oracle
window and click OK.
If the Oracle XE installation gets stuck, open the Task Manager and end the Setup
Launcher (32 bit) task.

For a default path installation, do not edit the destination folder and click Next.
You will now be prompted to enter a password as shown in the image below. It is important
that you remember this password as this password will be used for the databse accounts.

Click Install.

Your Oracle XE installation is now complete. Click Finish.

Installing the Database for Network Storage

For network storage, the best practice is to:
1. Install the database to a local device.
2. Verify that the local installation of the database was successful.
3. Move the folder to the network-attached storage (NAS) using BriefCam’s Move Storage utility,
which will automatically update the configuration.
Setting Up the Data Drive on a Shared Network Drive

If you want to install the data drive on a shared network folder, follow the instructions below:
Permissions configuration:
o Right click the shared folder you would like to use and click Properties.
o On the Sharing tab click Share.
o Add the user group IIS_IUSRS (case sensitive) from the dropdown menu.
o If the IIS_IUSRS does not appear in the dropdown menu, select Find people.
o Search for IIS_IUSRS (case sensitive) using the Check Names button.

o Click OK.
o Change the IIS_IUSRS user group’s permission level to Read/Write.
o Click Share.
To run the database scripts:
Edit the CreateSchema.bat file located on the default server installation directory
in the following path: C:\Program Files\BriefCam\BriefCam
Server\DB\Setup.
Change the DATA_DRIVE to the shared folder host. For example: set
DATA_DRIVE=\\10.0.0.1\Shared\
Run the database configuration script by double-clicking the ConfigureDB.bat
located on the default Server installation directory in the following path:
C:\Program Files\BriefCam\BriefCam Server\DB\Setup.
Run the create schema script by double-clicking the CreateSchema.bat (the file
that was modified in the previous steps).
Run the setConnectionsLimit.bat file that is located on the Server installation
directory in the following path: C:\Program Files\BriefCam\BriefCam
Server\DB\Setup.
Oracle SE Installation
The deployment size determines which Oracle edition needs to be installed, XE or SE. The recommended
edition is specified in the purchase order.
BriefCam Server Installation
Remember that before installing the BriefCam server, the Oracle XE needs to be installed.
To run the BriefCam Server Installation wizard, double-click

BriefCamServer_64bit_<Version number>.exe.
The installation checks for prerequisites. If anything is missing, you will be prompted to install
the missing prerequisites.

Click Install.
Click Next.
Accept the terms of the license agreement and click Next.

Select the modules that you want to install (by checking the necessary components in the
table below) and click Next.

Required BriefCam Server Components

Server All-in-One Distributed
Description
Component Configuration Configuration
Administration Manages, configures and monitors the Should be installed on


Utility BriefCam system. the VSServer machine
Responsible for access control and video

retrieval from the VMS. This component
Should be installed on
Server installs the VSServer, which is responsible 
the VSServer machine
for scheduling and watch dog of the real-
time channels.
Responsible for video decoding, object

extraction and classification. Consists of When installed on
Processing single or multiple GPU cards. Multiple dedicated machine,
*
Server (PS) Processing Servers can be deployed per the Activation Tool
site depending on the required scale of should also be
video processing. installed
Should be installed
BriefCam products should be activated and and run on every
registered prior to first use. Use the machine that includes
Activation Tool supplied BriefCam License Activation  BriefCam components
application and the provided product key to (Server, Processing
activate the software. Server, Alert
Processing Server)
Video
VMS integration testing tool (connection
Integration  Should be installed on
and fetching tester).
Tester the VSServer machine
Responsible for video rendering, can be

installed on dedicated machine to allow
scalability, where multiple users are
expected to consume video synopses Should be enabled on
Rendering
concurrently.  the Rendering
Service
machine
In general, concurrent users or more,
deploy the Rendering service on a separate
machine.


Description
The Rendering service can be installed on

as many host machines as needed with no
need for additional configuration.
See also Using Specific IP for
Rendering Service.
Database
A collection of scripts to configure, maintain Should be installed on
Configuration 
and upgrade BriefCam database. the VSServer machine
files
Responsible for real-time video decoding,

object extraction, and classification. Consist
of single or multiple GPU cards, every APS
should have a single or multiple dedicated When installed on
GPU card(s). dedicated machine,
the Activation Tool
Install this component to enable the should also be
Respond module. installed
Multiple Alert Processing Servers can be Note: To use the alert
deployed per site depending on the real- processing server
Alert Processing time video processing requirements. A (APS), an APS license
single machine may host both a Processing *, **
Server (APS) must be installed with
Server and Alerts Processing Server for the processing server
both on-demand and real-time use cases, (PS) license on the
each with its dedicated GPUs assigned by same machine.
the GPU utility.
Multiple Alert Processing Servers can be
installed during the same implementation
on different machines with different
operating systems. The processing tasks
will be entered into the processing queue
and will be directed to the available server.
Responsible for automated process (ETL) **

Research ETL which updates incrementally the Research Should be installed on
Service BI platform data. Should be installed as the VSServer machine
part of the Research module.


Description
Troubleshooting and storage relocation Should be installed on

Tools 
tools. the VSServer machine
Face Should be installed on

Responsible for the face recognition
Recognition  a machine running a
ranking and feature extraction.
Service Processing Server
Responsible for fetching the videos from

the video management system (VMS).
Fetching service This service can be deployed multiple times 
(on different PCs) for stability and
scalability purposes.
Oracle XE or Standard Edition (metadata

database) and shared folder (video file Should be installed on
Database storage). The shared folder can be installed  the VSServer machine
on a local drive, network drive or a or on dedicated
dedicated machine. storage machine
Should be installed on
every machine on
Responsible for the communication which the VSServer
VMS Plugins between BriefCam Server to one or more  /Processing
VMS environments. Server/Alert
Processing Server is
installed
* Requires dedicated GPUs assigned by the GPU utility

**Should be selected only when the product includes the Respond module

Examples:
Environment Component per Server Component to Other BriefCam

Configuration Machine Select Installers
• Server • Web Services Installer

Distributed
• Research ETL Service • VMS Integration plugin
Environment (4
Installer
machines • Activation Tool
deployment, VSServer and • VMS SDK (if relevant)
• Rendering Service
according to the Rendering
• Database configuration
following files
topology:
• Video Integration
1 - hosting the Tester
VSServer and the
• Research Installer
Rendering Server, Research -
• ODBC Plugin Installer
1 - hosting the
Research module, • Processing Server (PS)
2 Processing Server • VMS Integration plugin
1 - hosting 2 (PS) • Activation Tool Installer
Processing • Face Recognition • VMS SDK (if relevant)
Servers (PS), Service
1 - hosting the 1 Alert Processing • Alert Processing Server • VMS Integration plugin
Respond module Server (APS) (APS) Installer
APS)
• Activation Tool • VMS SDK (if relevant)
• VSServer • Server • Web Services Installer

• Rendering • Research ETL Service • Research Installer
• Processing Server • Rendering Service • VMS Integration plugin
(PA) Installer
• Processing Server (PS)
• Respond (Alert • VMS SDK (if relevant)
• Activation Tool
All-in-One Processing Server
- APS) • Face Recognition
Service
• Research
• Database configuration
• VMS Plugin
files
• Video Integration
Tester

You will now be prompted to set up the database.

Confirm that the Database address correctly reflects the host name/IP address of the
database machine.
For an existing account, enter the password and for a new account, create and confirm the
password.
Click Next.
Select the installation destination paths and click Next.

For first time installations, make sure the Retain existing database settings checkbox is
not selected. You usually will not need to select this checkbox. If you do select it, the installer
will not override your existing database settings during the installation process. This is mainly
needed for setups that have manual configurations, such as cloud deployments.
Click Install.
Note that Microsoft IIS (Internet Information Services) will be installed automatically.
If you selected to install both the Alert Processing Server and the Processing Server in
step 5 above, the GPU Configuration tool will open. Configure the GPUs, click Save and then
close the tool to continue the installation. If you only select one, or none of the processing
servers, the tool will run silently and set any existing GPUs automatically. For more
information, see BriefCam GPU Configuration Tool.
Once installation is complete, keep the Test database connection checkbox checked and
click Finish.

If the database connection is successful, the following graphic will be displayed:
It is recommended to always log on with the same OS user to the BriefCam server.
The OS user that installs the BriefCam product has to be an administrator with full
privileges. This user should be the only OS user to log on to the BriefCam server post
installation.
Using Specific IP for Rendering Service

You can explicitly set which network interface card (NIC)/IP address the Rendering service should use to
stream video. You do this using the BaseVideoURL administrator setting.
1. In the Value field, replace {URL} with the IP address of the NIC.
2. Restart the Rendering service on every machine.

BriefCam GPU Configuration Tool

The BriefCam GPU configuration tool is designed to set up the GPU card according to the desired
processing mode and available resources.
The BriefCam.GPUConfigurationTool utility is installed by default with the BriefCam Server installation
to the following path: C:\Program Files\BriefCam\BriefCam Server.
Each GPU card should be assigned to a processing mode:
o On-demand processing (Review and Research modules)
o Real-time processing (Respond module)
If the Processing Server was installed, the GPU card will automatically be assigned to On-Demand
processing. If the Alert Processing Server was installed, the GPU card will be set up to Real-time
processing (Respond).
If both the Processing Server and Alert Processing Server are installed on the same machine, then the
GPU Configuration tool will be launched automatically when installing the BriefCam Server.
By default, both GPUs will be assigned to On-Demand processing and the user will set the desired GPU to
Real-time processing manually.
If you want to make any changes to the default settings, you can execute the tool manually.
The tool will set up the recommended number of workers based on the GPU hardware. The number of
Configured Workers displayed is identical to the number of Recommended Workers and can be modified
manually.

The number of Recommended Workers is calculated per a target resolution. However, the user can set
the Configured Workers manually if the target resolutions of the on-demand processing and real-time
processing are different.
Select the Include face recognition in workers calculation checkbox if you want the tool to take into
account face recognition, which consumes GPU memory, leaving less memory for the workers.
From the Select the face recognition ranking GPU drop-down list, which is a list of all of the GPUs
available for processing, select one GPU to be used for face recognition ranking and feature extraction.
Each loaded face, either from the Review process or an external file, is ranked and the features are
extracted (see the Face Recognition Quality section in the User Manual). Note that only one GPU should
be selected for the entire cluster. This means that in a clustered deployment where there are multiple
processing servers, only select a GPU from this drop-down list on one of the processing servers.
The GPU selected must be on-demand and it is recommended that the GPU will have at least 8 GB of
RAM.
If you select a GPU that the tool does not yet have benchmarked values for, a screen with known
configurations will open. You can use this list of known benchmark values to try and find a GPU similar to
the one that you are using.
BriefCam does not support using more than one type of GPU on the same machine.

The following table specifies the Number of Configured Workers that should be configured according
to Camera Resolution and GPU Memory for medium activity scenes. Please note that the maximum
common denominator should be chosen per GPU.
Camera # of Configured
GPU Memory (GB)
Resolution Workers
8 4
4K
11 4
8 11
1080P
11 18
8 19
720P
11 21
8 27
4CIF
11 25
BriefCam ODBC Plugin Installation (Optional)

This plugin is available for BriefCam Protect/Insights products.
The ODBC plugin should only be installed if the BriefCam Research (BI) component is installed on a stand-
alone machine. The ODBC plugin should be installed prior to the Research BI component.
To run the BriefCam Oracle ODBC Plugin Installation wizard, double-click
BriefCamOracleODBCPlugin_x64_<Version number>.exe.

Select the installation destination path and click Next.
At the database settings step, set the following:

o BriefCam database host name – set the host name on which BriefCam database is
installed. By default, the database is on the same machine as the VS Server, therefore
the value should be localhost.
o BriefCam database port number – port 1521 by default.
o BriefCam database service name – XE by default (for both the Oracle XE and Oracle SE
installations).
Click Install.

Click Finish.
BriefCam Research Installation

The Research component should be installed if you have a Protect/Insights product license.
Prerequisites
o The following ports are required during the BriefCam installation for the Research module.
Make sure that they are available before starting the installation:
Component Port #
HTTP 8090, 4248
HTTPS 4244, 443
API ports 4242, 4243
Additional ports* 4432, 4103, 4747, 4899, 4900, 4949
*The additional ports are used by the Research module and should be available on the Research machine.
o Before installing the Research component, close the Task Manager, Services, Computer
Management and MMC Console applications.
To run the BriefCam Research Installation wizard, double-click

BriefCamResearch_<Version number>.exe.
Click Next.

You will now be prompted to enter the Research settings as shown in the image below.
The fields will be populated automatically; confirm that the settings are correct:
o Research server hostname – the hostname where the Research component is
installed (use the system host name and not localhost).
o HTTP port – the Research module’s port. Populated with 8090 by default. To define
an alternative port if the default port is occupied, follow the details in section How to
Change Default Port Configuration.
o Oracle ODBC driver name – If the Oracle database is not installed on the same
machine as the Research module, the ODBC driver name must be installed first and its
name provided in the configuration screen above. If the Oracle database is installed on
the same machine, the ODBC driver is installed and populated automatically here. To

get the ODBC driver name that is installed on the machine, click the Search icon on the
Windows taskbar, type ODBC Data Sources (64-bit) as shown in the image below.
In the Administrator tool that is opened, click the Drivers tab (see following image).
In the Drivers window, find the Oracle installation, the name that is specified on the Name
column is the Oracle ODBC driver name.

o Oracle TNS name – The name of the Oracle database service (the SERVICE_NAME
field in the tnsname.ora file). The Oracle TNS name parameter (connection
name) can be found in the local naming parameters file (tnsnames.ora).
 If Qlik is installed in the same server as the DB
The local setting will be used. You will need to modify the local tnsnames.ora
file and set the right connection in the Oracle TNS name field. The
tnsname.ora file will be in the BriefCam Server installation folder (i.e.
C:\Program Files\BriefCam\BriefCam Server). And the Oracle TNS name is
usually XE, as in the following example:
 If Qlik is installed on a different server than the DB (Distributed)

Then the tnsname.ora file is in the Qlik Server in the Oracle plugin folder (i.e.
C:\oracle\instantclient_11_2\network\admin). And the Oracle TNS name is
usually Research, as in the following example:
The last three fields are only used by the installer to write the Research settings to the BriefCam
Oracle database. For an all-in-one installation, these will usually be populated automatically. If you
supplied your own Oracle server, you will need to manually enter these values.
o Database hostname – The machine name of the server where the Oracle database is
installed.
o Database port – The port number for the Oracle database.
o Service name – XE by default (for both the Oracle XE and Oracle SE installations).
Click Next.
You will now be prompted to install Qlik with the default license or to enter Research (Qlik)
license information, as illustrated in the image below.

To use the default license, make sure that the Install Qlik with the default license is
checked, click Next.
Enter the Research (Qlik) license information.
o Serial - Qlik license key.

o Control - Qlik control number.
o LEF - the LEF parameter should
only be specified if there is no
internet connectivity.
Click Next.
Select the data drive.
You can use local accounts or domain accounts. Make sure the domain account is a member of the local
Administrators group.
password.
Click Next.

The BriefCam user account should be a local administrator user on the local machine. Use the same
password you configured for the BriefCam user account that was created during the database installation.
Note: When upgrading the Research component, you cannot change the user. You must use the same
user that you used in the original installation and the user field will be grayed out.
Click Next.
Click Install to continue.
Please note that Research installation may take 10 minutes or more to completely install.
When installation has completed successfully, click Finish.

Creating a Virtual Proxy

A virtual proxy might be needed in the following conditions:
o When the Research machine is in a domain
o Other cases in which the Research machine has multiple host names
Note that a Qlik virtual proxy named bc is always created.
A virtual proxy can be used to handle different settings for the same physical server.
To define a virtual proxy, follow these steps:
In the Qlik Management Console (open a browser and use the following URL:
https://Research_Host_Name/qmc), select Virtual proxies on the QMC start page or from
the Start drop-down menu to display the overview.
In the Virtual Proxy window, select the pre-configured Central Proxy and click Edit.
Click Advanced, and in the Host white list section, click Add new value.
Add any names (not IPs) by which this server will be accessed. For example: localhost,
myhostname.mylocaldomain.
All values added here are validated starting from the bottom level. If, for example,
domain.com is added, this means that all values ending with domain.com will be approved. If
subdomain.domain.com is added, this means that all values ending with
subdomain.domain.com will be approved.

Click Apply. Wait for the service to restart; then, log in again, navigate back to the Virtual
Proxies page, and repeat the steps above for the bc Virtual Proxy.
BriefCam Web Services Installation

To run the BriefCam Web Services Installation wizard, double-click
BriefCamWebServices_64bit_<Version number>.exe.
Click Next.
To proceed with the installation, read and accept the License Agreement terms.
Click Next to continue.


password. (The user and password must be identical to the same credentials you have used in
all other distributed components.)
Click Next.
From the Environment settings screen, set the Licensing Server host name (BriefCam
Server host name) and the Database address.

Define the destination installation folder for WebServices, the Storage path and the BI
Certificate path (the Storage path must point to the exact location of the BriefCam
database).
Click Next.
In this screen, it is recommended to keep the default ports that were populated automatically.
Click Next.
The following step is required if the Research module (BI) is installed. Otherwise, skip this
step by clicking Next.

o Select the Research certificate path under the Research installation folder for
example C:\BriefCam\Certificates.
Click Install.
When the installation has completed successfully, click Finish.

If the Research component and the Web Services component were installed on separate
machines (distributed environment):
Copy the Certificates folder (located at: [Installation Path]:\BriefCam) from the
Research machine to the Web Services machine.
On the Research machine, grant BCUser full access permissions to the qlikshare
folder, which is located at: [Installation Path]:\qlikshare.
Share the folder with the BCuser account, and grant it full control.
Restart the IIS services on the VS Server and clear the browsers’ cache.
Add the VSServer IP and FQDN to the host whitelist control in Qlik QMC > Virtual
Proxy (add to both virtual proxies). This allows the VSServer to open a WebSocket
connection to the Research server.
K-Lite Installation
Install K-Lite on the Web Services machine and on all processing servers.
o Run the latest K-Lite Mega pack installation, which you can download from:
https://www.codecguide.com/download_k-lite_codec_pack_mega.htm.
Keep the default installation mode, Normal, and click Next.

Keep everything as it is by default and make sure that the Preferred video decoder is set to
LAV video decoder.
Keep everything as it is by default and click Next.


Click Decline.

Click Install.
Check the Run Codec Tweak Tool checkbox and click Finish.

Once the Codec Tweak Tool has opened, click Preferred Splitters.
Make sure that LAV Splitter is selected for every type of container. Scroll down the list and
select LAV wherever it is not selected. Once done, click Apply & Close.

Click Exit. The K-Lite codec pack installation is complete.
BriefCam VMS Integration Plugin Installation (for

BriefCam Protect/Insights/Rapid Review)
You can install one or more VMS-specific BriefCam integration plugins to subsequently enable the
BriefCam Server to connect to one more VMS environments (multiple simultaneous integrations are
supported). The VMS integration Plugin Installation, as well VMS SDK (for relevant VMSs) is required to be
installed on every machine on which the BriefCam Server/Processing Server/ Alert Processing Server is
installed.
Plugins are available for selected VMS systems (please refer to the Supported VMS Matrix table below).
Each installed plug-in will be embedded on the BriefCam Server for subsequent selection within the
BriefCam Server Admin application. For more information, see Video Source Setup in the Administrator
Manual.

Avigilon Integration
What Should Be Installed
o VMS SDK
o VMS integration plugin
Installation Guidelines
VM S SDK
Prior to the plugin installation, make sure you have the proper version of Avigilon SDK installed on the
BriefCam Server. If the Processing Sever is installed on dedicated machine, the proper version of Avigilon
SDK should be installed also on the BriefCam Processing Server.
For Avigilon 6.4, you need to have AvigilonControlCenterSDKRedistributable-5.6.0.18.exe installed
prior to plugin installation.
For Avigilon 6.10 you need to have AvigilonControlCenterSDKRedistributable-6.10.0.24.exe
installed prior to plugin installation.
I ntegration Plugin I nstallation
Run the VMS Integration Plugin Installation on the BriefCam Server by double-clicking the
BriefCamAvigilonPlugin_<Version_number>.exe file.
The VMS integration Plugin Installation is required to be installed on every machine on which
the BriefCam Server/Processing Server is installed.
Read and accept the License Agreement terms.
Select the path to the plugin installation directory. Please note that it should be the same
directory as the BriefCam Server directory.
By default, it is set to C:\Program Files\BriefCam\BriefCam Server\.
Click Install and continue as instructed by following the installation procedure.

Bosch Integration
o VMS SDK
o K-Lite Mega Codec Pack
VM S SDK
Prior to plugin installation, make sure you have the proper version of Bosch SDK installed on the BriefCam
Server. If the Processing Server is installed on a dedicated machine, the proper version of Bosch SDK
should be installed also on the BriefCam Processing Server.
For Bosch v7.5 and Bosch 9, install videosdk06120078x64.
Note: When configuring the Respond module to use Bosch cameras, the timestamp is not delivered as
part of the RTSP stream. As a result, BriefCam uses the local system time as the stream time minus a
configurable time lag to represent network and systems latency. This time lag can be configured in
BriefCam.Bosch6Fetcher.ini -> LiveDelaySeconds property (default is 0, meaning no delay).
Run the VMS Integration Plugin Installation by double-clicking the
BriefCamBoschPlugin_<Version_number>.exe file.
Install the VMS integration Plugin Installation on every machine where the BriefCam
Server/Processing Server is installed.
K -Lite M ega Codec Pack

Refer to the K-Lite Installation section in this document.

CASD Integration
o VISIMAX.OCX registry key
Make sure that the VMS and BriefCam servers’ operating systems are synced to the same
Network Time Protocol (NTP).
I nstalling the VI SI M AX.OCX registry key

Prior to the plugin installation, you need to add the proper VISIMAX.OCX parameter to the
Windows registry.
To add the VISIMAX.OCX parameter to the registry, copy the VISIMAX.OCX file to your
BriefCam Server PC and run a Command line as admin (CMD). To do so, click the Start
button, type cmd, and select cmd.exe from the search list on the right, followed by Run as
administrator.
Enter Regsvr32 <full path to the location where you put visimax.ocx> (i.e. Regsvr32
C:\VISIMAX.OCX).
A pop-up window will indicate that the registry has been added successfully. Click OK.
For additional information on how to add VISIMAX.OCX, please contact your System Integration
manager or BriefCam Support.


BriefCamVisiMaxPlugin_<Version_number>.exe file.


Digifort Integration
The Respond module is currently not supported for this VMS.
BriefCamDigifortPlugin_<Version_number>.exe file.

K now n I ssues w ith VM S Vendor
The configuration of cameras with MPEG-4 video formats is not supported.

Exacq Integration
(Only versions 14.6 and above with the Exacq integration are supported)
BriefCamExacqPlugin_<Version_number>.exe file.

Only K-Lite Mega Codec Pack versions 14.6 and above with the Exacq integration are supported

FLIR (Formerly DVTEL) Integration

o VMS SDK
o FLIR licenses (prerequisite requirement)
I ntegration - Plugin I nstallation
BriefCamDvtelPlugin_<Version_number>.exe file.
the BriefCam Server/Processing Server/Alert Processing Server is installed.
VM S SDK
DVTEL Latitude 7.0.0.5780 and 8 SDK (updates should be installed both on the VMS and on the BriefCam
Server machine), is required to be installed on every machine on which the BriefCam Server/Processing
Server/ Alert Processing Server is installed. It is not required to be installed on the client PC.
FLI R Licenses
The following FLIR certificates are required for the integration to work properly.
The licenses should be ordered from FLIR. Once you have received the license, apply it following FLIR’s
instructions on the VMS environment.
FLIR License BriefCam Component
Server Certificate SDK Connection 1 for VSServer
Respond Real-time Mobile User License 1 per GPU that is configured for Alert
Processing Processing Server (Respond module).
1 for VSServer.

Enabling M P4 Decoding
To enable MP4 decoding for the FLIR VMS:
1. Open the BriefCam.DvtelIntegration32.ini file, located at: Program
Files\BriefCam\BriefCam Server\32\BriefCam.DvtelIntegration32\.
2. Change the following line: ;EnableMP4Decoding=false to
EnableMP4Decoding=true (remove the semicolon (;) and set the value to true).

Genetec Integration
o VMS SDK
o Genetec licenses (prerequisite requirement)
o Genetec Security Center embedded client application
I ntegration - Plugin I nstallation
BriefCamGenetec<Genetec_version>Plugin_<Version_number>.exe file.
Select the specific installer according to your VMS version:
For GSC v5.7 SR3, run BriefcamGenetecSC5.7Plugin_<Version_number>.exe
For GSC v5.6/5.6 SR4 CU2, run BriefcamGenetecSC5.6Plugin_<Version_number>.exe
For GSC v5.5, run BriefcamGenetecSC5.5Plugin_<Version_number>.exe
For GSC v5.2/5.3/5.4, run BriefcamGenetecSC5.2Plugin_<Version_number>.exe
For Genetec Omnicast 4X, run BriefcamGenetecOmnicastPlugin_<Version_number>.exe
the BriefCam Server/Processing Server/ Alert Processing Server is installed.
VM S SDK
Security Center SC 5.7 SR3 SDK Installer is required to be present on every machine on which the is
BriefCam Server/Processing Server/Alert Processing Server is installed. This SDK version supports access
to Security Center 5.7 SR3.

Security Center SC 5.6 SR4 SDK + Update pack CU2 Installer is required to be present on every
machine on which the BriefCam Server/Processing Server/Alert Processing Server is installed. This SDK
version supports access to Security Center 5.6 and 5.6 SR4 CU2.
Genetec Licenses
The following Genetec certificates are required for the integration to work properly.
The licenses should be ordered from Genetec (see Genetec part numbers in the table below). Once you
have received the license, apply it following Genetec’s instructions on the VMS environment.
Genetec Security Center license:
Genetec Security Center Part# BriefCam Component
Server Certificate GSC-1SDK-BRIEFCAM-VSEnterprisS 1 for VSServer and BriefCam Server
Administrator Application (both of
BriefCam’s components are installed on
the same machine and therefore can use
the same certificate. To use the same
license, the VSServer should be stopped
before configuring the VMS directory)
1 per GPU that is configured for Alert
Processing Server (Respond module)
Client Certificate GSC-1SDK-BRIEFCAM-VSEnterprisC 1 per Embedded Client deployed (license
per Security Desk client). The client
certificate is required in order that the
embedded BriefCam client will appear
within the Genetec Security Desk
application’s Video Synopsis tab.

Genetec Security Center Em bedded Client I nstallation

The following section describes the installation and configuration that need to be performed to allow the
BriefCam web client application to become embedded in the Genetec Security Desk Application.
After installing the Genetec plugin and the relevant SDK on the BriefCam Server, and after applying the
Genetec certificates, you are ready to install Genetec Embedded Client.
On the same computer where the Genetec Security Desk Application, run the Embedded
Integration Plugin Installation by double-clicking the
BriefCamEmbeddedClientForGenetecSecurityCenter_64bit_<Version_number>.ex
e file.
To proceed with the installation, read the license and indicate acceptance of the License
Agreement terms. After you have accepted the terms, click Next to continue.


Note that the installation path must be the same directory where Genetec Security Desk
Application is installed.

Enter the BriefCam Web Application URL and verify that the provided URL is correct by clicking
the Verify URL button (both IP address or hostname values can be specified).
The URL will be saved in BriefCam.GenetecEmbeddedViewer.dll.config, which is located by

default in C:\Program Files (x86)\Genetec Security Center x\Plugins\BriefCam.
Once the installation is complete, the URL configuration can be modified manually as needed.
For example:
<appSettings>
<add key="serverAddress" value="x.x.x.x/Synopsis/" />
</appSettings>
Note: Both IP address or hostname values can be specified.

Click Install.

Your installation is now complete. Click Finish.

To establish a connection from the BriefCam client embedded in the Genetec Security Desk
Application to the BriefCam Server:
o Launch the Genetec Security Desk Application and log in to the Genetec server.
o Once it is up and running, access the Genetec Security Desk main Tasks view. A
Video Synopsis icon for an embedded BriefCam client will appear under the
Integration section. Click the Video Synopsis icon to access the embedded
BriefCam client in a separate application tab.

o You will be asked to log into BriefCam upon clicking the Video Synopsis icon. Enter
your username and password and click Sign In.
o Upon logging in, the embedded BriefCam client will appear within the Genetec Security
Desk application’s Video Synopsis tab.
Please note: Bookmarks created within BriefCam will not be displayed on Genetec
Security Desk application.

Silent I nstallation of Genetec

To run a silent installation of Genetec, use the following command line:
"BriefCamEmbeddedClientForGenetecSecurityCenter_64bit_<Version>.exe"
/v"INSTALLDIR=<Path to Genetec Security Center 5.7
location> BC_SERVER_HOSTNAME=<ServerHostname/IP>/synopsis/ /qr+ /log
GenetecEmbedded.log"
For example:
"BriefCamEmbeddedClientForGenetecSecurityCenter_64bit_5.4.0.17839.exe"
/v"INSTALLDIR=\"C:\Program Files (x86)\Genetec Security Center 5.7\"
BC_SERVER_HOSTNAME=10.0.0.189/synopsis/ /qr+ /log GenetecEmbedded.log"
Connecting to Genetec Aux iliary Archiver

If Genetec Auxiliary Archiver is configured on the VMS and BriefCam is configured to connect to it, then
every request from the VMS will automatically fetch video from the auxiliary archiver. If you wish to
connect to Genetec Auxiliary, make sure to edit the BriefCam.GenetecSc52Fetcher32.ini file, which is
located by default at C:\Program Files\BriefCam\BriefCam Server\32\plugins – Set the
;UseAuxiliaryArchiver = false parameter to true, uncomment the line and save the file.

Sending Alerts to Genetec

Alerts can be sent to Genetec Security Center’s Alarm monitoring tab.
In the Administrator Settings’ VSServer section, there are two settings relevant for sending alerts outside
of BriefCam (see the image below):
o To send alerts outside of BriefCam, set the RespondAlertsPublishEnabled setting to
true.
o To change the polling interval, use the
Respond.AlertsPublishingIntervalInMilliseconds setting.
If you make changes to the settings, you need to restart or start the VSServer.
When the Genetic plug-in is installed, the BriefCam.GnetecSc57Fetcher.ini file is created at:
C:\Program Files\BriefCam\plugins. The [Alerts] section contains the DefaultAlarmName
parameter, which is used as the connection between BriefCam and Genetec.
In order for this to work, a new Alarms entity should be configured in the Genetec Config Tool and it
should be assigned a recipient who is the same user that is used by BriefCam to connect to the VMS.

GeoVision Integration
BriefCamGeoVisionPlugin_<Version_number>.exe file.

Geutebruck Integration
BriefCamGeutebrueckPlugin_<Version_number>.exe file.

HikVision Integration
BriefCamHikVisionPlugin_<Version_number>.exe file.

IndigoVision Integration
o Prerequisite configuration
The Respond module for this VMS is only supported on cameras that are on the actual VMS
(ControlSiteDb / NVR) and not cameras that are added through the gateway.
Prerequisite Configuration
In order for the BriefCam plugin to connect to the Control Center Site Database and be enabled to fetch
video, the following conditions should be met:
o The same Windows user (local user) should be configured on all machines (BriefCam
Server, BriefCam Database and the machine hosting the Control Center Site Database).
The user must have administrator privileges on the machine hosting the BriefCam
Server. In case of BriefCam distributed environment setup, you can use the default
BCuser that is created during installation and create the same user on the machine
hosting the Control Center Site Database.
o The user should have access to the Control Center Site Database folder.
o The Control Center Site Database folder should be manually configured in the
BriefCam.IndigoIntegration32.ini file located at C:\Program
Files\BriefCam\BriefCamServer\32\plugins where the DbFolderPath
parameter points to the location of the Site Database as such
\\<[IP or HostName]\FolderName>, for example: DbFolderPath =
\\172.1.1.122\ControlCenterDB.
The steps for the above configurations are as follows:
On the machine hosting the Control Center Site Database, navigate to the DB folder
IndigoSiteDB and share this folder with the user that is available on all machines. Grant the
user Read/Write permissions.
On the machines hosting the BriefCam Server or BriefCam Database, add the IP/host name
(with the relevant credentials) of the machine hosting the Control Center Site Database:
o Navigate to the Control Panel->User Accounts->Credentials Manager.

o Click Add a Windows Credential.

o You will be prompted with 3 fields to fill in: the IP/host name of the machine hosting
the Control Center Site Database, the Windows username (of the user that has access
to the Control Center Site Database folder), and the password. Be sure to enter the
details correctly.
On the BriefCam Server machine, set the VSService to log on using the username you have
already configured with access to the Control Center Site Database folder:
o Open the Services dialog through the Start menu or the Task Manager.
o Locate the VSService service on the list and right click. Click Properties.
o On the Log On tab, click the This account radio button.
o Enter the username and password for the user that has access to the Control Center
Site Database folder.

BriefCamIndigoVisionPlugin_<Version_number>.exe file.
the BriefCam Server/Processing Server/ Alert Processing Server is installed


Milestone Integration
o Milestone embedded client application
BriefCamMilestonePlugin_<Version_number>.exe file. You need to install the VMS
integration plugin on every machine on which the BriefCam Server/Processing Server/Alert
Processing Server is installed.
Read and accept the License Agreement
terms. Then, select the path to the
plugin installation directory. Please note
that it should be the same directory as
the BriefCam Server directory. By
default, it is set to C:\Program
Files\BriefCam\BriefCam Server\.
If you installed the simple version of the
BriefCam XProtect® client, leave the
Install the SSO provider checkbox
unchecked and click Next.
If you installed the enhanced BriefCam
XProtect® client, you need to check the
Install the SSO provider checkbox
and enter the address where you
installed the BriefCam Open API (BOA).
To install the SSO provider, BriefCam Open API (BOA), which is licensed separately, must
be installed.
Click Install.

M ilestone Em bedded Client I nstallation

The following section describes the installation and configuration that need to be performed to allow the
BriefCam web client application to become embedded in the Milestone XProtect Smart Client.
After you have installed the Milestone plugin on the BriefCam Server, you are ready to install Milestone
Embedded Client.
Note: Milestone smart client (64 bit) version 2017 R3 and below are not supported.
On the same computer on which Milestone XProtect Smart Client is installed, run the
Embedded Integration Plugin Installation by double-clicking the
BriefCamEmbeddedClientForMilestoneXProtect_64bit_<Version_number>.exe file.
Read the license, accept the License Agreement terms and click Next.


Note that the installation path must be the same directory where Milestone XProtect Smart
Client is installed.
Enter the BriefCam Web Application URL and verify that the provided URL is correct by clicking
the Verify URL button.
The URL will be saved in BriefCam.MilestoneEmbeddedViewer.dll.config, which is located by

default at C:\Program Files\Milestone\XProtect Smart Client\MIPPlugins\BriefCam.
If you installed the simple version of the BriefCam XProtect® client, leave the BriefCam Open
API (BOA) Server Address field blank. If you installed the enhanced BriefCam XProtect®
client, enter the address where the BriefCam Open API (BOA) was installed.
Click Next.
Once the installation is complete, the URL configuration can be modified manually as needed.
Click Install.
Your installation is now complete. Click Finish.

To establish a connection from the BriefCam client embedded in the Milestone XProtect Smart
Client to the BriefCam Server:
o Launch XProtect Smart Client and log in to the Milestone server.
o Once it is up and running, a BriefCam Video Synopsis tab will appear in the XProtect
client’s main application window. Click it to access the embedded BriefCam client in a
separate application tab.

o You will be asked to log in to BriefCam when you click the Video Synopsis tab. Enter
your user name and password and click Sign In.
o Upon logging in, the embedded BriefCam client will appear within the Milestone
XProtect Smart Client’s Video Synopsis tab.
Note: Bookmarks created within BriefCam will not be displayed on the Milestone XProtect
Smart Client application.

Sending Alerts to M ilestone

Alerts can be sent to Milestone’s Alarm Manager.
In the Administrator Settings’ VSServer section, there are two settings relevant for sending alerts outside
of BriefCam:
o To send alerts outside of BriefCam, set the RespondAlertsPublishEnabled setting to
true.
o To change the polling interval, use the
Respond.AlertsPublishingIntervalInMilliseconds setting.

If you make changes to the settings, you need to restart or start the VSServer.
When the Milestone plug-in is installed, the BriefCam.MilestoneIntegration.ini file is created at:
C:\Program Files\BriefCam\plugins.
The [Alert] section contains four parameters relevant to sending events to Milestone: Vendor,
Description, Message and SendAnalyticEvent.
By default, BriefCam sends an alarm to Milestone and no farther configurations are required to make the
alarm appear in the Milestone client.
BriefCam can also send an analytics event to Milestone instead of an alarm by setting the
SendAnalyticEvent parameter to true in the BriefCam.MilestoneIntegration.ini.
Note that only alerts produced by the Milestone connected cameras will be sent to the Milestone server.
Performing Milestone actions
The analyticsEvent sent by BriefCam can be utilized in Milestone to perform actions, such as: Start
recording on <device>, Start feed on <devices>, etc. This is done by configuring a Milestone rule based
on the analyticsEvent as follows:
1. In Milestone’s Management Client, go to Rules and Events - Rules.
2. Create a new rule.
3. On the first step, leave the option Perform an action on <event>.
4. In the Edit the rule description field, click the underlined event (as shown in the image
below).

5. A tree menu will appear at the bottom, where you will see Analytics Events. Select the
event that you want to trigger the rule and then design the rule.
Creating a Synopsis Directly from M ilestone

If you installed the enhanced BriefCam XProtect® client, you can create a synopsis directly form Milestone.
When you are viewing a video in Milestone (in the Live tab, Playback tab and a floating image), you can
click the BriefCam icon at the bottom right of the screen. This will create a new video synopsis in
BriefCam.

Once you click the BriefCam icon, the following screen will appear.

At the top right of the screen, select either to Create a new case or Add to existing case, and then
click OK.
You will then see at the bottom left of the screen the BriefCam icon and see the progress
of the synopsis’s processing.
Click the BriefCam icon to navigate to the BriefCam tab and to the correct case.
K now n Lim itations

The BriefCam Server stops extracting new objects while Milestone archives data. It restarts automatically,
but there is a temporary latency of a few minutes.

OnSSI/SeeTec Integration
Note that the same plugin installer is used for both OnSSI and SeeTec integration.
Note that SGS and Transcoding modules should be installed on the VMS in order for BriefCam to work
properly, please contact your system administrator.
BriefCamOnSSISeeTecPlugin_<Version_number>.exe file.
the BriefCam Server/Processing Server is installed


Qognify (Formerly Nice) Integration

o VMS SDK
VM S SDK
Prior to plugin installation, make sure you have the required NiceVision SDK installed on the BriefCam
Server. You need to have PlayerComponent Package_12.1.0.147.exe for NiceVision 3.1 installed
prior to plugin installation.
The SDK is required to be installed on every machine on which the BriefCam Server/Processing Server is
installed.
BriefCamNiceVisionPlugin_<Version_number>.exe file.
the BriefCam Server/Processing Server is installed
After you have accepted the terms, select the path to the plugin installation directory. Please
note that it should be the same directory as the BriefCam Server directory.


Salient Integration
o Port configuration
BriefCamSalientPlugin_<Version_number>.exe file.

Port configuration
When configuring Salient directory using the VSAdmin application, it is important to specify the VMS HTTP
port number. The port number can be found on the Salient CompleteView Server configuration application,
as shown below:

To configure the directory on the BriefCam VSAdmin application as follows:

o Set up the Server IP followed by the port number in the following format
http://IP_Address:Port#.

Teleste Integration
o Setup API token
BriefCamTelestePlugin_<Version_number>.exe file.
Teleste AP I Token Setup

An API token (software key) should be provided by Teleste to allow integration with the VMS. This token
should be manually added into the BriefCam Teleste plugin ini file that is available on BriefCam Server:
…\plugins\BriefCam.TelesteIntegration.ini.
Simply type the provided key into the API Token section.

Verint Integration
o Installation prerequisite
I ntegration I nstallation Prerequisites
The Windows user must have access to the VMS file system in order for BriefCam to be able to fetch
video from the VMS. Grant access by performing the following steps:
Open File Explorer on the VSServer and navigate to the VMS by entering the VMS installation
path in the navigation bar (remember to add \\ before the actual IP address or host name).
Add the VMS IP/host name with the relevant user in the credential manager by navigating to
Control panel->User accounts->Credentials manager and click Add a Windows credential.
You will be prompted with three fields to fill in: the VMS IP/host name, the actual Windows
username, and the password. Make sure to enter the details correctly.
Set the VSService to log on as the user you have already configured to have access to the
VMS file system. Do so by opening the Services dialog through the start menu or the task
manager. Locate the VSService service in the list and right click on it, select Properties, and
then select the Log on tab. Click on the This account radio button and fill in the details
(account name and password). Make sure that you enter the credentials correctly and that the
account name is the same as the user chosen in the previous steps.
Please note that Verint VMS login credentials are case sensitive.

BriefCamVerintPlugin_<Version_number>.exe file.



Supported VMS Matrix

VMS platforms supported by BriefCam Protect, Insights and Rapid Review:
Hardware/Software
Latest Certified Decoding Support
Respond
Vendor Product Model Version BriefCam
Support On-
Version Real Time
Demand
Hardware (on
Avigilon Control Control
Avigilon 6.10.2.8 5.3.1 Yes Software selected
Center Center
modes)
Bosch Video
Bosch BVRM 7.5 5.4 Yes Hardware Hardware
Security
Bosch Video
Bosch BVMS 9 5.4 Yes Hardware Hardware
Security
VisiMAX NVR-
CASD Visimax 8.7 5.4 Yes Software Hardware
RTSP
Digifort
Digifort Digifort 7.2 5.3.1 No Software N/A
Enterprise
Digivod Digivod 4.0 4.3.0 No
Exacq ExacqVision ExacqVision 8.2.1 5.3.1 No
Exacq ExacqVision ExacqVision 9.6 5.4 Partial Software Hardware
FLIR
7.0.0.57
(formerly Latitude Latitude 5.3.1 Yes
80
DVTel)
FLIR Hardware
(formerly Latitude Latitude 8 5.3.1 Yes Software (disabled by
DVTel) default)
5.6 SR4
Security CU2
Genetec Security Center 5.4 Yes
Center (5.6.977.
19)
5.7 SR3
Security
Genetec Security Center (5.7.809. 5.4 Yes Software Software
Center
45)
Geovision NVR N/A 8.5 3.1.0 GA No
Geutebruck 3.2.2.52
G-Core G-Core 5.3.1 No Hardware Software
GmbH 3
Hikvision DVR N/A 4.2 3.1.3 No

Hardware/Software
Latest Certified Decoding Support
Respond
Vendor Product Model Version BriefCam
Support On-
Version Real Time
Demand
Control
IndigoVision Control Center 14.2 5.4 Yes * Hardware Hardware
Center
2017 R3
Milestone XProtect Corporate 5.3.1 Yes
(11.3a)
2018 R3
Milestone XProtect Corporate 5.4 Yes Hardware Hardware
(12.3a)
Milestone XProtect Corporate 2019 R1 5.4 Yes Hardware Hardware
Qognify
(formerly NiceVision Qognify SVR 3.1 5.2.1 UP3 No Hardware Software
Nice)
CompleteView CompleteVie
Salient 4.1 5.2.1 UP3 No
Pro w Pro
CompleteView CompleteVie
Salient 4.8.1.36 5.4 No Hardware N/A
Pro w Pro
SeeTec / SeeTec Cayuga /

R9 / 5.3.1873 6.9.1 5.4 No
OnSSI OnSSI Ocularis
SeeTec / SeeTec Cayuga /

R11 / 5.5 5.3.0 Yes
OnSSI OnSSI Ocularis
SeeTec / SeeTec Cayuga / 6.12.1.0

R12 / 5.6 5.3.0 Yes Hardware Hardware
OnSSI OnSSI Ocularis 2
Teleste Teleste Teleste 4 4.3.0 No Software Software
Timespace
Timespace X300 5.4 No
(decoder)
6.4.3.28
Verint Nextiva Nextiva 5.2.1 UP2 No
11
7.5.7623
Verint Nextiva Nextiva 5.4 No Hardware Hardware
.0
* For the IndigoVision VMS, Respond will only be supported on cameras that are on the actual VMS (ControlSiteDb / NVR) and
not cameras that are added through the gateway.

Infodraw Integration Installation

This plugin is available for the BriefCam Investigator, Investigator for Teams and Protect versions.
BriefCam supports Infodraw DVR exported file format (MP4 and .FLV file formats).
The following section describes the installation process.
o Integration plugin installation
Run the Integration Plugin Installation by double-clicking the
BriefCamInfoDrawPlugin_<Version_number>.exe file.
The Integration Plugin Installation is required to be installed on every machine on which the
BriefCam Server/Processing Server is installed.
Enable the Infodraw decoder in RenderingService.ini and in the VSServer.ini file on the
Server directory, by removing the semicolon character:
; BriefCam InfoDraw Decoder = 5ae7da91-25d6-4e0f-be32-9b415d389b4c
If the InfoDraw files are encrypted, specify the password in “BriefCam.InfoDrawDecoder.ini”
C:\Program Files\BriefCam\BriefCam Server\plugins.

Timespace X300 Integration Installation

This plugin is available for the BriefCam Investigator, Investigator for Teams and Protect versions.
BriefCam supports Timesapce X300 DVR exported file format (XBA file format, single stream & multi-
stream).
The following section describes the installation process.
o Integration plugin installation
Run the Integration Plugin Installation by double-clicking the
BriefCamTimespaceX300Plugin_<Version_number>.exe file.
The Integration Plugin Installation is required to be installed on every machine on which the
BriefCam Server/Processing Server is installed
Enable the XPEG decoder in RenderingService.ini and in the VSServer.ini file on the
Server directory, by removing the semicolon character:
;BriefCam XPEG Decoder = A637C67D-0D3D-4A64-B143-00C6F857405A

How to Change Default Ports Configuration

To define alternative ports in case one of the default ports is occupied, follow the steps below.
Research HTTP Port (8090):
https://Research_Host_Name/qmc), select Proxies on the QMC start page or from
the Start drop-down menu to display the overview. Select Central proxy and click Edit. Click
the Ports tab on the right-side menu.
In the Proxies window, select Edit Proxy and change the default 8090 port on Service
listen port HTTP to an available port.
On the machine where the Web Services are installed, edit the Reserach HTTP Port on the
Web config file. The file is located in the BriefCam Web Services installation folder (i.e. C:\
inetpub\ProWebApi\Web.config), by updating QlikHttpPort value to the same port you have
configured on the Qlik Management Console:
<add key="QlikHttpPort" value="8090" />
Research API Ports (4242, 4243)

https://Research_Host_Name/qmc), select Proxies on the QMC start page or from
the Start drop-down menu to display the overview.
In the Proxies window, select Edit Proxy and change the default 4242/4243 ports on REST
API listen port/Authentication listen port HTTP to an available port.

On the machine where the Web Services are installed, edit the Reserach API Ports on the
Web config file. The file is located in the BriefCam Web Services installation folder (i.e. C:\
inetpub\ProWebApi\Web.config), by updating QlikQrsPort /QlikProxyPort values to the
same ports you have configured on the Qlik Management Console:
<add key="QlikProxyPort" value="4243" />
<add key="QlikQrsPort" value="4242" />
License Activation
BriefCam products should be activated and registered prior to first use. Use the supplied BriefCam License
Activation application and the provided product key to activate the software. Both online (Internet-
connected) and offline activation modes are supported.
If a physical software protection dongle is used, no activation is required,

! and this section can be skipped entirely.
To extend or renew your software license, please contact your sales channel
or BriefCam presales representative. In some cases, such as license
extension or product renewal, product keys may be delivered by e-mail.
Online Activation
Online activation requires an active Internet connection.

To perform online activation:

Launch the BriefCam License Activation application from the VSServer machine’s Start menu.
Enter your product key and click Activate.
Upon successful activation, the following dialog will appear.
Click OK to close the dialog, then click Close in the main application window to close the
License Activation application.

Offline Activation
Offline activation is useful in cases where Internet connectivity is not readily available on the computer
being used to install BriefCam products.
Two offline activation flows are supported – one intended primarily for use with a stand-alone PC lacking
an Internet connection, and the other involving the use of an intermediary, Internet-connected PC.
To perform offline activation on a stand-alone PC lacking an Internet connection:
Launch the BriefCam License Activation application.
Click the Offline tab to access offline activation.
Click 1. Collect Information to generate a c2v (client to vendor) file, select or approve the
destination in which it is to be stored, and click Save.

E-mail the c2v file to license@briefcam.com. The BriefCam support group will then respond by
e-mailing you the appropriate v2c (vendor to client) file required for activation.
Click 3. Apply license in the main License Activation application window, select the v2c file
provided by the BriefCam support group when prompted to do so, and click Open.
The BriefCam product will now be activated. Once informed of successful product activation,
click OK and close the License Activation application.
To perform offline activation via an intermediary PC with an Internet connection:

Launch the BriefCam License Activation application.

Click the Offline tab to access offline activation.
Click 1. Collect Information to generate a c2v (client to vendor) file, select or approve the
destination in which it is to be stored, and click Save.
Transfer the c2v file (via a USB stick, for example) to an intermediary PC on which the License
Activation application is also installed and on which an Internet connection is available. Launch
the License Activation application on this PC, click the Offline tab for offline activation, and
click 2. Retrieve license.
Enter your product key in the appropriate field on the dialog that appears, then click the
browse button (..) next to Information file: (input) to locate and load the c2v file
generated on the offline PC.

Now click the browse button (..) next to License file: (output), select a desired destination
in the browse dialog that pops up, and click Save. The License Activation application will then
generate and save an appropriate v2c (vendor to client) activation file.
Transfer the v2c file back to the offline PC and Click 3. Apply license in the main License
Activation application window.

Select the v2c file generated via the intermediary PC when prompted to do so and click Open.
The BriefCam product will now be activated. Once informed of successful product activation,
click OK and close the License Activation application.
For details about how to launch BriefCam, see the User Manual.
Running BriefCam in Virtual Environments

BriefCam generally recommends using dedicated physical hardware servers for production environments,
as per the specifications outlined earlier in this section. In some cases, customers may wish to employ
VMs (Virtual Machines) to run BriefCam software. While this is technically possible, VMs tend to
excessively depend on virtualization solution resources, and may be impacted by other concurrently
running VMs. BriefCam therefore cannot guarantee optimal performance for customers using such
environments.
If customers want to use VMs in accordance with the limitations stated above, they will need to assure
that VMs conform with the physical hardware server specifications recommended by BriefCam, and
specifically that the virtualization products reserve and allocate the GPU, CPU and RAM resources required
by BriefCam. Additionally, disk IOPS performance (whether of the virtual machines or of external NAS or
SAN storage devices) must be guaranteed to be similar to that of a local disk.
Page 100 of 101 © BriefCam | 4/19/19

Contact Information
AMERICAS
Riverside Center
275 Grove Street Suite 2-400
Newton, MA 02466 USA
+1-860-269-4400
APAC
1 Harbourfront Place
Harbourfront Tower One
04-01 Singapore 098633
+65 6722 3770
EMEA
2 HaMa’yan Street
Modi’in Technology Park
Modi’in 7177871 Israel
+972-2-533-7228
Visit us on social m edia
Page 101 of 101 © BriefCam | 4/19/19

BriefCam v5.4 Installation Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BriefCam v5.4 Installation Guide

Caricato da

Copyright:

Formati disponibili

TRANSFORMING VIDEO SURVEILLANCE

INTO ACTIONABLE INTELLIGENCE

Page 2 of 101 © BriefCam | 4/19/19

FLIR (Formerly DVTEL) Integration ................................................................................... 56

Page 3 of 101 © BriefCam | 4/19/19

o Windows 10 Pro or Windows Server 2016

Page 4 of 101 © BriefCam | 4/19/19

Firewall Consideration and Local Ports Availability

Research (BI) Ports:

Page 5 of 101 © BriefCam | 4/19/19

All-in-One or Distributed Deployment

Upgrade to 5.4 Instructions

To upgrade to V5.4, follow the instructions below:

Page 6 of 101 © BriefCam | 4/19/19

Page 7 of 101 © BriefCam | 4/19/19

From Version Build Number Run Scripts

Page 8 of 101 © BriefCam | 4/19/19

If upgrading the Research module from v5.2 or v5.2.1:

The changes will take effect in the next Qlik run.

Page 9 of 101 © BriefCam | 4/19/19

Select the drive where you want to install Oracle XE.

Select the data drive on which you want to install Oracle.

Page 11 of 101 © BriefCam | 4/19/19

Use a password that is compliant with your password policy.

Page 12 of 101 © BriefCam | 4/19/19

Once the Oracle installer is displayed, click Next.

Page 13 of 101 © BriefCam | 4/19/19

Page 14 of 101 © BriefCam | 4/19/19

Page 15 of 101 © BriefCam | 4/19/19

Your Oracle XE installation is now complete. Click Finish.

Page 16 of 101 © BriefCam | 4/19/19

Installing the Database for Network Storage

Setting Up the Data Drive on a Shared Network Drive

Page 17 of 101 © BriefCam | 4/19/19

BriefCam Server Installation

To run the BriefCam Server Installation wizard, double-click

Page 18 of 101 © BriefCam | 4/19/19

Accept the terms of the license agreement and click Next.

Page 19 of 101 © BriefCam | 4/19/19

Page 20 of 101 © BriefCam | 4/19/19

Required BriefCam Server Components

Administration Manages, configures and monitors the Should be installed on

Responsible for access control and video

Responsible for video decoding, object

Responsible for video rendering, can be

Page 21 of 101 © BriefCam | 4/19/19

Server All-in-One Distributed

The Rendering service can be installed on

Responsible for real-time video decoding,

Responsible for automated process (ETL) **

Page 22 of 101 © BriefCam | 4/19/19

Server All-in-One Distributed

Troubleshooting and storage relocation Should be installed on

Face Should be installed on

Responsible for fetching the videos from

Oracle XE or Standard Edition (metadata

* Requires dedicated GPUs assigned by the GPU utility

Page 23 of 101 © BriefCam | 4/19/19

Environment Component per Server Component to Other BriefCam

• Server • Web Services Installer

• VSServer • Server • Web Services Installer

Page 24 of 101 © BriefCam | 4/19/19

You will now be prompted to set up the database.

Select the installation destination paths and click Next.