Configuration options - connect_cdc_sqdata - 4.1

Connect CDC (SQData) Architecture

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
4.1
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Architecture
Topic type
Installation
How Do I
Copyright
2024
First publish date
2000
ft:lastEdition
2024-02-07
ft:lastPublication
2024-02-07T13:24:57.122078

The versatility Connect CDC (SQData) can initially appear to imply complexity. While the product is indeed complex internally, it has been engineered to minimize external complexity while at the same time preserving the flexibility to run on multiple platforms and support all the principal data sources and targets. The Apply Engine for example can often be configured and tested on one platform and implemented on another operating system with little or no modification. Migration of Apply and Replicator Engines from a development environment through integration testing and on to the production environment can be accomplished without modification and using your existing configuration management tools.

While the Apply and Replicator Engines are powerful tools, they do not exploit any behind the scenes or under-the-cover interfaces to the Target databases, file systems or messaging systems. They operate under the same constraints placed on any "C" application program that can Insert, Update or Delete Target data including IBM Db2Connect, Oracle SQL*Net, ODBC, librdkafka for Kafka (and Kafka look-alikes like AWS MKS and Azure EventHub) and the IBM MQ the standard interfaces to those tools, specifically the open source librdkafka interface and the IBM MQ client

The one area where a level of complexity cannot be completely mitigated are the configuration of the Captures. Even the captures however use a common set of tools for configuration and nearly identical configuration parameters. It is the source databases themselves that each require some specific configuration steps to initially enable and facilitate ongoing capture. Once performed however those typically responsible for the configurations will find it easy to repeat the process as needed for subsequent implementations.