|
|
|
|
|
|
|
|
|
|
- Overview
- Functions for managing the assisted replication
- Functions for managing the universal replication
- Functions for managing log-based replication
- Functions used to handle the replication of HFSQL servers
Different types of replication are proposed: - the assisted replication. This replication mode is used to easily define the records to replicate via ReplicEdit. Then, the records are replicated by ReplicSynchro. This replication mode uses the universal replication. Specific WLanguage functions are used to handle the replications.
The assisted universal replication is available for the iOS and Android applications. For more details, see Replication of mobile data (Android or iOS). - the universal replication. The purpose of universal replication is to keep several databases synchronized. These databases can have different types (HFSQL, Oracle, ...). Universal replication uses a centralized model. This means that all databases are synchronized with a master database. Then, the master database reflect the changes in the other databases. Several WLanguage functions are used to implement the universal replication.
- log-based replication. Log-based replication uses logs to keep the remote HFSQL databases up to date. Several WLanguage functions are used to implement log-based replication. You can also use WDReplic.
- the replication between HFSQL servers. This replication mode is used to update the data found on HFSQL servers linked 2 by 2.
Functions for managing the assisted replication The following functions are used to implement the assisted universal replication (replication created from ReplicEdit):
| | | ReplicDeleteSubscription | Deletes the subscription of a replication on the replication server. | | ReplicInfo | Returns information about a replication. | | ReplicInitialize | Initializes or reinitializes a replication defined by the replication editor (ReplicEdit). | | ReplicOpen | Opens a replication in direct mode or with a replication server. | | ReplicSynchronize | Synchronizes the data corresponding to a replication. |
Functions for managing the universal replication The following functions are used to implement a universal replication. For more details, see Implementing universal replication.
| | | HCreateMasterReplica | Creates the description file of a Master Replica (logged replication or universal replication). | | HCreateMovableReplica | Creates a movable replication. | | HCreateSubscriberReplica | Creates the description file of a subscriber replica. | | HRecreateSubscriberReplica | Recreates the subscriber replica description file (universal replication only) based on the information of the master replica (.rpm and .syn files). | | Adds a data file to a universal replication. | | HRplDeclareLink | Declares a (1, 1) (0, n) link between two tables. | | HRplFilterProcedure | Defines the WLanguage procedure that will be called whenever a replication operation is performed on a specific file. | | HRplManageFile | Defines the options used for the universal replication of a file: - the replication direction.
- the management mode of conflicts.
| | HRplManageItem | Specifies the replication options for an item: the item can be replicated or not. | | HRplPass | Sets the passwords used to protect the universal replication files. | | HSetReplication | Temporarily disables (or re-enables) the replication. | | HSynchronizeReplica | Synchronizes master and subscriber replicas: operations performed on one replica are transferred to the other. |
Functions for managing log-based replication Functions used to handle the replication of HFSQL servers The functions below are used to implement a replication between 2 HFSQL servers. For more details, see Programming a replication of HFSQL servers.
| | | HRSAddConfig | Adds a replication between two HFSQL server onto the master server. | | HRSDeleteConfig | Deletes a replication between two HFSQL servers. | | HRSExecute | Immediately execute periodic replication between HFSQL servers: replication is triggered ahead of schedule. | | HRSIgnoreError | Ignores errors so that replication between HFSQL servers can continue to run. | | HRSInfo | Reads the replication configuration for an HFSQL server that takes part in one or more replications. | | HRSInit | Configures an HFSQL server in order for this server to be a master server or a subscriber server for a replication between HFSQL servers. | | HRSListConfig | Lists the replications available on a master HFSQL server. | | HRSModifyConfig | Modifies some parameters of an existing replication between two HFSQL servers. | | HRSRenameServer | Changes the DNS name of the replication server if it has a new name. | | Transforms a Spare server into an HFSQL server. This makes it possible to delete replications of a spare server so that it can be used again. For example, this function can be used in the case of a master server that becomes unreachable. This function should only be used in an emergency. Attention This function is only available from version 2025 Update 1. | | HRSWaitForDataProcess | Waits for: - the replication data on the master server to be sent to the subscriber server.
- the replication data received on the subscriber server to be entirely applied.
|
The replication between HFSQL servers is also using the following type of data:
| | | hRSConfig | The hRSConfig type is used to define the advanced characteristics of a replication between 2 HFSQL servers. |
Related Examples:
|
Training (WINDEV): WD Universal Replication
[ + ] This examples explains how to use the universal replication to synchronize data of different sites. The universal replication is used to synchronize the data of a site (master site) with the same data of one or more replicated sites (subscriber sites). The data structures are identical on each site but they can be exploited via different data managers. HFSQL Classic and Access will be used in this example. The example presents the processes that must be included in your applications to allow the user, via a simple action (menu, button, ...), to: - create a master replica, - create one or more subscriber replicas, - see and modify the data of these replicas, - export the created or modified data to a site (portable replica), - import the created or modified data into another site...
|
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|