Troubleshooting: "Search failed" for Find Rules tool in a multi-node cluster
Symptom
The Developer portal gives you the ability to search for rule instances using the Find and Advanced Search utilities. Process Commander uses indexes to perform search queries quickly and efficiently. You can control the location of the index files using the Dynamic System Setting instance named SearchSoapURI.
Normally, this is defined during the PRDBUtil
portion of the application deployment.
In a multi-node system, the search index files are stored on one node only, to save disk space and processing. Searches performed by users connected to another node are forwarded to the hosting node using a SOAP servlet. The node containing the indexes is identified by a Dynamic System Settings data instance.
In this multi-node environment, the following error may occur when you perform a search from any of the nodes other than the one hosting the indices:
Search failed due to problems connecting to the search SOAP service. Please review the Data-Admin-System-Setting for “SearchSoapURI” to ensure a valid endpoint URL, or try again after some time.
This error occurs because of an incorrect Data-Admin-System-Setting value.
Update: This issue is fixed in V5.3.
Solution
To resolve this issue, open the Data-Admin-System-Setting for SearchSoapURI and change the Key Index, as follows:
- From the Class Explorer, select Data-Admin-System-Settings. The Instances of this class appear on the right:
- Select the Key String indexing/SearchSoapURI. The following is displayed:
Note the Key String field contains index/SearchSoapURI. - Click the Save As icon to display the following.
- Remove indexing/ from the Setting Purpose field and click Save As.
The new D-A-S setting appears as follows: - It also appears on the Instances page: