- 1 Creating a domain controller
- 2 Creating a domain
- 3 Configuring the domain for replication
- 4 Device loader installation
- 5 Starting the domain controller
- 6 Changing the replication configuration
- 7 Updating to version 9.6 or above
- 8 Connecting a new segment
- 9 Updating and transfiguring multiple domains into one
© Tillypad, 2008-2017
Table of Contents
Data replication is carried out between segments connected to the same domain. To ensure data replication, a segment must always be connected to the domain.
Data replication is carried out by the domain controller, which can be started on any computer that has access to all of the domain segment servers. The domain controller is started by the device controlled by the Domain controller starter software module. This device starts the 32-bit or 64-bit domain controller, depending on the operating system installed on a given computer. The domain controller uses its starter's parameters.
All replicated information is saved on the segment servers, while temporary data are stored in the RAM. For a higher replication speed, we recommend starting the domain controller on a computer with a lot of RAM and the 64-bit operating system. A multicore processor also speeds up the process.
After restart, the domain controller reads all data from the segments connected to its domain. Data received by the domain controller are immediately logged in the database of one of the connected segments.
The domain controller connects to the segments specified in its domain Segment parameters. The segment is identified by the AppServerHostName and AppServerPort parameters.
In the local initialisation file (ini file), the domain controller stores unique IDs (GUID) of the segments, to which it connects. If the local ini file does not contain the unique segment ID or if it does not match the actual ID, the information in the local ini file is updated.
When you connect to the segment, the domain controller verifies information about the domain, to which this segment belongs. If the domain of the domain controller is specified, everything is now ready for replication. If the domain is not specified, the domain controller writes the name of its domain. However, if a different domain is specified for the segment, the domain and segment are disconnected. Information about errors is saved in the error log. The next connection attempt is made 15 seconds after initial disconnection.
Setting up data replication between two segments (Central office and North branch)
In our example, the menu is managed from the central office of the venue. Changes in the menu must be applied to all branches via replication. Information about sales and stock movement must be sent from the branches to the central office.
To ensure this data exchange, you need to set up replication between two segments: Central office and North branch.
