Connection Shared by Replication Agent and ECDA

A single Replication Server connection can support both an ECDA gateway and a Replication Agent, because each of these components connects to the Replication Server on a different thread.

If you replicate information both into and out of the same database, having a common connection for both a database gateway and a Replication Agent can make the replication system network topology less resource intensive.

To create a Replication Server connection to a database that is both primary and replicate, you must define the connection to correctly support the ECDA database gateway, then configure the Replication Agent appropriately:

In the Replication Server, use the create connection command to define the server_name and database_name for the connection. The server_name value must match a configured service name in the ECDA.
In the Replication Agent, set the value of the rs_source_ds parameter to that server_name, and set the value of the rs_source_db parameter to the desired database_name.

To use direct-load materialization, you must have two database connections: one for incoming data and one for outgoing data. You must create the connection for incoming data—which is used by Replication Agent—using the appropriate connection profile (rs_rs_to_<replicate>_ra, where <replicate> is oracle, mssql, udb, or hanadb). Use a connection profile supporting normal replication to create the connection for outgoing data.