Monitoring and managing the performance of
Lifecycle Query Engine
You can monitor and manage the performance of
Lifecycle Query Engine by
viewing the status in the widgets on the administration home page, or on the Health
Monitoring page, by configuring properties that impact the responsiveness of queries and
server performance, and by responding early to issues that are identified.
Monitoring Lifecycle Query Engine performance
When you log on to Lifecycle Query Engine (LQE), you can quickly assess the overall status by viewing information in various widgets on the home page. You can view the high-level status of data sources, nodes, the query service, and backups. If issues need to be addressed, such as errors with data sources, you can click to see the details and take the appropriate actions.
Improving Lifecycle Query Engine performance
As an administrator, you might need to address performance issues that aren’t related to any of the query service or Lifecycle Query Engine ( LQE) node configurations. In these situations, you can review and update several advanced properties.
Improving the Lifecycle Query Engine performance by compacting indexed data
Each time you index the data from your lifecycle management applications, the amount of space required to store that data increases. Over time, as the index files get larger and the amount of available hard disk space decreases, you might experience server performance issues. You can take steps to prevent this situation by monitoring the hard disk usage and, when required, compacting the indexed data.
Improving the responsiveness of Lifecycle Query Engine queries
When the query activity is high, the load on the server can affect the responsiveness of the queries. As an administrator, you can take several measures to improve the resiliency of Lifecycle Query Engine ( LQE) and the responsiveness of queries by defining properties on the Query Service page. For example, you can define limits for running queries, enable query caching, enable load shedding, or block long-running queries.
Analyzing Lifecycle Query Engine server statistics
Lifecycle Query Engine ( LQE) provides detailed statistics that you can use to analyze the performance of the server and queries. You can use this information to identify performance issues and take corrective actions, or to make decisions about improvements.
Managing Lifecycle Query Engine nodes
If you installed and deployed Lifecycle Query Engine across several nodes, you can use the LQE Nodes page to view the status and performance details for each node, or to modify the configuration for a specific node.
Distributing query workload by deploying multiple Lifecycle Query Engine servers
By deploying multiple Lifecycle Query Engine ( LQE) instances across a set of servers, you can distribute the query workload and improve performance and scalability. Each LQE instance requires its own relational database and contains its own independent triple store index, which indexes the tracked resource set (TRS) data providers that you specify on the LQE administration page. Configure each LQE instance to index the same set of data sources.
How Lifecycle Query Engine uses licenses
Lifecycle Query Engine ( LQE) connects to tracked resource set (TRS) feeds to index data from the connected data sources (TRS providers).
Managing Lifecycle Query Engine vocabularies
The RDF vocabularies are descriptions of the schema that Lifecycle Query Engine ( LQE) uses to build SPARQL queries. You can add vocabularies, view the elements of vocabularies, or update the namespace, name, or prefix for a selected vocabulary.
Configuring Lifecycle Query Engine and connecting to external databases by using properties files
You can use a properties file to specify the initial configuration of Lifecycle Query Engine ( LQE) or to connect to an external database. LQE comes with templates of the lqe.releaseconfig.properties file and the dbconnection.properties file that you can use to create your own files.
Changing the database password
As an administrator, you must periodically change the database password.
Resolving data spill by removing sensitive data from Lifecycle Query Engine and the Link Index Provider
If an administrator removes sensitive data from an IBM® Engineering Lifecycle Management application that is registered with Lifecycle Query Engine ( LQE), the change is indexed by LQE automatically. To immediately index the deletion, complete this procedure. If you are using the Link Index Provider (LDX) to manage configurations, follow the same steps on the LDX administration page.