CA Endevor/DB Conceptual Overview › Supporting Functionality › CA Endevor SCM to CA Endevor/DB Bridge

CA Endevor SCM to CA Endevor/DB Bridge

The CA Endevor SCM to CA Endevor/DB Bridge assists in the promotion management process when both dictionary and non-dictionary entities (COBOL programs, for instance) are involved. As a link between CA Endevor/DB and CA Endevor SCM, this product interface provides centralized change logging and promotion management capabilities.

• Centralized Change Logging – Using the CA Endevor SCM to CA Endevor/DB Bridge, changes to both dictionary and non-dictionary entities are logged, tracked and reviewed in one central location— the CA Endevor/DB Change Control Database (CCDB). As changes are made to CA Endevor SCM entities, that change activity can be dynamically monitored through the CA Endevor SCM to CA Endevor/DB Bridge and logged to CA Endevor/DB's Change Control Database. The end result is a centralized view of all related change activity, regardless of whether that activity takes place in the dictionary or in CA Endevor SCM And through the use of CA Endevor/DB CCIDs, all change activity pertaining to a particular maintenance request, development activity, or software release activity can be logged to the same CCID within the Change Control Database.
• Centralized Promotion Management – When all change activity is being logged to the Change Control Database, it is possible to use CA Endevor/DB's promotion management facilities to control the promotion cycle for both dictionary and non-dictionary entities. The Selection process can be used to produce an entity list that includes related non-dictionary structures (supporting COBOL programs for an &ADS. application, for example) as well as all appropriate dictionary structures (maps, dialogs, processes, etc.). The Verification and Correlation processes can be used to assess the impact of both dictionary and non-dictionary changes. The Migration process can then be used to migrate changed dictionary entities from one dictionary to the next and move the related non-dictionary entities from one CA Endevor SCM location to the next. Finally, the Confirmation process can be used to complete the cycle by confirming the successful promotion of both the dictionary and non-dictionary entities.