PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | French EN
  • Overview
  • Implementing a replication between HFSQL servers
  • Configuring a replication with the HFSQL Control Center
  • Defining the subscriber server from the HFSQL Control Center
  • Defining the master server from the HFSQL Control Center
  • Defining a replication on the master server
  • Managing the existing replications
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Managing the replications of HFSQL servers (Control Center)
HFSQL Client/ServerAvailable only with this kind of connection
Overview
The HFSQL Control Center is used to:
Reminder: The replication of HFSQL servers consists in replicating the data from server to server automatically. See HFSQL server replication for more details.
Caution: The replication of HFSQL servers must not be implemented without the agreement of the developer of the application. Indeed, implementing the replication between several HFSQL servers requires some adaptations in the application.
If these adaptations are not performed, the application may not operate properly and data may be lost.
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
Implementing a replication between HFSQL servers

Configuring a replication with the HFSQL Control Center

To configure a replication with the HFSQL Control Center:
  1. Define the subscriber server in the Control Center. The subscriber server will be the server that receives the replicated data.
  2. Define the master server in the Control Center. The master server will be server that replicates its data.
  3. Define the replication on the master server.
Remarks:
  • The user of the HFSQL Control Center must have the rights to "Create a replication between two HFSQL servers" in order to create and configure the replication between servers.
  • The communication between servers is authenticated. It is not encrypted.

Defining the subscriber server from the HFSQL Control Center

To define the subscriber server from the HFSQL Control Center:
  1. From the HFSQL Control Center, connect to the HFSQL server that will be the subscriber server.
  2. Double-click the HFSQL server in the treeview on the left.
  3. In the server tab, in the ribbon, click "Server configuration".
  4. In the list of possible configurations, select "Replication". You can configure the replication for the current server.
  5. Check "The server is subscriber or spare (will receive replicated data)".
    CCHF - Replication
  6. Specify the port for receiving the replicated data.
  7. Specify the password and the confirmed password for the replication.
  8. Specify the unique identifier of the HFSQL server (included between 1 and 32000).
  9. Specify the priority of the server.
    Remark: During a modification conflict, this number is used if the method for solving the conflict corresponds to a resolution by priority. The smaller the priority value defined for the server is, the higher the priority granted to the server will be.
  10. Validate.

Defining the master server from the HFSQL Control Center

To define the master server from the HFSQL Control Center:
  1. From the HFSQL Control Center, connect to the HFSQL server that will be the subscriber server.
  2. Double-click the HFSQL server in the treeview on the left.
  3. In the server tab, in the ribbon, click "Server configuration".
  4. In the list of possible configurations, select "Replication". You can configure the replication for the current server.
  5. Check "The server is master (will replicate its data)".
  6. Specify the unique identifier of the HFSQL server (included between 1 and 32000).
  7. Specify the priority of the server.
    Remark: During a modification conflict, this number is used if the method for solving the conflict corresponds to a resolution by priority. The smaller the priority value defined for the server is, the higher the priority granted to the server will be.
  8. Click the "Apply" button.

Defining a replication on the master server

To define a replication on the master server:
  1. If no replication has been defined, click the link "Click here to create a new server replication".
    If one or more replications have been defined, click "Add".
    The wizard for creating a replication starts.
  2. Specify the type of replication:
    • Unidirectional replication,
    • Versions 25 and later
      Spare replication,
      New in version 25
      Spare replication,
      Spare replication,
    • Bidirectional replication.
      For a bidirectional replication, the server will also be configured as subscriber. In this case, you must specify:
      • the port used to receive the replicated data.
      • the password for the replication. This password will be identical for the subscriber server.
  3. specify the destination of the replication (which means the characteristics of the subscriber server):
    • the DNS name or IP address of the subscriber server.
    • the replication port on the subscriber server.
    • the password for the replication to the subscriber server (for a unidirectional replication).
  4. Select the elements to replicate. You can replicate:
    • the entire content of the server,
    • a database,
    • a selection of databases or files.
    Remarks:
    • You can exclude certain files from the replication. If this option has been selected, the next step of the wizard allows you to select the elements to exclude.
    • If necessary, you can make an initial copy of the elements to replicate.
  5. Schedule the replication:
    • Periodic: the replication will be perfomed on a regular basis. A wizard allows you to define the periodicity.
    • Continuous mode: the replication will be performed continuously, whenever a modification is performed.
  6. In the case of a unidirectional or bidirectional replication, select the conflict resolution mode:
    • More recent: During a conflict, the more recent element has priority.
      Caution: This method requires a synchronization of the clock on the different servers. The date and time (to the second) of records is used for the comparison (YYYYMMDDHHMMSS). If two records in conflict strictly have the same date and time, the identifier of servers is used in order for the comparison to be deterministic.
    • Priority: During a conflict, only the priority value defined for the server is taken into account. The smaller the priority value defined for the server is, the higher the priority granted to the server will be.
    • Stored procedure with all the items: During a conflict, a stored procedure is started. In this procedure, all the items found in the record will be accessible. Specify the name of the stored procedure to use.
    • Stored procedure with the modified items: During a conflict, a stored procedure is started. In this procedure, only the modified items will be accessible. Specify the name of the stored procedure to use.
  7. Give a name to the replication and validate. The wizard for creating the replication is closed and the replication appears in the List of replications.
Managing the existing replications
If replications have been defined on the current HFSQL server, the HFSQL Control Center allows you to:
  • Add a new replication ("Add" button). In this case, the wizard for creating a replication is automatically started.
  • Modify a replication ("Modify" button). The replication description window appears. This window is used to modify the main characteristics of the replication. Some characteristics cannot be modified. In this case, you may have to delete the replication and re-create it.
    The following characteristics can be modified:
    • the mode for solving the conflicts ("General" tab). This option is only available for unidirectional and bidirectional replications.
    • the description of the replication ("General" tab).
    • the replicated elements ("Replicated elements" tab): Caution: you only have the ability to exclude elements from the replication.
    • the scheduling of the replication ("Scheduling" tab).
  • Delete a replication ("Delete" button). After confirmation, the configuration of the replication is deleted.
    Caution: The subscriber server must be accessible. If the subscriber server is not accessible, you have the ability to force the deletion. In this case:
    • the replication information will not be deleted from the subscriber server.
    • If the replication is bi-directional, the configuration will not be deleted from the inaccessible server. We advise you to perform this deletion from this server as well to avoid a useless memory consumption.
    Versions 25 and later
    In the case of a spare replication, when the replication is deleted, the subscriber server reverts to read/write mode. The data is not deleted from the subscriber server.
    New in version 25
    In the case of a spare replication, when the replication is deleted, the subscriber server reverts to read/write mode. The data is not deleted from the subscriber server.
    In the case of a spare replication, when the replication is deleted, the subscriber server reverts to read/write mode. The data is not deleted from the subscriber server.
  • Trigger a replication ("Trigger" button). This option is used to immediately trigger a programmed replication.
Minimum version required
  • Version 18
This page is also available for…
Comments
Click [Add] to post a comment