There are several ways to deploy the eConnect system. This section will describe the desired
Information Technology Data Hosted, Surveillance segmented
In today’s common casino systems, it is likely that Surveillance and the IT dept are segmented.
Data collection being done at the Surveillance Level is possible, but historically more
complicated due to firewalls, network address translations, etc. In larger environments where
users of both Surveillance and other departments want access to the data sets created by
eConnect, We recommend a two server approach. This way we can actively protect the video
system, and still grant access to users to the data they need.
Keep in mind, the above diagram is just an example. But it does allow for easier module
additions as the product grows. This type is topology would be recommended when there are
several eConnect modules deployed, with several different user groups (not just surveillance)
attempting to see the data.
In today’s systems IT depts, it is likely that the team is already managing a Microsoft SQL
server. Your DBA can add the required databases to the server as well as handle disaster
recovery options not normally managed by surveillance teams. It is also very likely that the
Casino has an active directory infrastructure, so you can manage your users using LDAP user
groups. If a user leaves the company and their account is disabled in AD, it also disables in
The server located in the Surveillance network, is only a simple application server used to
handle requests of the Surveillance user, process video snapshots, exports and store video
cases not accessible to the IT dept.
Single Server, Surveillance Managed
In most initial deployments of eConnect, a single server approach is used. This may be the
easiest way to get the eConnect application installed. eConnect typically supplies a server with
eConnect pre-installed and all of its services used for collecting data. In the diagram shown
below, optionally the IT dept may consider hosting the eConnect databases instead of keeping
them on the eConnect server. This lowers costs if the site requires a full version of SQL server.
In the below pictured diagram, it is likely that there will be some kind of firewall or NAT sitting
between the two networks. Each integration with eConnect will have a unique set of firewall
requirements to accomplish the integration.
It is possible to keep users outside of surveillance from being able to see video, cases,
snapshots and exports. This is accomplished within eConnect user control, which can also be
tied to Active Directory permission groups.