Replication Components

The following is a description of the InstantdbSync components:

 

UNIX/Linux

 

Component Name

Process Name

Location

Invoked by

Log File

Comments

CONNX Message Queue

cnxmq

connx/replicator/common

mqserver script in the connx directory

connx/replicator/log/

cnxmq_run.log

A message queue needs to be running on each system that contains replication components.

CONNX Replication Controller

cnxcontrol

connx/replicator/consumer

eventserver script in the connx directory

connx/replicator/log/

CTRL.log

 

CONNX Event Consumer (EC)

cnxrep

connx/replicator/consumer

Controller (cnxcontrol)

connx/replicator/log/

EC_<source>_<target>.log

Used for moving transactions from the message queue to the target database.

 

Windows

 

Component Name

Process Name

Location

Invoked by

Log File

Comments

CONNX Message Queue

cnxmq.exe

c:\connx32\replication\common

Windows Service

c:\connx32\replication\log\

cnxmq_run.log

A message queue needs to be running on each system that contains replication components.

CONNX Replication Controller

cnxcontrol.exe

c:\connx32\replication\consumer

Windows Service

c:\connx32\replication\log\

CTRL.log

 

CONNX Event Consumer (EC)

cnxrep.exe

c:\connx32\replication\consumer

 

cnxcontrol.exe

c:\connx32\replication\log\

EC_<source>_<target>.log

Used only with replications that have a relational target.  Is not used with Adabas to Adabas replication.  There will be one cnxrep process running for each source database/target database combination.

CONNX Event Producer (EP)

cnxepsqlserver.exe

c:\connx32\replication\producer

 

cnxeprun.exe

c:\connx32\replication\log\

EP_<dbid>.log

 

The EP is started by the EP listener.  There is one EP process for every source/target database combination..

CONNX Event Producer Listener

cnxeprun.exe

c:\connx32\replication\producer

Windows Service

c:\connx32\replication\log\
CNXEPLISTENER.log