This section covers several operational scenarios likely to be encountered after the initial Keyed File Compare Capture has been placed into operation, including changes in the scope of data capture and additional use or processing of the captured data by downstream Engines.
One factor to consider when contemplating or implementing changes in an operational configuration is the implementation sequence. In particular processes that will consume captured data must be tested, installed and operational before initiating capture in a production environment. This is critical because the volume of captured data can overwhelm transient Publisher if the processes that will consume the captured data are not enabled in a timely fashion.
While the examples in this section will generally proceed from capture of changed data to the application at the target by an Engine, it is essential to know what the expected results are before configuring the data capture. If for example the results are a new column populated in an existing table by an existing engine from an existing Keyed File file; all the changes will be made at the target side where the Engine runs. On the other hand if a new table full of columns is to be populated from a new source file, configuration changes will be made from one end to the other. When working through the examples below be prepared to continue from one example to the next when thinking about how to implement your own new scenario.