Checkpoint Systems Inc. FISOCKS Manual De Usuario
1-4
I L S 2 . 5 U s e r G u i d e
Single Server, Multi-Branch Architecture
New with this release, ILS Version 3.0 enables a single server to manage the circulation of
not only its only branch but multiple remote branches as well, granting the administrator
greater power and ease to manage the entire system. In this scenario, Local Security
Controllers are used to assist the Application Server.
not only its only branch but multiple remote branches as well, granting the administrator
greater power and ease to manage the entire system. In this scenario, Local Security
Controllers are used to assist the Application Server.
The Local Security Controller (LSC) is a combination hardware and software solution for
a multi-branch ILS deployment. The LSC assists the Intelligent Library Controller in
maintaining the response speed of Exit Interrogators, managing the connection between
the Exit Interrogators at the branch and the remote Application Server to provide
maximum caching performance. The LSC also enables the intelligent sensors to operate
(with limitations) if the main server is down. This scenario is normally used with libraries
containing up to 20 branches.
a multi-branch ILS deployment. The LSC assists the Intelligent Library Controller in
maintaining the response speed of Exit Interrogators, managing the connection between
the Exit Interrogators at the branch and the remote Application Server to provide
maximum caching performance. The LSC also enables the intelligent sensors to operate
(with limitations) if the main server is down. This scenario is normally used with libraries
containing up to 20 branches.
Peer-to-Peer Communication
New with this release is the ability to run a library’s security and inventory management
system from any ILS Server. This enables a granular redundant system that is crash
resistant because each node can run the entire system, as well as, holding a complete copy
of the checkout cache database at any time.
system from any ILS Server. This enables a granular redundant system that is crash
resistant because each node can run the entire system, as well as, holding a complete copy
of the checkout cache database at any time.
The main Application Server communicates to each node (peer server) the latest
circulation database in a configurable matter of time (from seconds to hours or even
daily); meaning circulation records are nearly always up to date. This means that exit gates
(intelligent sensors) are updated throughout the day at every branch. This allows a patron
to walk to another branch (for example on a college campus) and their library material will
respond with the correct check-in or checkout status. This scenario is normally used for
libraries containing more than 20 branches.
circulation database in a configurable matter of time (from seconds to hours or even
daily); meaning circulation records are nearly always up to date. This means that exit gates
(intelligent sensors) are updated throughout the day at every branch. This allows a patron
to walk to another branch (for example on a college campus) and their library material will
respond with the correct check-in or checkout status. This scenario is normally used for
libraries containing more than 20 branches.