Connecting Lifecycle Query Engine to data providers to generate the index

Edit online

Any lifecycle management tool that supports the Tracked Resource Set (TRS) specification can be used as a data provider for the Lifecycle Query Engine index. To ensure that Lifecycle Query Engine can access the data, you must configure it to work with Jazz® Team Server and then add the lifecycle tools as data providers (TRS providers) for Lifecycle Query Engine.

About this task

If Lifecycle Query Engine and the lifecycle management tools that you are indexing share the same JTS, it is easy to configure the data providers because JTS can share some settings with Lifecycle Query Engine. If you ran the setup wizard, the TRS feeds are discovered automatically when you add a data provider.

Adding applications that run on the same JTS

If you installed Lifecycle Query Engine on a separate JTS from the lifecycle management applications, first you install the client access license for Lifecycle Query Engine on the JTS of the lifecycle applications, you create a functional user ID, you create an inbound consumer key for Lifecycle Query Engine in the administration section of each lifecycle management application, and then you add the data providers.

Adding applications that run on a different JTS

For more distributed topologies in which there are several JTS servers, read these topics:

Important: If you index the IBM DOORS® Next data provider after upgrading, or to fix problems that affect the Engineering Requirements Management DOORS Next TRS feed, perform a TRS 2.0 rebase before indexing.

As an administrator, open a web browser, and go to https://RM_Server:9443/rm/admin#action=com.ibm.rdm.fronting.server.web.trs.
Click TRS 2.0 Full Rebase. Wait for the operation to complete before you proceed. This step might take some time depending on the data size. Reindex the Engineering Requirements Management DOORS Next data provider only after the rebase operation completed.