The entirety of this Web site is copyright © 2007, ACI
Worldwide, Inc.
|
|
|
|
HotSync is an integral part of ASx that allows the solution to
be installed in a load-sharing, multi-node configuration, while still maintaining
total data integrity at all times. HotSync provides synchronization and recovery
of data between nodes regardless of the hardware, operating system or underlying
database being used. Each node can be a primary server and as such will process
transactions under normal circumstances. Hence, the concept of a back-up server
need not be considered unless a customer prefers, since all nodes are categorized
as "live". The transaction load can be distributed between nodes and shared in a
predefined manner. Should a node fail or the connection to a node be broken, then
transactions can be transparently and immediately rerouted to other still active
nodes. When the failed node is returned to service, the data is then automatically
re-synchronized between the nodes. The computers that represent the node can reside
in different data centers and as such can be distributed to provide a very high
level of business contingency for any organization. The distance between data centers
is not a problem so long as there is sufficient network bandwidth between the locations
to support the required transaction volumes.
The major benefits associated with HotSync are fully discussed in the HotSync article
that can be viewed by selecting the Further Information option from the menu.
|
Primary/Secondary Mode
|
In a primary/secondary configuration, secondary ASx does not receive
transactions unless primary ASx becomes unusable. (N.B. This is not a load sharing
configuration.)
|
Primary ASx updates the secondary ASx database with critical operational
data. Should the communications with secondary ASx be lost for any reason, the critical
data is written to a local store and forward queue. The secondary ASx database is
re-synchronized when communications are re-established.
Should primary ASx become unusable for any reason, the transactions will be immediately
re-routed to secondary ASx.
|
Secondary ASx shall continue processing until primary becomes available.
The critical data is stored in the secondary ASx store and forward queue. When primary
ASx becomes available once more, the critical data stored by secondary ASx shall
be used to resynchronize the primary ASx database.
|
Load-shared Mode
|
In a load-shared configuration, both primary and secondary ASx
receive transactions.
|
Should either ASx system become unusable, all transactions are
routed to the remaining functional ASx system. As with the primary/secondary configuration,
critical data is stored and then forwarded when the unusable ASx system is brought
back on-line. Transactions can be routed to the relevant ASx systems in a user defined
fashion, for example, in a round-robin manner or based upon device type, merchant
or any other category.
|
|
|
|
|
