Getting started with administering Lifecycle Query Engine

As a Lifecycle Query Engine (LQE) administrator, you might be responsible for a wide range of activities, including planning, installation, configuration, and management of the LQE servers in your environment. If you are new to LQE, this information will help you understand how it works, and how to ensure optimal performance.

The boxes in the following figure are links to corresponding topics that provide more information.

Image shows the different tasks that LQE
administrators typically perform. Click a box to open a topic. Planning a Lifecycle Query Engine implementation Installing Lifecycle Query Engine Upgrading Lifecycle Query Engine Migrating Lifecycle Query Engine Managing data sources for Lifecycle Query Engine Managing user access to data sources in Lifecycle Query Engine Managing Lifecycle Query Engine vocabularies Backing up and restoring Lifecycle Query Engine and Link Index Provider (LDX) Improving the Lifecycle Query Engine performance by compacting indexed data Setting up email notification for Lifecycle Query Engine events Configuring Lifecycle Query Engine and connecting to external databases by using properties files Monitoring and managing the performance of Lifecycle Query Engine Improving the responsiveness of Lifecycle Query Engine queries

Planning a Lifecycle Query Engine implementation

When you are deciding whether to use Lifecycle Query Engine to index the data from across your lifecycle management tools, there are several details to consider. Because the volume of data to be indexed can be considerable, and several factors can impact performance, you must carefully review the system requirements, deployment topologies, and best practices to ensure that the system performs as expected. The following resources can help:

Lifecycle Query Engine partitions

Lifecycle Query Engine has four partitions, each is a triple store databases, which contains Resource Definition Framework (RDF) data. All of these partitions are required for reporting. The partitions are as follows:
  • Artifacts

    A triple store index that provides RDF data for reporting from tools. When you run a report, it queries against the artifacts database. The database is persisted on the local file system at server/conf/lqe/indexTdb. Compaction reduces the size of this partition on disk.

  • Artifact Types

    It is the triple store index that provides the reporting metamodel, which you can compute from all the tools. The database is persisted on the local file system at server/conf/lqe/shapeTdb. Report Builder uses the metamodel to assist you while authoring the reports. Compaction reduces the size of this partition on disk.

  • Historical Data

    A triple storage database that contains historical metric collections that you can use in reports to track trends over time. It contains daily computed analytics about the RDF data in the artifacts partition. Compaction does not reduce the size of the historical data on disk. The database is persisted on the local file system at server/conf/lqe/historyTdb.

  • Internal metadata

    LQE uses this triple store index internally to ensure the data integrity of the RDF data in the artifacts partition. The database is persisted on the local file system at server/conf/lqe/versionTdb. Compaction reduces the size of this partition on disk.

Attention:
  • Do not run virus scans on the indexes, they might damage the indexes.
  • Do not access partition folders when a server is running.
  • Before accessing any of the partition folders, allow server to finish startup or shutdown activities that are running and stop completely.

Installing Lifecycle Query Engine

Lifecycle Query Engine is a Jazz® Reporting Service component that is available in the web installer for IBM Engineering Lifecycle Management.
Note: While the default installation and setup using the wizard leads you to install all of the applications on a single server, this topology is not necessarily the best choice. Carefully consider the options. You can install LQE on separate servers, and even deploy it across several nodes, each with their own external relational database..
For more information, see the Interactive installation guide.