Integrating DOORS Next with ClearQuest

Edit online

When IBM® Rational® ClearQuest® is integrated withDOORS® Next in the IBM Engineering Lifecycle Management you can associate requirements with defects, tasks, requests for enhancements, and other record types.

Before you begin

  • Install the DOORS Next application and configure Jazz® Team Server.
  • Install the compatible version of the ClearQuest web server component. You can install the ClearQuest web server on the same computer as the DOORS Next application or on a remote computer. For more information, see Deploying and installing ClearQuest in the Installing section of the ClearQuest documentation.
  • Configure the integration in ClearQuest . For instructions, see ClearQuest documentation. This configuration requires that you apply the OSLCLinks package to your ClearQuest schema. Optionally, you can apply the RequirementsChangeRequest package to the schema.
  • Obtain an Analyst Client Access License or a license with similar IBM Engineering Requirements Management DOORS Next capabilities.
  • Create or access a IBM Engineering Requirements Management DOORS Next project to integrate with a ClearQuest schema repository. You must have project adminIBM Engineering Requirements Management DOORS Next the requirements management project. If a IBM Engineering Requirements Management DOORS Next project does not exist, see Creating requirements projects.
  • Use public host names rather than aliases or proxies for the ClearQuest web server and Jazz Team Server.
  • Disable any software that blocks pop-up windows in your browser.

Procedure

  1. Set up cross-server communication with ClearQuest .
    1. In a web browser, go to https://fully qualified hostname:9443/jts/admin.
    2. On the Server Administration page, click the Server tab.
    3. In the Communication section, click Friends (Outbound). The Friends page opens.
    4. Click Add. The Add Friend window opens.
    5. Type the name to use to identify the ClearQuest web server.
    6. For the root services URI, type the concatenation of the public URI and the ClearQuest discovery context information.
      For example, https://cq-hostname/cqweb/oslc/repo/schema-repository/discovery, where cq-hostname is the name of your ClearQuest web server and schema-repository is the name of your ClearQuest schema repository.
    7. For the OAuth secret, enter a code to associate with the new OAuth consumer key of the server.
      Note: Do not enter the key itself; enter a shorter phrase to associate with the actual key.
    8. In the Re-type Secret field, retype the OAuth Secret code phrase.
    9. Select Trusted to designate the ClearQuest web server as a Trusted consumer. Trusted consumers can share authorization with other trusted consumers and do not require user approval to access data.
    10. Click Create Friend. If the connection to the root services URI was successful, a message confirms that the friend was added and that a provisional key was generated. Click Next.
    11. Click the Grant access for the provisional key link.
    12. Enter an administrator user ID. Click Continue and log in to the ClearQuest web server.
    13. Click Yes to approve the consumer key. Click Finish.
  2. Complete the steps in Configuring ClearQuest Web server for cross-server communication, which is in the Integrating section of the ClearQuest documentation. If you already completed those steps, skip to the next step.
  3. In the DOORS Next application, create a link between the ClearQuest user database and the IBM Engineering Requirements Management DOORS Next project area.
    1. In the DOORS Next application, from the Administration menuAdministration menu item click Manage Project Areas.
    2. Click the project area to configure.
    3. Scroll to the Associations section, and then click Add.
      The Add Association page opens.
    4. From the Application list, select your ClearQuest web server and log in to the server when you are prompted.
    5. From the Association list, select an association type to use for the integration.
      For example, Uses - Implementation Requests or Uses - Requirements Change Requests.
    6. In the Artifact Container section, click the ClearQuest databases.
    7. Click OK and then save the changes to the project area. If needed, add another association type.

What to do next

Team members in your project can now start creating links between requirement artifacts and ClearQuest records.