Our example began with the addition of a new Oracle Table to the data capture process and sending the captured data 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 Straight replication the implementation process is essentially the same.
Our example continues with the addition of a new Engine (ORATOSQL) that will populate relational tables with columns corresponding to one or more fields from the same Oracle source. The new Engine will be running on second platform, Windows SQL Server, not previously used by an Connect CDC (SQData) Agent and will be updating SQL Server tables.
While no changes are required to the Storage agent to support the new Engine, the Capture agent will require configuration changes and the new Engine must be added.