Symptom

The full text (Lucene) indexes permit developers to search for content within rules, data objects, and work objects.

Use the System Management application to build, or rebuild, these indexes.

In a multi-node cluster, the indexes reside only on one node; users on other nodes access them through SOAP services.

Two Dynamic System Settings values controlling access to the indexes must be consistent, identifying the same node. If these two are inconsistent, you may receive the following error during the rebuild process:

Failed to invoke MBean operation
Failed to invoke an operation
java.lang.Exception: Failed to invoke MBean operation
Failed to invoke MBean operation
ADMC0009E: The system failed to make the SOAP RPC call:

This error occurs due to inconsistent Dynamic System Settings values.

Solution

To resolve this issue, adjust the value of the following Dynamic System Settings (Data-Admin-System-Settings class) to reference the same Process Commander node:

• searchSoapURI – the URL used to communicate with full-text search engine on the indexing node.
• indexing/hostid – the internal node identifier string that uniquely identifies the indexing node in a multi-node deployment.

For example, if searchSoapURI is http://10.1.21.22:9081/prweb/PRSOAPServlet:

Then the value of the indexing/hostid Dynamic System Setting must match the node ID hash value associated with the deployment on node 10.1.21.22 at port 9081 with context root prweb.

Step 1. Determine this value by:

1. Interactively connecting to that node.
2. Using the Clipboard Viewer to examine the property pxSystemNodeID on the pxProcess page.

A Node ID value is a 32-character encoded hash string, similar to the following:

ad37e012e22f2a8cdfcfefb4c9ea7cb3

Step 2: Update the indexing/hostiddata instance and save the Dynamic System Settings form. Your changes will affect users who log in after you save this form.

Step 3: Start the System Management Application and reperform the index build.