Overview
Replication in
LinkSOFT is a vital module designed to ensure seamless data synchronisation
across multiple company locations, such as a head office and various branches.
It enables businesses to maintain consistent inventory, sales, and customer data
across their network, providing crucial support for distributed operations. This
module is essential for real-time information flow, operational continuity even
during network outages, and robust data management in complex business
environments.
Here are the key features and functionalities of the Replication module:
- Core Functionality: Replication facilitates the automatic
synchronisation of data between a head office and multiple branch servers, as
well as standalone stations. It is designed to ensure operational continuity,
allowing branches to function even if central server connectivity is lost, as
all replication is automated with no user intervention required.
- Key Components: The module is structured around several
components: Servers (defining SQL database servers with
unique names, physical addresses, database names, and unique two-character
masks for transaction IDs), Server Connections,
Server Topology (providing a visual representation of the
replication network), Rules (controlling data flow),
Import/Export Data (for manual synchronisation during
extended outages), and a Queue Monitor (for tracking data
transfer and managing failed items).
- Setup and Configuration: Proper setup requires all
servers (Head Office, Branch, and Standalone) to have synchronised time (using
UTC). Server specifications and network bandwidth are crucial for smooth data
flow. The process involves installing the LinkSOFT application, setting up the
Head Office with parent links, and configuring branch servers with child
links. The previous "Replication Server Mode" has been reviewed and removed,
simplifying configuration by making standalone functionality equivalent to the
standard parent/child setup.
- Data Flow Rules: Replication rules are pivotal for
controlling data transmission. These rules can be configured to restrict
specific data types from flowing to all branches, ensuring only relevant data
reaches designated locations. For example, shift details are generally not
replicated to other branches to prevent discrepancies, and
POSCASH
customer details are not replicated by default.
Conversely, specific tables like LT_INV_InventoryBarcode
are
explicitly included to ensure essential barcode information synchronises
across locations, and the replication of Inventory List records is allowed so
branches can review stock levels.
- Performance and Reliability: Significant efforts have
been made to enhance replication performance and prevent data corruption,
particularly concerning primary key issues. This includes fine-tuning
processes, reducing data load for high-volume transactions, and ensuring
consistency across replicated objects. Custom triggers are dynamically built
for efficient data handling, and manual replication jobs have been migrated to
automated processes to improve efficiency, such as correctly handling stock
movement updates from branches to the head office.
- Troubleshooting and Monitoring: Tools like "Compare Data"
allow users to identify any "Additional," "Missing," or "Different" data
between head office and branch databases. The Queue Monitor provides detailed
insights into data transfer queues, enabling administrators to re-submit or
delete failed items after a certain number of retry attempts. Comprehensive
error logging and improved handling of transmission batches contribute to
overall system stability.
- Licensing and Access: Access to Replication features,
including its dedicated menus and processes, is strictly controlled by a
specific license based on server connections. If the necessary license is not
active, these functionalities are automatically hidden from the user
interface, ensuring controlled and secure management of this critical data
synchronisation module.
- Technical Modernisation: The module has undergone
technical modernisation, moving towards using the LinkSOFT API for data
transmission between databases, thereby replacing older methods that relied on
"Linked Servers." This approach enhances the efficiency and reliability of
data exchange within the LinkSOFT ecosystem.
The replication module can be used to
achieve data synchronization for the
following:
-
Head Office to
Branch
-
Branch Server to Stand-Alone POS
Machines (Fail Safe)
Configure the "LinkSOFT API" in menu
"Integration -> Integration Setup" to send and receive replication
data.
The following
functions are available:
Important Notes:
-
All Branch and Head Office servers must have time
synchronised
-
All Standalone servers must have time
synchronised
-
The system uses UTC time for replication so the time
zone does not matter, however the local time must be correct. Synchronise with
Internet Time.
-
If you decide to setup REPLICATION between servers,
the server specifications and interconnection bandwidth must be correctly
chosen in order for data to flow smoothly. Line stability is also an important
factor.
-
When setting up STAND ALONE mode, the stations should
connect to the Branch server under normal operation. The stations will switch
to Fail Save mode automatically if there is a problem with the main
server
-
An administrator should check replication logs to
resolve any conflicts
Also See:
-
-