AYUDA EN LÍNEA
 WINDEVWEBDEV Y WINDEV MOBILE

Este contenido se ha traducido automáticamente.  Haga clic aquí  para ver la versión en inglés.
Ayuda / WLanguage / Administrar bases de datos / HFSQL / Gestión de la replicación / Replicación universal
  • Overview
  • Principle of the assisted universal replication
WINDEV
WindowsLinuxJavaReportes y ConsultasCódigo de Usuario (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Código Navegador
WINDEV Mobile
AndroidWidget Android iPhone/iPadIOS WidgetApple WatchMac Catalyst
Otros
Procedimientos almacenados
Overview
To easily establish the universal replication between the data of a remote application and a central database, WINDEV and WEBDEV allow you to:
  • create a replication via a replication editor (ReplicEdit). This editor is used to define the characteristics of a replication.
  • implement an automatic replication on the data of an application. The replication is directly performed by the end users via two tools:
    • ReplicSynchro, used to perform a replication.
    • ReplicAdmin, used to manage the replications.
    For more details, see Implementing an automatic assisted universal replication.
  • implement a programmed replication included in an application via WLanguage functions. These functions are used to handle a replication and to perform the synchronization.
    For more details, see Implementing a programmed assisted universal replication.
Remarks:
Principle of the assisted universal replication
The purpose of the assisted universal replication is to propose a quick replication for any type of application.
The assisted universal replication proposes the following modes of replication:
  • direct replication: replication is performed directly between the local base and the master base. This replication mode is recommended when a computer must connect to the local network for example. This replication mode requires no specific configuration.
  • replication per server: replication is performed via a replication server. The transfer of replicas is automatically managed.
Server-based replication can be implemented with immediate replication in which case data is synchronized immediately. The subscriber database sends the data to replicate, the replication is performed and the subscriber database retrieves the data to update. This operation can take quite a long time. This replication mode is recommended for a daily synchronization for instance (a salesperson synchronizes every evening with the office).
Server-based replication can be implemented with deferred replication In this case, data is synchronized as it is exchanged with the server. When the server receives the data to replicate, it automatically prepares the data to return. This data will be returned during the next synchronization. This replication mode is recommended for a periodic synchronization for instance (whenever an order is placed).
Versión mínima requerida
  • Versión 12
Esta página también está disponible para…
Comentarios
Haga clic en [Agregar] para publicar un comentario

Última modificación: 27/03/2025

Señalar un error o enviar una sugerencia | Ayuda local