Our example began with the addition of a new pair of Keyed Files to be compared with the captured data published to an existing Engine. Often however a change results from recognition that a new downstream process or application can benefit from the ability to capture changes to existing data. Whether the scenario is event processing or some form of simple replication the implementation process is essentially the same.
Our example continues with the addition of the new Engine (KFITODB2) that will populate a single relational table with columns corresponding to one or more fields in a Keyed File file already being captured. The new Engine will be running on another platform, not previously used by an Connect CDC (SQData) Agent and will be updating a DB2/LUW table.
While no changes are required to the capture configuration to support the new Engine, the CDCzLog Publisher Agent will require configuration changes and the new Engine must be added.