A replication agent notifies Replication Server of actions in a primary database that must be copied to other databases. The replication agent reads the database transaction log and transfers log records for replicated tables and stored procedures to the Replication Server managing the database, which distributes the modifications to databases that subscribe to the data.
A replication agent is needed for every database that contains primary data and for every database where stored procedures that need to be replicated are executed. A database that contains replicated data and no stored procedures marked for replication does not require a replication agent.
Replication agents communicate with Replication Server by executing commands in Log Transfer Language (LTL).
See Chapter 5, “Creating a Replication Agent,” in the Replication Server Design Guide for more information about LTL commands.
The replication agent you use depends on the data servers in your replication system. Supported replication agents are:
RepAgent – for Adaptive Server data servers. RepAgent, a thread in Adaptive Server, is the replication agent described in this book.
Log Transfer Manager (LTM) – for SQL Server data servers. For information about the LTM, see and the Replication Server Administration Guide for Replication Server version 11.0.
Replication Agents for non-Sybase data servers:
SQL Anywhere
Lotus Notes
DB2
Oracle
IMS
VSAM
Refer to the Sybase documentation for these products for more information. Refer also to the release bulletin for your platform for a list of all supported replication agents for this version of Replication Server.
You also can create a replication agent to replicate data from a foreign data server. Refer to Chapter 5, “Creating a Replication Agent,” in the Replication Server Design Guide for details.
