Connecting Lifecycle Query Engine or Link Index Provider to applications that use the same Jazz Team Server

Lifecycle Query Engine or Link Index Provider can index data from any lifecycle management tool that supports the Tracked Resource Set (TRS) specification. If Lifecycle Query Engine or LDX and its data providers share Jazz® Team Server, it's easy to configure the communication because JTS can share settings with Lifecycle Query Engine or Link Index Provider.

1. From the Lifecycle Query Engine administration page, go to Data Providers at http://<host_name>:<port>/lqe/web/admin/data-sources.
   This page shows the live status of the data providers that Lifecycle Query Engine is connected to.
   LDX: From the LDX administration page, go to Data Providers at http://<host_name>:<port>/ldx/web/admin/data-sources.

   This page shows the live status of the data providers that LDX is connected to.

2. Click Add Data Provider.
   If you ran the setup wizard, the TRS feeds for applications that share the JTS with Lifecycle Query Engine or LDX are listed on the page in this format: https://server:port/tool/trs. Some feeds contain application resources. Process feeds contain data for timelines, iterations, projects, and teams.
   1. Select the data provider that you want to add.
      To see what TRS feeds are provided by the applications in IBM Engineering Lifecycle Management, read about Choosing tracked resources feeds for Lifecycle Query Engine.
   2. Enter a label as an identifier for the data provider.
   3. Optional: Specify the date and time for the initial indexing. If you leave the fields blank, the index is created when the wizard finishes. In a test lab environment, Lifecycle Query Engine or LDX 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 providers simultaneously. Each one runs on its own thread. Alternatively, you can schedule the initial indexing of multiple data providers to run one after the other.
   4. For applications that use the same JTS as LQE or LDX, authentication is not necessary. If you want to change the authentication type, select what authentication to use.
3. Configure the data provider.
   Hover over the question marks next to the property labels to find out details about the properties and their values.

   • The refresh rate specifies how often Lifecycle Query Engine or LDX attempts to access the data provider to refresh the index. A data provider that is not updated frequently can have a slower refresh rate than a data provider that is updated continuously. Increasing the refresh rate has a performance impact.
   • The refresh rate specifies how often Lifecycle Query Engine or LDX attempts to access the data provider to refresh the index. A data provider that is not updated frequently can have a slower refresh rate than a data provider that is updated continuously. Increasing the refresh rate has a performance impact.
   • The number of threads to fetch artifacts when adding or reindexing the data provider must be between 2 and 4. Each thread is roughly equivalent to one user that uses the Lifecycle Query Engine or LDX server. On Intel systems, if you use more than 4 threads, the improvement in data retrieval speed is minimal.
   • The option to continue with change log processing if resources are skipped, allows Lifecycle Query Engine or LDX to log an error and continue indexing after encountering a resource that cannot be indexed. This option is selected by default. If you disable it, the indexing process stops when a resource cannot be indexed.
   • The retry settings specify the following configurations related to fetching of resources and TRS documents:
     • Wait time before retrying failed patches or skipped resources.
     • Number of retries.
     • Retry interval multiplier.
     • Number of retries for TRS document.
     • Retry interval multiplier for TRS document.
     • Maximum retry wait.
     • Number of retried if data provider is temporarily available.

   
4. Click Save to start indexing or to activate the indexing schedule.