Configuring Rational DOORS and Rational DOORS Web Access as TRS providers for Lifecycle Query Engine

To track Rational® DOORS® resource changes, configure Rational DOORS as TRS provider so that Lifecycle Query Engine (LQE) can access the application data.
Important: If your application is on a different Jazz™ Team Server (JTS) than LQE, the keys that are generated in this task are reused later when you add data sources to the Lifecycle Query Engine as described in: Configuring Lifecycle Query Engine and generating the index. Note carefully the name and secret of each key.

About this task

To configure Rational DOORS as a TRS provider, follow the steps that are described in the following topics in the CLM information:
  1. Configuring Rational DOORS as a TRS provider
  2. Configuring Rational DOORS Web Access as a TRS provider
After the TRS providers are set up, you can configure Rational DOORS as a data source for LQE:

Procedure

  1. Browse to https://hostname:port/lqe/web.
  2. Select Administration in the toolbar menu.
  3. On the Data Sources page, select Add Data Source
  4. In the Add Data Source dialog, select the Root Services document URL option. Enter the Rational DOORS root services URL. Select the TRS URL. Enter a label, and select Specify authentication details
    • Root Services URL: https://doorsserver:port/dwa/public/rootservices
    • Select https://doorsserver:port/dwa/rm/trs
    • Label: Rational DOORS
    Screen capture of the Data Source values for Rational DOORS being added to LQE
  5. Enter the consumer key and secret.
    Note: The Consumer Key and Secret must match the values in the Rational DOORS Web Access festival.XML file. In the following example, xyz is the value.
    <f:property name="functional.user.consumer.key" value="xyz"/>
    <f:property name="functional.user.consumer.secret" value="xyz"/>
    Screen capture of the consumer key and secret
  6. Set the number of threads to 1 for first time and incremental indexing and click Finish. Occasional errors can occur if more than one thread is used for indexing.

What to do next

After you configure your applications as TRS providers, follow the steps in Running queries to test or debug the Lifecycle Query Engine implementation to validate your configuration.

Feedback