Hi @Beaula123 ,
Root Cause (Most Common):
AEM Guides Search and Replace depends heavily on DITA Map parsing and indexing. If:
- The map is not associated with a DITA-OT map type, or
- References within the map are broken or incomplete, or
- The search engine configuration isn't detecting UUID-based maps,
then the tool will fail silently and show “0 files found”.
Steps to Fix:
1. Confirm DITA Map Association
Ensure the selected map is correctly typed as a DITA Map.
Go to CRXDE: /content/dam/broadcom/techdocs/ctp-test/Beaula/choice-table-test.ditamap
Confirm that it has this property:
jcr:primaryType = dam:Asset
dc:format = application/dita+xml; format=map
If not, right-click in CRXDE and update the dc:format manually to:
application/dita+xml; format=map
2. Ensure Map Contains Valid References
- Open the map in Web Editor and confirm it successfully references topics.
- Broken references (red exclamation) will prevent indexing.
3. Reindex Map Content from AEM Guides UI
- Go to Tools → AEM Guides → Content Indexing
- Select the DITA map in question and click “Reindex Map”
4. Check and Restart the Async Indexing Job
Sometimes background jobs get stuck. Do the following:
- Go to: http://<host>:<port>/system/console/status-slingjobs
- Look for any stuck/failed jobs related to DITA or indexing.
- Clear and restart them if needed.
5. Check Lucene Query Limits
Sometimes Lucene result limits can truncate queries:
- Go to /system/console/configMgr
- Look for "Apache Jackrabbit Oak QueryEngineSettingsService"
- Increase the limit:
- Query Limit: 500000
- Read Limit: 500000
- Save and test again.
6. Enable Debug Logs Temporarily
If still stuck, enable logs for detailed output:
- Log level: DEBUG
- Class: com.adobe.fmdita.search
Use /system/console/slinglog to do this.
Regards,
Amit
