Replication Agent captures transactions in the primary database then transfers them to Replication Server for distribution to replicate databases.
Replication Agent extends the capabilities of Replication Server by allowing non-Sybase database servers to be primary data servers in a Sybase replication system.
Replication Agent reads the primary database transaction log and generates Log Transfer Language (LTL). Replication Server uses LTL to process and distribute replicated transactions through a replication system.
Each Replication Server Option contains the Replication Agent suitable for a particular database platform:
Replication Agent for UDB – retrieves transactions from a DB2 Universal Database primary database running on UNIX and Microsoft Windows platforms.
Replication Agent for Microsoft SQL Server – retrieves transactions from a Microsoft SQL Server primary database.
Replication Agent for Oracle – retrieves transactions from an Oracle primary database.
Replication Agent runs as a standalone application, independent of the primary database server, the primary Replication Server, and other components of a replication system. However, for Oracle and Microsoft SQL Server, Replication Agent must have direct, physical access to the transaction log.
Replication Agent can reside on the same host machine as any other component of the replication system, or it can reside on a machine that is separate from other replication system components.
Replication Agent instances can be managed and monitored by Replication Manager (RM). In addition, you can completely configure, manage, and monitor a Replication Agent instance using any Open Client™ application (such as isql) that is capable of communicating with the Sybase Tabular Data Stream™ (TDS) protocol.
You can use the Sybase Central Replication Manager plug-in, which provides a replication system administrator the ability to develop, manage, and monitor a Sybase Replication environment.
For more information, see the documentation for Replication Agent.
