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, insuring that no transaction is lost in the event of a software failure. It then attempts to deliver the message. RepConnector does not signal an acknowledgment to Replication Server until it successfully delivers the message to the specified messaging system. This process guarantees that no transactions are skipped and deliveries are sequential.
