Resolving data spill by removing sensitive data from Lifecycle Query Engine and the Link Index Provider

Edit online

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.

See what data providers are configured for LQE 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 LQE 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:
- Requirements Management (RM): Deleting artifacts from the RM repository
- Change and Configuration Management (CCM): Deleting work items in the web client and Deleting work items in the Eclipse client
- Quality Management (QM): Permanently deleting sensitive QM data and Deleting test artifacts
- Global Configuration Management (GCM): Finding sensitive data and data spills in global configurations and components and Deleting sensitive data from global configurations and components
Force an update to 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 in the upper right corner.
Compact the indexed data.

Example: If some requirements contain sensitive information, you follow the RM data spill procedure first, and then you force and LQE update, and compact the data.