Previous Topic: CorrelationNext Topic: Supporting Functionality


Migration

Once the candidate list has undergone QA, the final promotion "picklist" is used by CA Endevor/DB's Migration facility to copy source statements, executable modules or both from the source system to the target system. During Migration, the Dynamic Change Monitor on the target system is run in a special migration mode to reflect that data dictionary modifications are the result of migration.

After migration has been successfully committed and tested on the target system, the CA Endevor/DB Confirmation facility sends a confirmation file back to the source system, reflecting the exact time the entities were received on the target system. The Confirmation facility then signs the migrated entities back in. At this point, a complete migration audit trail exists on both the source and target systems, identifying exactly what was sent, what was received, when and where. Furthermore, the migrated entities are freed so that the software development life cycle can continue.