Installation guide

4.2.1 - Auto Sync settings
Settings Description
On
When saving a profile when AutoSync is ON, edited on any of the Administration Consoles, the
profiles are automatically published to all managers connected to the same database. Changes are
reflected immediately on all devices currently using this profile. If the client is busy, changes are
reflected when displaying the Session Logon/Main Form. All the devices across all the managers
connected to this database share all the connector profiles.
Note: You cannot choose a connector profile selectively to be shared across manager/devices
(either you share all or none).
Important: The first Administration Console that you turn on becomes the master to start with.
Ensure that this setting is turned on only on a single Administration Console
Once Auto Sync is set to On, you can save the profile (service/connector) from any Administration
Console. That is, the profiles currently on the administering manager override any existing profiles across
all managers. This means that in the database, all the connector profiles are shared among all the managers
(instead of duplicating the profiles).
Off When you enable the Auto Sync function, you share the configuration data for the services, connector
profiles, and connector settings with all ShareScan managers in the current database. At any point of time if
you choose not to share the profiles across managers, you can uncheck the Auto Sync feature that
duplicates the profiles across managers and breaks the share.
Note: Existing settings are now lost. You can backup your database before enabling Auto Sync to
save existing settings.
For example, if there are two Administration Consoles running (pointed to the same database)
and if you turn Auto Sync on from Admin 1 and go to Admin 2 and try to save any profile, the
following message occurs:
A new profile has been detected and the AdminConsole has to reload before saving any
changes.
The changes made prior to the re-load are lost. At this point, the Administration Console reloads
the new data (which was saved from Admin 1). You can now make changes and save it back.
Note: The consequence of the previous behavior is that the concurrent editing of the profiles is,
even if it is not prohibited, not encouraged. While managing the same system with two instances
of the Administration Console concurrently from two different workstations is possible, it is not
recommended, mainly because there are many pieces of information that are displayed in the
Administration Console, but not refreshed immediately when the data is changed in the
underlying database by another Administration Console.