Vocabulary reindexing operation for Lifecycle Query Engine

When you run the reindex operation without deleting the existing LQE TDB folders, reindexing the vocabularies is not required. However, if you delete the LQE TDB folders that store the Lifecycle Query Engine index, you need to reindex the vocabularies.

Problem

The reindexing of the vocabularies is not implemented when the LQE TDB folders get deleted, the following issues will occur in the Report Builder:
  • Reports stop working because of the missing types and attributes.
  • User would not be able to pick the types and attributes.
  • Types and Attributes show up as the URLs in the Report Builder UI.

Solution

  1. Reindex the vocabularies.
    If the LQE index folders were deleted, follow these steps:
    1. From the Lifecycle Query Engine Administration page, go to the Vocabularies section.
    2. Click Reindex Vocabularies.
    3. In the Internal Properties Configuration section, click Edit.
    4. Enable the Restore initial vocabularies checkbox.
    5. Click Reindex, then click OK.
  2. Refresh metadata in Report Builder.
    The vocabularies can take 1 hour to finish reindexing. No indication displays upon completion. After the vocabularies are reindexed, the Lifecycle Query Engine data source in Report Builder needs to be refreshed either manually or automatically.
    To manually refresh the metadata for a data source:
    1. From the Report Builder Administration page, go to the data source section.
    2. Click Refresh.
    To configure Report Builder for automatic metadata refresh:
    1. Go to Report Builder advanced properties section or conf/rs/app.properties file.
    2. Configure the following properties:
      • Define the time when type system model refresh task runs initially:
        • metamodel.autorefresh.time=6:00AM
      • Define the number of minutes between two runs of type system model refresh task:
        • metamodel.autorefresh.repeat.inminutes=720

Metadata refresh behavior

The metadata refresh operates according to the following rules:

  • The refresh runs at the scheduled start time and at the configured interval.
  • If a refresh fails, the next refresh occurs after the configured interval; it does not run immediately.
  • If the server is restarted during a scheduled metadata refresh window, the refresh runs immediately after startup.

The system behavior depends on whether a previous successful metadata refresh exists.

If a previous successful refresh exists:

  • You can create, edit, and run reports.
  • Report Builder uses the cached metadata from the last successful refresh.
  • Changes to the type system after that refresh do not appear in reports.

If no previous successful refresh exists:

  • You cannot create new reports.
  • Existing reports continue to run by using outdated metadata.
  • Reports do not reflect any type system changes made since the last cache.