Overview of Lifecycle Query Engine relational store
Jazz® Reporting Service is a reporting solution for IBM® Engineering Lifecycle Management. It allows quick data consolidation from various data providers across your tools and project areas. It consists of three components: Report Builder, Data Collection Component, and Lifecycle Query Engine. Lifecycle Query Engine reports on artifacts across projects or versioned data in configurations.
Apache Jena served well, however as a file-based data store, it has scaling limitations. The Apache Jena requires significant system resources, especially RAM. Customers with many projects and applications are reaching the limits Apache Jena can comfortably offer. IBM replaced Apache Jena in a way this is incremental, measured, predictable, and consumable for administrators and practitioners.
Lifecycle Query Engine relational store
In Jazz Reporting Service Report Builder version 7.0.3 and later, you can associate Lifecycle Query Engine and Lifecycle Query Engine scoped to a configuration data source with the reporting relational database-based solution. When this capability is configured and you author a report, you can switch between the default SPARQL-based query and the SQL query. Lifecycle Query Engine rs deployment topology depends on the customer type.
- If you have existing ELM data, deploy the two Lifecycle Query Engine architectures side by
side, keeping the Lifecycle Query Engine Jena system as is while you add a system to host
Lifecycle Query Engine relational store. A Report Builder can be configured to
run both Jena and SQL queries, and to compare the queries for correctness and performance. This
allows you to transition to Lifecycle Query Engine relational store with the least amount of
risk. The Lifecycle Query Engine Jena system can be decommissioned after the transition is completed.
- If you are starting out with the Engineering Lifecycle Management, deploy Lifecycle Query Engine
relational store only.
