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, the change is indexed by Lifecycle Query Engine automatically. To immediately index the deletion, complete this procedure. If you are using the Link Index Provider to manage configurations, follow the same steps on the LDX administration page.

See what data providers are configured for Lifecycle Query Engine or LDX. Go to the Data Providers administration page:
- LQE: Go to https://<Host_name>:<port>/lqe/web/admin/data-sources.
- LDX: Go to https://<Host_name>:<port>/ldx/web/admin/data-sources.
Fix the data spill in each affected application that is registered with Lifecycle Query Engine or LDX, or contact the application administrator to confirm that the sensitive data was removed.
You might have data from one or more of these applications:
- DOORS® Next (RM): Deleting artifacts from the RM repository
- Engineering Workflow Management: Deleting work items in the web client and Deleting work items in the Eclipse client
- Engineering Test Management (QM): Permanently deleting sensitive QM data and Deleting test artifacts
- Global Configuration Management: Finding sensitive data and data spills in global configurations and components and Deleting sensitive data from global configurations and components
Force an update to the index immediately instead of waiting for the scheduled data refresh. Go to the administration page:
- LQE Go to https://<Host_name>:<port>/lqe/web/admin/data-sources
- LDX Go to https://<Host_name>:<port>/ldx/web/admin/data-sources.
Click the data provider in which the sensitive data was removed, and then click Force update.
If the data providers are configured for Lifecycle Query Engine with Jena, then compact the indexed data.

Example: If some requirements contain sensitive information, you follow the Engineering Requirements Management DOORS Next data spill procedure first, and then you force and Lifecycle Query Engine update, and compact the data.