Praise Jesus
Get instant WHOS-IN updates notification with Twitter

SIP Member

StrikeStar

Hudson Software supplies real time Lightning Tracker data to the Australian StrikeStar lightning detector network as a free community service. Click StrikeStar logo for lightning map.


Hudson Software now runs on 100% green power! With our new solar panels, we now generate more power than we use !

WHOS-IN Pro - Admin Help


Auto Sync:



If you select the SERVERS node (from the Main Screen TreeView), and there are existing valid entries for remote servers, the AutoSync node (on the TreeView) will be enabled. This allows you to synchronize LISTS of remote databases so that users in one database can attach to another database and examine the status of people in another area.


Example:



Imagine the scenario above, where a company might have branch offices spread across 5 cities linked by a high speed Wide Area Network (Optic or T1+). Each branch has their own 'server' copy of WHOS-IN, however not all offices can 'see' each other (because not everyone has updated their 'Remote Servers' list).


Perth can't see anyone, Adelaide can see Perth and Melbourne, Melbourne can see Sydney and Adelaide, Sydney can see Melbourne and Brisbane, and Brisbane can't see anyone.


If the Administrator in Melbourne presses the AutoSync button, it will examine the remote servers list in the Adelaide office, and find an entry for Perth. It adds Perth to the Melbourne list. It then examines the Sydney server, and finds there is an entry for Brisbane, so it also adds Brisbane to the Melbourne list. It then examines the Perth and Brisbane lists to see if there are any additional servers connected to them. Once no more servers can be added, it then updates ALL 5 databases with a complete list of all other servers. The result is pictured below...



NOTE: The databases themselves remain as separate entities THEY ARE NOT REPLICATED. To examine the status of a user in a different office, the users need to 'connect' to that database, and return to their 'Home' database afterwards.


Replication of the complete database is not economical with regards to Network Bandwidth, and generally, because the data is updated so frequently, if there were replicated copies, they would be out-of-date in a matter of moments. Keeping the databases separate eliminates these problems.