Replication with Infosphere CDC : Overview of IBM InfoSphere CDC replication between solidDB® servers : Architectural overview of IBM InfoSphere CDC Replication
  
Architectural overview of IBM InfoSphere CDC Replication
The following diagram illustrates the architecture and key components of a typical configuration of the IBM InfoSphere CDC Replication setup.
The roles and functions of the components are described below.
solidDB® — the source or target database which you replicate data to and from.
IBM InfoSphere CDC replication engine — a runtime instance of the IBM InfoSphere CDC engine for solidDB®. The IBM InfoSphere CDC instances can be installed on the same or a different node where the solidDB® servers are running.
IBM InfoSphere CDC Configuration tool — a GUI or console based tool used to configure and create IBM InfoSphere CDC instances. While configuring the instance, you supply the port number for communication with the rest of the IBM InfoSphere CDC system as well as login information to connect to the database.
IBM InfoSphere CDC Access Server — a process (running typically as a service or daemon) allowing users to access the IBM InfoSphere CDC instances and configure them. Different users can have access to different instances. During the Access Server installation you are requested to provide a port number and Administrator login information, to be used by the Management Console.
IBM InfoSphere CDC Management Console — an interactive application with a GUI that you can use to configure and monitor replication. It allows you to manage replication on various servers, specify replication parameters, and initiate refresh and mirroring operations from a client workstation.
You start using the Management Console by creating datastores in the Access Manager perspective. A datastore is a logical entity of a database and the related IBM InfoSphere CDC instance. Using the datastores defined, you can set up subscriptions that embody data replication from one datastore to another.
There are three types of datastores: source, target, and dual. Dual datastore can participate in subscriptions as both a source and target. If a replica is meant to be read-only in the frontend data server, a single upload subscription is defined.
After you have finished setting up replication, the Management Console can be closed on the client workstation without affecting active data replication activities between source and target servers. Management Console also includes an event log and a monitor. The event log allows you to examine generated IBM InfoSphere CDC event messages. The monitor provides the necessary support to continuously monitor replication operations and latency. Diagrams depicting components of your replication configuration are constructed through direct manipulation of graphical objects. The monitor in Management Console is intended for time-critical working environments that require continuous analysis of data movement.
See also
Overview of IBM InfoSphere CDC replication between solidDB® servers