Importing an IBM DOORS Project

Use the Connector for DOORS to import a complete IBM DOORS project into Polarion. The connector works with all Doors 9.x versions running on Windows. (It will still work if Polarion is run on a Linux machine.)

Limitations and Recommendations

Before importing, read the Import Limitations and Recommendations section below.

The connector will import the following:

Once imported, the connector can be used to continuously import updates made within the DOORS modules.

TIP

To ensure that the synchronization runs smoothly, make sure that there is a strong network connection between DOORS and Polarion.

  1. Click on the on the top left and got to Administration.

    ( Administration ConnectorsDOORS)

  2. Open the DOORS Client.

  3. Open the DXL Interaction Window in DOORS. (Tools Edit DXL )

  4. Click on the script on the "Establish connection to DOORS" screen in Polarion and copy (CTRL +C) it to the clipboard.

  5. Paste (CTRL +V) the script into the DXL Input text box in DOORS and click Run.

  6. The DOORS client will connect to the Polarion server and send the required connector data.

  7. Select the target DOORS project and click Next.

  8. Select all DOORS modules to configure and import.

    Previously imported modules have a black check mark. These modules will be re-imported but not re-configured.

    Click the check box again so that they turn green to re-configure them.

    Remove the check mark on any modules you do not wish to re-import.

    Maximum Number of Modules That Can Be Configured per Import

    The maximum number of modules that can be configured in a single import is 50. (But there is no limit to the number of pre-configured - black check marked modules - that can be imported). If more than 50 modules need to be configured, simply run the connector multiple times.

  9. Configure the Work Item type to be used when importing and configure how the DOORS attributes are mapped to Polarion attributes.

  10. The "Create missing attributes and values" check box will automatically create all missing custom fields and enumeration values.

  11. Click Start Import to import all selected modules to Polarion.

  12. The import status can be checked in the Monitor.

DOORS Import Limitations and Recommendations

  • Picture objects are not supported but pictures inserted as OLE objects are.

  • If a DOORS module’s structure can't be mapped to a document flow, Requirements may not appear at the expected location. For example, in DOORS you can create the following structure.

    Example:

    Heading

    Requirement

    But a document flow would recognize it as;

    Example:

    Heading

    >Requirement

    The connector would therefore preserve the parent child relation by re-positioning the requirement to;

    Requirement

    Heading

    Headings that are hierarchically below a Requirement can’t be inserted into the document during import.

    Example:

    Requirement

    >Heading

  • Module properties are not imported, only object properties are.

  • DXL attributes will be imported as static data into Polarion so will not act as they do in DOORS.

  • The thumbnails generated for imported OLE objects are not always accurate.

    (Especially when the conversion is executed on Linux.)

Note

Image Magick must be installed and configured to see the thumbnails of imported OLE Objects. See the Include thumbnails for OLE DOORS and ReqIF imports section for details.

Memory Settings when Importing Large DOORS Modules

Synchronizing large DOORS modules that contain a lot of OLE objects consumes a lot of memory.

If you're planning to import them, assign at least 4 GB to Polarion.

If you see an error like "Expected 5 objects (top-level) from Doors but received 4" in the synchronizer log it's probably because Polarion has run out of memory and you'll need to assign more. (You can confirm this by looking for java.lang.OutOfMemoryException entries in the main Polarion log.)

Return to the Import DOORS instructions at the top of this section.