Bi-directional replication - Connect_CDC - connect_cdc_mimix_share - 5 - 5.8

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2023
First publish date
2003
ft:lastEdition
2023-09-27
ft:lastPublication
2023-09-27T18:12:55.651884

How do I set up bi-directional, that is, where two tables are kept exactly synchronized?

You can use bi-directional replication and protected collision resolution to set up a configuration where two tables are kept exactly synchronized.

In the Getting Started Guide and in previous Advanced User Guide topics, routing has been uni-directional, that is, from source to target(s) only. You can also define a bi-directional configuration, which allows user updates locally at both a source and a target server and where the server is defined as both a source and a target. No hierarchical relationship exists between the servers.

In a bi-directional distribution, Connect CDC assumes responsibility for detecting data collisions and either resolves them automatically or presents them for resolution as you specify.

 

Note: Bi-directional distribution is restricted to data replication. Neither Copy nor Synchronization can be used with bi-directional distribution patterns.

The principal tasks described in the section include: