DOORS Bridge Settings
To access the DOORS Bridge settings you need to enter the Web-Address that is hostname, ip-address and port of the Codebeamer DOORS Bridge Server. And then you need to enter your DOORS Username and Password to login.
DOORS Bridge is a transparent proxy for the underlying DOORS instance, that forwards all requests to DOORS, including the user authentication. So basically, you can use any DOORS user, but in combination with DOORS Bridge only users with Edit DXL in batch mode permission works.
Once you login you need to Select the DOORS Formal Module to associate with the current tracker.
Preview the first 50 entries to confirm that you've selected the correct module.
 |
Generating a preview with lots of embedded images and objects may take some time.
|
The import from the selected DOORS module is Enabled by default, but you can disable (and re-enable later) at any time, by (un-)checking the appropriate checkbox.
You must decide whether to trust the DOORS object history for the selected module.
|
|
Experience with real-world customer installations has shown that the DOORS object history is not always reliable. For example:
• Attribute values have changed between baselines, but the lastModifiedTime of the objects did not update.
• The object history does not reflect these changes.
|
• Consecutive imports can be incremental, importing only objects modified since the previous import, based on lastModifiedTime and the object history.
• Incremental imports are significantly faster than initial or full imports.
|
|
If the object history is flawed, incremental imports may result in data loss.
|
If you do not trust the DOORS history
• Every import whether initial and subsequent must be a full import, downloading the entire module or baseline.
◦ If the DOORS history is also imported (see below), the imported history entries (changes) and the computed differences is merged into a consistent history.
• Full imports take more time, especially for large modules.
• During import, the object change history is reconstructed by comparing the current values against those from previous imports.
• If the DOORS history is also imported, the imported change records are merged with the computed differences to form a consistent history.
If you're importing historical module baselines and are unsure about the reliability of the DOORS history, import the baselines without trusting the DOORS object history. Because this is a one-time migration, data quality should take priority over duration of the import.
After the initial migration is complete, and before you enable the automated or periodic synchronization, you can safely switch to incremental imports to improve the performance.