Delta Generation 

The repository objects in the Data Orchestration Engine (DOE), such as data objects, back-end adapters, and distribution models have runtime objects associated with them. These runtime objects include DDIC objects and generated code.

When an application developer activates a repository object by using the DOE workbench, the system persists the metadata of the application and then generates the runtime objects. The runtime objects are generated by the generation framework by using generators. Each runtime object has a corresponding generator. A generator is a combination of a meta information function module and an optional code template (based on the type of object being generated). These generators use the code templates along with the metadata information of the repository object to generate the runtime objects.

If any change is made to a meta information function module or code template, all the runtime objects associated with the corresponding generator must be regenerated. Since it is not possible to identify and generate specific runtime objects from the Data Orchestration Engine workbench, you must trigger the generation for the entire repository object. This can be time-consuming if you have to regenerate a large number of repository objects. To ensure that you can regenerate only the required runtime objects, you can use delta generation.

Delta generation allows you to:

·        Identify the changed generators

·        Identify the affected runtime objects as a result of changes to generators

·        Regenerate the affected runtime objects

·        Schedule the regeneration of objects if you have to regenerate a large number of objects

·        Perform monitoring activities such as monitor the status of regeneration, abort regeneration (if required), and schedule or cancel a scheduled regeneration

You can perform these activities even on generators that have not changed.