Determining your replication needs
The first step in planning an CDC Replication deployment is to establish your replication needs. You need to determine each source database for replication and their corresponding target for replication.
CDC Replication source will capture changed data in your source database and send source table changes to the target.
The following table lists all of the databases, middleware and messaging middleware providers that are supported for replication by CDC Replication:
| Supported source databases | Supported target databases and middleware applications |
|---|---|
| IBM® DB2® for Linux®, UNIX and Windows (LUW) | IBM DB2 for Linux, UNIX and Windows (LUW) |
| IBM DB2 for i | IBM DB2 for i |
| IBM DB2 for z/OS® | IBM DB2 for z/OS |
| IBM Informix® Dynamic Server | IBM Informix Dynamic Server |
| IMS | CDC Replication Engine for Event Server |
| Microsoft SQL Server | IBM InfoSphere® DataStage® (for replicating by flat file or HDFS) |
| Oracle | Microsoft SQL Server |
| Sybase | Netezza® |
| Oracle | |
| Sybase | |
| Teradata | |
| CDC Replication Engine for FlexRep | |
| IBM Cloudant® | |
| Apache™ Hadoop® |
Each database that will act as a source for replication will need to have an instance of the CDC Replication replication engine installed, as will each target for replication.
Both the Management Console and Access Server applications must also be installed in order to configure and monitor replication between the source database and the target of replication.
If you are replicating from a non-relational database using InfoSphere Classic Change Data Capture for z/OS, you will also need to install Classic Data Architect.