|
|
|
|
|
|
|
|
|
|
- Properties specific to hRSConfig variables
- Single-channel unidirectional replication
- Functions that use the hRSConfig type
hRSConfig (Variable type) In french: hRSConfig
 Available only with this kind of connection
The hRSConfig type is used to define the advanced characteristics of a replication between 2 HFSQL servers. The characteristics of this replication can be defined and modified using various WLanguage properties. Note: For more details on the declaration of this type of variable and the use of WLanguage properties, see Declaring a variable. Cnx is Connection
ConfigRéplication1 is hRSConfig
ConfigRéplication1.Server = "atlas.masociete.com:4996"
Add(ConfigRéplication1.File, "Mabase")
Add(ConfigRéplication1.File, "-Mabase\Monfichier.fic")
HRSAddConfig(Cnx, ConfigRéplication1, hrsNoCopy)
ConfigRéplication is hRSConfig
ConfigRéplication.Bidirectional = True
ConfigRéplication.Server = gstServeurRéplication.sPoste + ":" + gstServeurRéplication.nPortRPL
ConfigRéplication.Password = gstServeurRéplication.sPwdRPL
Add(ConfigRéplication.File, "*")
HRSAddConfig(cnxConnexionCS, ConfigRéplication, hrsCopy)
Properties Properties specific to hRSConfig variables The following properties can be used to handle a replication between HFSQL servers:
| | | | Property name | Type used | Effect |
|---|
| Bidirectional | Boolean | - True if replication is to take place in both directions: replication will be bi-directional.
- False otherwise (default): unidirectional replication.
| | Description | Character string | Description of replication. | | File | Array of strings | List of elements to replicate. The elements to replicate can correspond to: - a database,
- a data file,
- a data file to exclude from the replication. In this case, the name of the file must be prefixed by "-" (minus).
- a server. In this case, the File property must correspond to "*" (see example).
| | Identifier | entier | Used to identify the replication handled. This property is read-only. | | IdentifierOpposed | entier | In the case of bidirectional replication, corresponds to the replication identifier from the opposite server to the replicated server.. This property is read-only. | | Initialization | entier | Used to follow the evolution of the initial copy of replicated elements from the connection server (master server) to the other server (subscriber server) during a copy in background task (HRSAddConfig associated with the hrsCopyBackgroundTask constant). If this property: - is included between 0 and 1000, the replication is currently added.
- is set to 1000, the replication was added.
- is not specified, the replication failed to be added.
This property is read-only. | | ModificationConflictResolution | Integer constant | Method for solving the conflicts: - hrcmPlusPriority (default value): In the event of 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.
- hrcmPlusRécent: In the event of a conflict, the most recent element takes precedence.
Caution: This method requires synchronization of the clocks on the different servers. - hrcmProcedureWithModifiedRubrics: When a conflict occurs, a stored procedure is launched (defined by the property ProcedureResolutionConflictModification). In this procedure, only the modified items will be accessible.
- hrcmProcedureAllRubrics: When a conflict occurs, a stored procedure is launched (defined by the property ProcedureResolveConflictModification).. In this procedure, all the items found in the record will be accessible.
| | Password | Character string or Secret string | Password specific to the replication. This password must correspond to the password specified in HRSInit used on the subscriber server.
 New in version 2025Secret strings: If you use the secret string vault, the type of secret string used for this parameter must be "ANSI or Unicode string". To learn more about secret strings and how to use the vault, see Secret string vault. This property is available in write mode. | | ProcedureForModificationConflictResolution | Character string | Name of the stored procedure to be used if the conflict resolution method (ModificationConflictResolution) corresponds to the hmcrProcedureWithModifiedItems or hmcrProcedureAllItems constants. This stored procedure must return: - the constant opReessayer constant to validate replication of the modification,
- the constant opAnnuler constant to cancel replication of the modification.
This stored procedure must be found in the replicated database on the subscriber server. | | Scheduling | hScheduling variable | Replication period. If all the members of the hScheduling variable are left empty, it will be a replication in streaming. | | Server | Character string | Target server of the replication. This server is identified by: - its DNS name or its IP address.
- the replication port (4996 by default).
If the port differs from the default port, the following syntax must be used to specify it: "<Server name>:<Replication port>". This port must correspond to the port specified in HRSInit used on the subscriber server. | New in version 2025Single-channel | Boolean | - True if replication is to be performed in "single-channel" mode.
- False otherwise.
This property is only taken into account if the replication is bidirectional (property Bidirectional property = True). For more details, see the Remarks. Note: Non-single-channel replication cannot be changed to single-channel replication. Note: This property is only available from version 2025 Update 1. | | Spare | Boolean | - True to perform a replication in spare mode,
- False otherwise.
Note: This property is incompatible with the Bidirectionalproperty. . |
Remarks New in version 2025Single-channel unidirectional replication By default, replication uses one communication channel and one replication channel. Single-channel replication opens a single communication channel on the server receiving the replication. Replication is only possible via the communication channel. In this case, replication must be initiated by the server receiving the data. Example: Replication with a laptop. - The laptop creates the replication.
- No communication ports must be open on the laptop.
- Replication will work with a dynamic IP address (that of the laptop).
Note: This feature is only available from version 2025 Update 1. Functions that use the hRSConfig type The following functions use hRSConfig variables: | | | HRSAddConfig | Adds a replication between two HFSQL server onto the master server. | | HRSDeleteConfig | Deletes a replication between two HFSQL servers. | | HRSIgnoreError | Ignores errors so that replication between HFSQL servers can continue to run. | | 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. |
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|