- This topic has 4 replies, 4 voices, and was last updated 15 years, 8 months ago by .
I am researching a new interface to an external repository. This repository will be outside of our four walls connected via a VPN. One of my concerns is that the when the external system’s interface is down, our engine will queue up transactions very quickly and likely impact other areas of our engine’s performance.
I am looking for ideas around a process that will at the time of external system disconnect, attempt to reconnect / resend some number of times then if no connection, the interface will switch from a TCPIP connection to a disk connection. At the time of the switch to disk mode, all of the recovery database queued transactions would be dumped to file first then continue to write all transactions to disk. This process would continue until manual intervention and a resend from the disk file could be performed.
Thanks in advanced for your ideas.
- The forum ‘Cloverleaf’ is closed to new topics and replies.