Administering Lifecycle Query Engine
After installation, administrators can add and configure data sources and user
access for Lifecycle Query Engine . They can analyze server statistics, monitor and manage the
query performance, or troubleshoot problems.
Getting started with administering Lifecycle Query Engine Lifecycle Query Engine administrator, you might be responsible for a wide range of activities, including planning, installation, configuration, and management of the Lifecycle Query Engine servers in your environment. If you are new to Lifecycle Query Engine , this information will help you understand how it works, and how to ensure optimal performance.Reducing downtime during Lifecycle Query Engine reindexing Lifecycle Query Engine , reports that run during the reindexing might not be accurate. Team members must run reports only after the reindexing is complete. To reduce this downtime while you reindex Lifecycle Query Engine , you can clone the Lifecycle Query Engine instance and reindex the clone. Team members can continue to run reports and historical trend data is still collected. After the clone is reindexed, you can merge the indexed data and resume by using the original Lifecycle Query Engine instance. Connecting Lifecycle Query Engine to data providers to generate the index Lifecycle Query Engine index. To ensure that Lifecycle Query Engine can access the data, you must configure it to work with Jazz® Team Server and then add the lifecycle tools as data providers (TRS providers) for Lifecycle Query Engine .Connecting Lifecycle Query Engine or Link Index Provider to applications that use a different Jazz Team Server Lifecycle Query Engine or Link Index Provider on a separate Jazz Team Server from the lifecycle management applications, first you add the client access licence for Lifecycle Query Engine or LDX on the JTS where the lifecycle tools are registered, then you create a functional Lifecycle Query Engine or LDX user that can run background tasks, you create an inbound consumer key for Lifecycle Query Engine or LDX on each lifecycle management application, and finally you add the data providers by using root services documents or URLs. This configuration ensures that Lifecycle Query Engine or LDX can access the IBM® Engineering Lifecycle Management data.Connecting Lifecycle Query Engine or Link Index Provider to applications that use the same Jazz Team Server Lifecycle Query Engine or Link Index Provider can index data from any lifecycle management tool that supports the Tracked Resource Set (TRS) specification. If Lifecycle Query Engine or LDX and its data providers share the same Jazz Team Server , it's easy to configure the communication because JTS can share settings with Lifecycle Query Engine or Link Index Provider .Adding data providers to Lifecycle Query Engine by using root services documents Lifecycle Query Engine data provider if the application is registered with a different Jazz Team Server than Lifecycle Query Engine .Adding data providers to Lifecycle Query Engine by using URLs Jazz Team Server than Lifecycle Query Engine , you can add it as data provider for Lifecycle Query Engine by using a data provider URL. If the application doesn't have a root services document, you can register the TRS feed as a data provider for Lifecycle Query Engine by typing the OAuth URLs. This is the most complex method of adding data providers to Lifecycle Query Engine . Use this procedure only if you are very familiar with the architecture of your solution.Choosing tracked resources feeds for Lifecycle Query Engine IBM Engineering Lifecycle Management applications are registered to a different Jazz Team Server than Lifecycle Query Engine , you must choose which tracked resource set (TRS) feeds to configure as data providers for Lifecycle Query Engine . The table in this topic shows what each TRS feed contains, and helps you decide what to configure.Moving data from Lifecycle Query Engine with Jena or Link Index Provider with Jena Lifecycle Query Engine with Jena or Link Index Provider with Jena data that is saved on the local file system consists of the index directories and several configuration files for the application. The index directories contain all the artifacts from the data source, merged artifacts, historical metrics that are created for trend reporting, and a version index that is used internally. The artifacts from the data sources are stored in the indexTdb directory and the historical metrics are stored in the historyTdb directory. Also, the merged artifact types are stored in the shapeTdb directory and the version information is stored in the versionTdb directory. If you do not have enough space for the indexed data on the drive where Lifecycle Query Engine with Jena or Link Index Provider with Jena is located, you can move the data to a new location on a different drive.System requirements for Lifecycle Query Engine relational store Installing and enabling Lifecycle Query Engine relational store Lifecycle Query Engine admin query diagnostic tab functions Query tab in Lifecycle Query Engine can be used to test or troubleshoot unexpected report results. Managing data providers for Lifecycle Query Engine Lifecycle Query Engine to index the data from the lifecycle management tools, you can check the status of each connection on the Data Providers page. You can also view and modify the properties of your data providers, reindex, or add more data providers. If you deploy Lifecycle Query Engine across several nodes, you can view detailed status for each node.Backing up and restoring Lifecycle Query Engine Relational store for Oracle Backing up and restoring Lifecycle Query Engine relational store for Db2 database Validating TRS feeds and the Lifecycle Query Engine or Link Index Provider index Lifecycle Query Engine or LDX index when Report Builder reports don’t show the artifacts that you expect. Validating these items can help you diagnose and troubleshoot problems and avoid reindexing data providers.Managing user access to data providers in Lifecycle Query Engine Lifecycle Query Engine gathers information about project areas and membership from each application in IBM Engineering Lifecycle Management . Lifecycle Query Engine uses this information to create data groups based on the access control settings from the project area of each tool. Data groups become part of the TRS feeds.Running Lifecycle Query Engine queries to test or debug Lifecycle Query Engine to test or troubleshoot unexpected report results. The SPARQL queries access the Lifecycle Query Engine data directly. The queries that you create cannot be stored in Lifecycle Query Engine .Collecting metrics for historical trends reports Lifecycle Query Engine tasks to collect data.Setting up email notification for Lifecycle Query Engine events Lifecycle Query Engine to send email notifications when specific events occur. For example, if a data provider becomes unavailable, or a node goes offline, you’re notified and can take the appropriate corrective action.