Integrating Lifecycle Query Engine with applications

You can integrate Lifecycle Query Engine with applications to enable traceability and reporting across your engineering tools.

Connecting Lifecycle Query Engine to data providers to generate the index
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.
Connecting Lifecycle Query Engine or Link Index Provider to applications that use a different Jazz Team Server
If you installed Lifecycle Query Engine or Link Index Provider on a separate Jazz Team Server from the lifecycle management applications, first you add the client access licence for Lifecycle Query Engine or LDX on the JTS where the lifecycle tools are registered, then you create a functional Lifecycle Query Engine or LDX user that can run background tasks, you create an inbound consumer key for Lifecycle Query Engine or LDX on each lifecycle management application, and finally you add the data providers by using root services documents or URLs. This configuration ensures that Lifecycle Query Engine or LDX can access the IBM® Engineering Lifecycle Management data.
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.

Parent topic: Administering Lifecycle Query Engine