Whether initiating Change Data Capture for the first time, expanding the original selection of data or including a new source of data from the implementation of a new application, the steps are very similar. The impact on new or existing Capture and Apply processes can be determined once the source of the data is known, precisely what data is required from the Source, whether business rules require filters or data transformations and where the Target of the captured data will reside.
Example:
Our example starts with the addition of a new Segment to an existing IMS Database DBD in an existing IMS SSID.
Solution:
In order to capture the changes for the new IMS segments, the EXIT keyword must be specified on either the SEGM or DBD keywords in the IMS Database Descriptor (DBD). Generally when a new segment is added to an existing IMS database, the method for specifying capture will be the same as previously used for existing segments.
If the IMS Log Reader Capture agent was already configured to capture the existing SSID, no changes to the Capture Agent CAB file are required. Once the IMS DBD is active and 99 records are being written to the IMS Log, the Capture agent will act on them.
If other segments from the same IMS Database are already being processed by an existing Engine, it is likely that no changes need to be made to the CDCzLog Publisher configuration.
Finally, determine how the new data will affect existing Engines and modify the Engine script accordingly.