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.
  1. See what data sources are configured for LQE or LDX. Go to the Data Sources 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.
    .
  2. 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:
  3. 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 source in which the sensitive data was removed, and then click Force update in the upper right corner.
  4. 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.

Feedback