Managing data sources for Lifecycle Query Engine

Edit online

After you install and configure Lifecycle Query Engine (LQE) to index the data from the lifecycle management tools, you can check the status of each connection on the Data Sources page. You can also view and modify the properties of your data sources, reindex, or add data more sources. If you deployed LQE across several nodes, you can view detailed status for each node.

Important: Lifecycle Query Engine is the data source for reporting on projects with or without configurations; however, there are considerations. For details, see Getting started with reporting by using Lifecycle Query Engine data sources on Jazz.net.

About this task

From the LQE administration home page, at: http://<host_name>:<port>/lqe/web/admin/data-sources you can run various operations:

Procedure

  • To add a data source, click Add Data Source.
  • To modify the properties of a data source, click the name of the data source, and then edit the settings.
  • To validate a data source, click name of the TRS feed in the list, and then click Validate. This task compares the TRS feed with the LQE index to ensure that the data in the index is up to date.
  • To reindex a data source, click the TRS feed name in the list, and then click Reindex. Depending on the amount of data, indexing for the first time or reindexing a data source can take a long time.
  • To check the status of a data source on a particular LQE node, click the status link and select the node. If the data source update fails, review and correct any errors. On the History tab you find statistics about the operations that ran for the data source you focus on: initial indexing, validation, reindexing, cleanup, or removal activities.

What to do next

Sometimes indexing completes with errors. Often these are problems in the TRS feed, or they are related to network connectivity issues. If LQE encounters issues during indexing, it skips resources. These skipped resources are not the result of errors or problems with LQE; they can occur for many reasons including socket timeouts, bad resource definition from the data sources, invalid RDF from the data sources, or temporary internet outages.

When LQE cannot index a resource from a data source, it tries to fetch the skipped resource five times, at one minute intervals. If the resource is not successfully fetched, LQE stops trying and generates an error in the LQE.log file. These entries are normal and expected, particularly with network or connectivity issues. To determine what is causing the data source issues, you can contact support for the affected data source tool.

  1. To review a list of skipped resources for a particular data source, on the Data Sources page, click Up-to-date.
  2. On the Data Source Status page, click the Skipped Resources tab and review the messages to determine if the skipped resources are caused by network issues or by possible product issues.

To ensure the integrity of the TRS feed data, and to troubleshoot missing or added artifacts, you can run validation. Validating the LQE index compares the current TRS feed from a IBM® Engineering Lifecycle Management application with the LQE index. Validating a TRS feed compares the current TRS feed to the data in the application repository. For details, read about this procedure.