RC-E User Manual
OnSSI Federated Architecture
Basic Rules of Federated Sites
One Parent-Many Children
A child can only have one parent, but a parent can have an unlimited number of children.
Parent Requests Child, Not the Other Way Around
A new parent/child link is always requested by the parent, and if necessary, authorized by the child. See Accepting
Inclusion in the Hierarchy (see "Manage OnSSI Federated Architecture" on page 177).
One Level at the Time
A parent knows about all its children, children's children, etc., but only controls them one level down. Furthermore a
child only knows about and answers to its parent one level up.
Synchronization of Hierarchy
A parent always contains an updated list of all its currently attached children, children's children, etc. But when distant
communication is needed, it takes place level by level, each level forwarding and returning communication, until it
reaches the server requesting the information. Depending on the number of levels that must be updated, changes to a
hierarchy might take a little time to become visible in the Federated Sites Hierarchy pane (see "Panes Overview" on
page 36), see Refreshing the Site Hierarchy (see "Manage OnSSI Federated Architecture" on page 177). The
federated hierarchy has a regularly scheduled synchronization between sites, as well as management-triggered
synchronization every time a site is added or removed. This synchronization only contains site configuration data and
each time will send less than 1MB. In addition to the data sent during synchronization, video or configuration data will
be sent when a user or administrator views live or recorded video or configures the system. The amount of data in this
case depends on what and how much is being viewed. It is not possible to schedule your own synchronizations.
Principles for Setting Up Federated Sites
When working with federated architecture, the link between management servers is established from the
management server wanting to become parent to another management server. Theoretically, establishment of a
parent/child relationship happens as follows:
1. The parent sends a link request to the potential child.
2. Depending on administrator settings, the child might have to authorize the link request.
3. If necessary, the child authorizes the link request.
4. Relevant info is exchanged.
5. The new parent/child link is established.
The Administrator Role and Federated Sites
Administrator vs. Non-administrator
In general, you must be an administrator to work with federated architecture. However, by requesting the
adding of children to a top-site (to which you have administrator rights), you can (without administrator rights
to the other sites) create the overall initial infrastructure of a federation. But, as described in Manage OnSSI
On-Net Surveillance Systems, Inc.
174
