Based on very slow replication (SLOG piled up - 20 replications per second - unstable Reptor) of mass data from Adabas on the mainframe to Adabas on Windows, I would like to know the following:
Is the Adabas Event Replicator latency sensitive and what are acceptable latency thresholds to keep the application from backlogging significantly enough to cause the mainframe process to become unstable?
Does the Replicator employ any slow start methodology or other way to optimize network performance?
How does the Replicator handle lost data within the replication stream or lost/retransmitted TCP/UDP packets?
Considering the Replicator, can the data sent between the host and client be safely encrypted with IPSec?
Do you have other customers successfully using the Replicator over an IPSec VPN tunnel?
Replicator ARF 3.1.1