Indexing your data with the Lifecycle Query Engine (LQE)

You can use the Lifecycle Query Engine to index and search for assets stored in any product configured to support the Tracked Resource Set specification.

Rational® Engineering Lifecycle Manager supports an integration with Lifecycle Query Engine through the implementation of a draft specification of a Tracked Resource Set API. The Tracked Resource Set API draft specification may not be implemented with any other application other than Lifecycle Query Engine.

By integrating with Rational Engineering Lifecycle Manager, you can use the Lifecycle Query Engine to create a Linked Lifecycle Data Index across tools that support the Tracked Resource Set specification, such as Rational Team Concert™, Rational Rhapsody®, Rational DOORS®, and Rational Quality Manager. A lifecycle tool makes its data available for indexing by exposing its Linked Lifecycle Data via a Tracked Resource Set (TRS), whose members must be retrievable resources with Resource Description Framework (RDF) representations, called Index Resources.

For more information about the Tracked Resource Set specification, see Open Services for Lifecycle Collaboration Tracked Resource Set Specification Version 2.0

An LQE Index built from one or more Tracked Resource Sets allows SPARQL queries to be run against the RDF dataset that aggregates the RDF graphs of the Index Resources. This permits the data from multiple lifecycle tools to be queried together, including cross-tool links between resources. Changes that happen to Index Resources in a lifecycle tool are made discoverable via the Tracked Resource Set's Change Log, allowing the changes to be propagated to the Lifecycle Index to keep it up to date.

Most of the resources in a Tracked Resource Set will be protected resources, to which the lifecycle tool ordinarily grants or denies access based on the identity of the authenticated user. LQE authenticates with the lifecycle tools as a trusted client (as opposed to as any particular user), giving it unrestricted access to the Index Resources. By implementing the Resource Access Control specification, lifecycle tools enable LQE to protect any information gleaned from the Index Resources, and to enforce the same access control policy on users of the index, as that of the lifecycle tools themselves.

The Lifecycle Query Engine is a jazz application, requiring registration with a single Jazz™ Team Server. In a distributed environment, friend relationships can be setup across different Jazz Team Servers.

Terminology used by LQE

Resource
A resource is an object being described by RDF expressions. An RDF resource is identified by a URI.
For more information refer to: Composite Capabilities/Preference Profiles: Terminology and Abbreviations
Triple
An RDF triple contains three components; the Subject, the Predicate, and the Object
For more information refer to: Resource Description Framework (RDF): Concepts and Abstract Syntax
Graph
An RDF graph is a set of RDF triples.
For more information refer to: Resource Description Framework (RDF): Concepts and Abstract Syntax
RDF vocabulary
An RDF vocabulary describes the meaningful use of properties and classes in RDF data.
For more information refer to: RDF Vocabulary Description Language 1.0: RDF Schema

URLs used by LQE

Home Page
https://[server]:[port]/lqe/web
Administration Page
https://[server]:[port]/lqe/web/admin
This is the page used to for all LQE administrative function.
Query Page
https://[server]:[port]/lqe/web/query
Use this page to run SPARQL queries. Useful when troubleshooting unexpected query results in other products.
User Authorization Page
https://[server]:[port]/lqe/web/auth
Use this page to enable or disable LQE access to data sources when running queries. This allows you to limit the data sources whose artifacts will be returned in query results.
Root Services Document
https://[server]:[port]/lqe/scr
The Jazz Team Server has a standard way of describing a Jazz Application called a root services document. The root services document for LQE describes its services, authentication model, license and functional user.

Log files generated by LQE

LQE Log
[JTS_ROOT]/server/logs/lqe.log
LQE Properties
[JTS_ROOT]/server/conf/lqe/lqe.properties
Jazz Team Server Log
Jazz Team Server Log: [JTS_ROOT]/server/logs/jts.log
Tomcat Log
Tomcat Log: [JTS_ROOT]/Server/Tomcat/logs/catalina.log
WebSphere® Application Server Log
[WebSphere_Install_Dir]\AppServer\profiles\[server_name]\logs\ lqe.log

Feedback