Connecting to a TRS provider on the same JTS as a data source for the Lifecycle Query Engine index

You can generate a Linked Lifecycle Data Index for any lifecycle tool that supports the TRS specification and shares the same Jazz™ Team Server (JTS) as Lifecycle Query Engine (LQE). Configuring LQE to use the lifecycle tool as a data source is easy because the JTS can share much of the configuration data.

Before you begin

The LQE functional user (lqe_user) must be created in the JTS for the lifecycle tool, as described in Configuring Lifecycle Query Engine to access lifecycle application data.

Procedure

  1. In the LQE administration panel, select the Data Sources panel. This panel shows the live status of any data sources that LQE is connected to.
    Screen capture of the data sources panel showing a data source being indexed.
  2. Select Add Data Source.
    Screen capture of the Add Data Source wizard.
    1. The data sources that share a JTS with LQE are listed in a format similar to: https://server:port/tool/trs. Select the data source that you want to add.
    2. Add a label as an identifier for the data source.
    3. Optional: Specify a date and time for the initial indexing. Leaving the fields blank results in the index being created as soon as the wizard is finished. In a test lab environment LQE can index 50,000 artifacts in less than 1 hour - depending on your hardware and configuration you might experience a slower indexing rate.
      Note: You can index multiple data sources simultaneously. Each one runs on its own thread. Alternatively you can schedule the initial indexing of multiple TRS data sources to run one after the other.
    4. For tools that use the same JTS as LQE, no authentication should be necessary. If you want to change the authentication type, you can choose to specify the authentication.
  3. Select the data source configuration options.
    Screen capture of the "Configure Data Source" panel of the Add Data Source wizard
    1. The refresh rate specifies how often LQE attempts to access the data source for ongoing refreshes of its index. A data source that is not updated frequently can have a slower refresh rate than a data source that is updated continuously. Increasing the refresh rate has a performance impact.
    2. The number of threads for the initial indexing should generally be set to between 2 and 4. Each thread is roughly equivalent to one user using the LQE server. For Intel machines, the rate of improvement in data retrieval speed for more than 4 threads is minimal.
    3. The number of threads for the ongoing indexing should generally be set to between 2 and 4. Each thread is roughly equivalent to one user using the LQE server. For Intel machines, the rate of improvement in data retrieval speed for more than 4 threads is minimal.
    4. Continue with incremental update in case of skipped resources allows LQE to log an error and continue indexing when it encounters a resource it cannot index. This is selected by default. If it is disabled, the indexing process stops any time that a resource cannot be indexed.
  4. Once you finish the wizard, you are shown the data that can be configured at any point for this data source. Click Save to begin the indexing. The live status of the indexing process is displayed in the main Data Sources panel. Clicking the link in the status field displays an in-depth status report for the indexing process.
    Screen capture of the Data Source status overview page
    Screen capture of the Data Source status history page

What to do next

You can stop indexing a data source or pause the indexing process by hovering over the associated Actions field and clicking the icons.


Feedback