Maintaining data synchronization for the Global Search feature

Three batch processes are used to maintain the accuracy of global search results.

• The Global Search Sync batch process runs automatically at midnight in the time zone of the server. It synchronizes activity and entity changes for that day.

• The Global Search Manual Sync process can be run manually from NexJ Admin Console. This process runs immediately to synchronize the specified class instance changes for a given period.

• The GlobalSearchSyncBatchJob-requestHandshake process can be run from NexJ Admin Console. This job is used to request a handshake with the OpenSearch server. During a handshake, the index policy is set if it doesn't exist, index templates are set if they don't exist, and missing indexes are recreated. It does not need to be run unless an index has been deleted.

To run the synchronization batch process manually, open NexJ Admin Console and click the Batch Broker button to open the Execute Batch Broker Process dialog.

Select the "GlobalSearchSyncBatchJob - manualRun" process from the dialog and specify the following information in the Value field for each argument:

class
Specify a single class name. By default, the two supported class names are Act and Entity. Any additional classes configured for your deployment of the Global Search feature need to be synchronized as well. You can only run the process for a single class at a time. If you need to synchronize all changes, you must run the process once for each class.

startTime, endTime

The values are specified in the YYYY-MM-DD [HH:mm:ss] format using the time zone of the server. These times refer to the audit attributes of the instances, such as create and edit times.

You can view the status of the processes in the NexJ Admin Console on the Process page. You can cancel a running process by right-clicking on it to bring up the "Cancel" menu.