Logged replication

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Help

Logged replication

Overview

Implementing the logged replication with WDReplic

Implementing the logged replication by programming

Precaution

See also

Logged replication

Available only with this kind of connection

Overview

The replication is the operation allowing you to keep updated remote databases of identical structures on which several operations are performed. The operations performed on each one of the databases are applied to all the other databases.

See The replication for more details.

WINDEV and WEBDEV propose two methods for implementing the logged replication:

Using WDReplic. In this case, no specific programming is required. All you have to do is configure the different replication options. This tool (and the necessary configuration files) will have to be installed along with the databases to replicate.
Using the WLanguage functions. In this case, the management of the replication will be performed in the application via specific options. These options will use the WLanguage functions for implementing the replication.

Remark: The logged replication is not available in HFSQL Client/Server. We recommend that you use the universal replication.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

Implementing the logged replication with WDReplic

The steps

To implement the logged replication with WDREPLIC, you must:

Modify the analysis (see Modifying the analysis to support logged replication for more details).
Create the executable (for a WINDEV application), then the setup procedure.
Remark: When creating the setup procedure, don't forget to add WDReplic to the setup program.
Install the application (and WDREPLIC) on the master and subscriber sites. The application setup also includes:
- WDReplic if the replication is performed with this tool
- an automatic update of the data files. This update is used to log (if necessary) and to replicate the data files. If the files were already logged, the existing logs are cleared.
  Reminder: To implement the replication, the data files must have an identical structure (analysis) on all the computers (master computer and subscriber computers).
Configure WDReplic on the master computer.
Install the files required by WDReplic on the subscriber computers.

See Help about WDReplic for more details.

Important: implementation conditions

Implementing the logged replication in an application is a major operation.

We recommend that you respect some basic rules.

For each file in replication, we recommend that you use a singe unique key in your files. This unique key must be an "Automatic 8-byte identifier".

See Logged replication: Modifying the analysis for more details.

Implementing the logged replication by programming

To implement the logged replication by programming, you must:

Modify the analysis (see Logged replication: Modifying the analysis for more details).
Modify the application to manage the replication with the WLanguage functions. See Logged replication: Program in WLanguage for more details
Create the executable (for a WINDEV application) and the setup program.
Install the application on the master and subscriber sites. The application setup must include an automatic update of the data files. This update is used to log (if necessary) and to configure the data files for the replication. If the files were already logged, the existing logs are cleared.

Reminder: To implement the logged replication, the data files must have an identical structure (analysis) on all the computers (master computer and subscriber computers).

Important: implementation conditions

Implementing the logged replication in an application is a major operation.

We recommend that you respect some basic rules.

For each file in replication, we recommend that you use a singe unique key in your files. This unique key must be an "Automatic 8-byte identifier".

See Logged replication: Modifying the analysis for more details.

Precaution

Moving the data files manually

Caution: To move the data files manually, you must comply with the following rules:

Update all the replicas on the relevant computers.
Copy the data files to the relevant computers.
Save then delete the following files:
- all the log files (".JNL" files).
- all the files of identification tables ("JournalIdentification.*" files).
- all the files of operation tables ("JournalOpération.*" files).