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 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. |
EP Configuration Helper | cnxepcfg_64 | connx/replicator/producer | the EP (libcnxepada_64) | connx/replicator/log/ EP_CONFIG.log | Invoked by the first replication enabled nucleus to be started and stays up until the last replication enabled nucleus is shut down. This process is a helper of the EP and is not the actual EP. The EP communicates with this process via TCP/IP on port 9207. |
CONNX Event Producer (EP) | libcnxepada_64.so* | connx/replicator/producer | shared library loaded into the Adabas nucleus process space | connx/replicator/log/ EP_<dbid>.log | The EP is shared library and not a stand alone process. It is loaded by the Adabas nucleus when the nucleus has been enabled for replication. The EP is responsible for starting the cnxepcfg_64helper process. |
Component Name | Process Name | Location | Invoked by | Log File | Comments |
CONNX Listener | cnxrun | connx/ | connxserver script in the connx directory | connx/cnxrun.log | The Adabas Data Server is made up of a Listener and Server component. cnxrun is the listener component |
CONNX Server | cnxadaC0 | connx/ | cnxrun | connx/cnxrun.log | A separate cnxadaC0 process is started for each connection made to Adabas from a CONNX client. The number of running cnxadaC0 process will be dependant on the number of active connections to the database. |
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. |
EP Configuration Helper | cnxepcfg.exe | c:\connx32\replication\producer | the EP | c:\connx32\replication\log\ EP_CONFIG.log | Invoked by the first replication enabled nucleus to be started and stays up until the last replication enabled nucleus is shut down. This process is a helper of the EP and is not the actual EP. The EP communicates with this process via TCP/IP on port 9207. |
CONNX Event Producer (EP) | cnxepada64.dll | c:\connx32\replication\producer | shared library loaded into the Adabas nucleus process space | c:\connx32\replication\log\ EP_<dbid>.log | The EP is shared library and not a stand alone process. It is loaded by the Adabas nucleus when the nucleus has been enabled for replication. The EP is responsible for starting the cnxepcfg helper process. |
Component Name | Process Name | Location | Invoked by | Log File | Comments |
Enterprise Server Service (CONNX Listener) | cnxremote.exe | c:\connx32\cnxremote\bin | Windows Service | c:\connx32\cnxremote.log | The Adabas Data Server is made up of a Listener and Server component. cnxremote is the listener component on Windows |
CONNX Server | cnxadabas.dll | c:\windows\system32 | cnxremote or loaded directly into CONNX client depending on configuration | c:\connx32\cnxremote.log | A separate server thread is started for each connection made to Adabas from a CONNX client. The number of threads will be dependant on the number of active connections to the database. |