Learn how RepAgent and other Replication Agents work with Replication Server to distribute transaction information to subscribing replicate databases
RepAgent logs in to Replication Server through an Open Client™ interface. It scans the transaction log, converts log records directly into LTL (Log Transfer Language) commands, and sends them to Replication Server as soon as they are logged—either in batches or one at a time. Replication Server then distributes the transaction information to subscribing replicate databases.
Replication Server has one RepAgent user thread for each primary database that it manages. Thus, Replication Server has one RepAgent user thread for each RepAgent. The RepAgent user thread verifies that RepAgent submissions are valid and writes them into the inbound stable queue for the database.