Syncing with Adabas
When doing Adabas to Adabas replication, an Adabas to Adabas license must be present for the Adabas nucleus and InstantdbSync. For further information on how to install and configure Adabas for Adabas to Adabas replication, please refer to the appropriate Adabas documentation.
The following diagram illustrates the InstantdbSync architecture when doing Adabas to Adabas replication:
This diagram shows InstantdbSync in an Adabas to Adabas replication environment.
In this environment, the data is replicated directly from the source Adabas nucleus to the target Adabas nucleus. The following components are required:

Component | Description
Adabas v6.3.1 (or above) for Open Systems | Adabas to Adabas replication requires Adabas version 6.3.1 and above. To use this feature, you must have an A2A license for both the nucleus and InstantdbSync. Once replications are deployed and the initial state process has completed, data is replicated from the source nucleus directly to the target nucleus. The replication server is integrated into the nucleus and is only shown separately in the above diagram for illustrative purposes.
Entire Net-work | Adabas to Adabas InstantdbSync uses standard Adabas calls to transfer data between the source and target nuclei, so if the target database is on a physically different machine, Entire Net-work is required.
Replication Administrator | The InstantdbSync graphical user interface is written in C#.NET and can only run in a Windows environment. Using the Replication Administrator, you can define new replications in less than a minute.
Event Producer (EP) | The Event Producer is a DLL (shared library) that is loaded by the Adabas nucleus. This is the component that communicates with the nucleus to tell it which files to replicate, as well as to get status on current replications. Status information is sent to the Replication Administrator, where it is displayed.
Message Queue (CNXMQ) | The CONNX Message Queue stores messages so the system can recover if communication is lost between components. If the Event Consumer or Controller components shut down for any reason (such as power outages or system reboots), the Message Queue ensures full recoverability when the components are brought back online again. In an Adabas to Adabas configuration, this component is used for passing communication messages between the EP, the controller, and the Replication Administrator.
Controller | The Controller manages communicating deploy requests as well as status between the EP and the Replication Administrator. It also handles calling the Adabas Utility ADABCK to perform the initial state process.
CONNX SQL Engine | The Controller uses the CONNX SQL Engine to perform "initial states." An "initial state" moves all the data from a source Adabas file to a target table for the first time. The CONNX SQL Engine uses the Adabas utility ADABCK to extract the data from the source database and to load it in the target database. Data is extracted from the source database by ADABCK where it is passed to the CONNX Data Server running on that system. The Data Server then passes the data via TCP/IP to the CONNX SQL Engine which in turn sends it via another TCP/IP connection to a second CONNX Data Server running on the target system. From there the data is passed to ADABCK where it is loaded into the target database. When replicating from Adabas to Adabas, the CONNX SQL Engine is not used to convert the data to SQL as it is when replicating from Adabas to a Relational database. Instead, the data is transferred directly between the source Adabas nucleus and the target Adabas nucleus in the native format.
Designer Data Dictionary | The Event Replication Designer requires a data dictionary containing the Adabas nucleus' connection information.