When routing replication events to messaging systems, RepConnector works with Replication Server to guarantee delivery. When RepConnector receives a message from Replication Server, it writes the message transaction ID to a file, ensuring that no transaction is lost in the event of a software failure. RepConnector then attempts to deliver the message. RepConnector does not send an acknowledgment to Replication Server until the message is successfully delivered to the specified messaging system. This process guarantees that no transactions are skipped, and that deliveries are sequential.
