You can use Lifecycle Query Engine with either the default Apache Derby database or with an external database; what you choose depends on how you deploy LQE. For example, if you deploy a single LQE node, you can use either option. However, if you are deploying LQE across several nodes, you must use an external database. For information about the supported databases, see Setting up the database.
Lifecycle Query Engine is a Jazz™ application that is registered with a single Jazz Team Server. In a distributed environment, friend relationships can be set up across different servers, providing access to the application data.
Lifecycle tools make data available for indexing by using tracked resource sets (TRS); members of the TRS are retrievable resources with resource description framework (RDF) representations, called index resources. You can create and run SPARQL queries on the RDF dataset that aggregates the RDF graphs of the index resources. These queries include data from across the lifecycle tools; they also cross-tool links between the resources. The change log in the tracked resource set captures any changes that happen to index resources, and the changes are propagated to the lifecycle index, keeping it up to date.
Resources in a TRS can be protected resources. An LQE administrator can grant access to indexed resources based on the entire index, each data source that is indexed, or access contexts that are defined by the lifecycle tools.
For more information about the TRS specification, see Open Services for Lifecycle Collaboration Tracked Resource Set Specification Version 2.0 .