Bi-directional requirements: system journal replication - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

To configure system journal replication processes to support bi-directional flow of objects, you need the following:

  • A data group (DG) definition is unique to its three part name (Name, System 1, System 2). This allows two DG definitions to be configured to share the same data group name with system 1 and system 2 reversed. You must specify both DG definitions to use the same Data source (DTASRC) parameter value. For example, in the following table both DG definitions use DataGroup1 as the data group name and both specify *SYS1 (System 1) as their DTASRC. This results in one DG definition that replicates from A to B, while the other replicates from B to A.

    Example of DG Definitions with reversed system names for bi-directional replication.

    Data Group Name

    System 1

    System 2

    DataGroup1

    A

    B

    DataGroup1

    B

    A

  • Each data group definition should specify *NO for the Allow to be switched (ALWSWT) parameter.

Note: In system journal replication, MIMIX does not support simultaneous updates to the same object on multiple systems and does not support conflict resolution for objects. Once an object is replicated to a target system, system journal replication processes prevent looping by not allowing the same object, regardless of name mapping, to be replicated back to its original source system.