For network connections, Mirror Replication Agent uses the Java Database Connectivity (JDBC) protocol, as implemented by the Sybase JDBC driver, jConnect™ for JDBC™.
Each Mirror Replication Agent instance uses a single instance of jConnect for JDBC to communicate with all Open Client™ and Open Server™ applications, including the Adaptive Server® Enterprise primary data server.
Mirror Replication Agent uses file or device I/O for access
to the mirror log devices.
Figure 1-4 shows how Mirror Replication Agent communicates with other Mirror Activator system components.
Figure 1-4: Mirror Replication Agent communication
During normal operation (while replicating transactions), Mirror Replication Agent maintains continuous connections with the following Mirror Activator system components:
Primary data server
Replication Server
Mirror Replication Agent maintains a connection with the primary data server to reserve the logscan context, which gives it control of the secondary truncation point in the primary database transaction log.
Depending on its configuration, Mirror Replication Agent may occasionally connect to the RSSD to retrieve replication definitions, which it can use to process the replicated transactions more efficiently.
