This section covers several operational scenarios likely to be encountered after the initial UDB 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 storage 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 integration engine, it is essential to know what the expected results are before configuring the data capture for example:
- A new column populated in an existing table by an existing engine from an existing UDB Table; all the changes would be made at the target side where the Integration engine runs.
- New tables to be populated from new UDB Tables maintained by a new transactions, will require configuration changes 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.