DOORS Bridge Settings
First you have to enter the Web-Address (hostname, ip-address and port) of the Codebeamer DOORS Bridge Server and a 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 will work:
(in batch mode) permission will work:
Then you need to Select the DOORS Formal Module to associate with the current tracker:
If you are not sure whether the selected module is the correct one, then you can show a Preview of the first 50 entries.
 | Please note that generating a preview with lots of embedded images and objects may take a few seconds. |
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.
Since CB-9.2 and newer, you have also to decide whether to Trust the DOORS history of the selected Module or not?
Bad experience with real-life customer DOORS installations showed, that the DOORS object history is not always reliable, e.g.
• Attribute values have changed between baselines, but the lastModifiedTime of the objects did not change, nor does the object history contain this change.
If the DOORS history can be trusted:
• Consecutive imports can be incremental imports, that can only import objects, that were modified since the previous import, based on the lastModifiedTime of the objects and the object history.
• Incremental imports are significantly faster than Initial or Full imports, but can cause data loss, should the DOORS object history be flawed.
If the DOORS history cannot be trusted:
• Not only the first or initial import, but also consecutive imports, is always download the full module or baseline. Depending on the size of the module, this can take quite some time.
◦ The object change history is rebuild upon the import by comparing the newly loaded values against the values from the previous imports.
◦ If the DOORS history is also imported (see below), the imported history entries (changes) and the computed differences is merged into a consistent history.
If you are importing historic module baselines and are not sure about the quality of the baseline history, then import the baselines without trusting the DOORS history. Since this is a one-time migration, the quality of the imported data should have precedence over the duration of the import.
But it should be saved, to switch to incremental imports, after the initial migration is finished and before you start an automatically or periodically recurring synchronization.