Rebuilding AWI search indexes in case of inaccurate search results

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• Automic SaaS

Issue/Introduction

This article provides steps to rebuild the Lucene search index for the Automic Web Interface (AWI). Rebuilding the index resolves issues where object searches return incorrect, inconsistent, or zero results.  Indexes should be rebuilt when there are problems in searching/listing objects that include, but are not limited to:

• The "Search for Use" option returns "0 objects" even when the object is in use.
• Search results show inconsistent counts (e.g., while there may be 2 objects matching the filter, 0 or 7 may show up in the search) without object changes.
• Newly created objects do not appear in search results.
• Search returns objects that were previously deleted.

Environment

• Automic Automation Versions: 12.x, 21.x, 24.x, 26.x
• Component: Automic Web Interface, Automation Engine

Cause

Local Lucene index stored in indexCache directory is inconsistent, corrupted, or cannot be updated due to disk space issues or process interruptions.

Resolution

For Automation Engine V21.x and V24.x

1. Stop all Java Work Processes (JWPs) across all nodes.
2. Navigate to the bin directory of the Automation Engine installation.
3. Remove the indexCache directory.
4. Restart the JWPs. The first JWP started assumes the indexing (IDX) role and rebuilds the index.

For Automation Engine V12.x

1. Stop all Java Communication Processes (JCPs).
2. Remove the indexCache or indexCache-12.X directory from the bin directory.
3. Restart the JCPs. The first JCP started rebuilds the index.

⚠️ IMPORTANT: In a distributed/multi-node setup, delete the cache directory on all nodes simultaneously before restarting processes.

Additional Information

• Search functionality may be limited or inaccurate while the rebuild is in progress.
• To monitor progress, check the JWP/JCP logs for message U00045136, which indicates the number of objects being re-indexed.
• To run a JWP with a dedicated indexing role, use: java -Xmx2G -jar ucsrvjp.jar -Iucsrv.ini -role=IDX (see the JWP Roles documentation for more information on starting JWPs with specific roles)

If further assistance is needed, the issue continues to occur, or rebuild does not resolve the issue, Contact Broadcom Support