In a multi-node clustered system, the index files required for search can be hosted on one or more nodes. To ensure high reliability and minimize search query downtime, configure at least two, and preferably three nodes as search host nodes.

• Viewing index host node status

  You can see whether your index host nodes are offline or online by viewing the index host node status on the Search landing page.

• Enabling and disabling encryption for communication among search nodes

  For on-premises deployments, enable encryption for communication among search nodes to prevent unauthorized access to the data that is transported across search nodes. By default, search is encrypted for cloud services and applications.

• Viewing search agent information

  You can view the status of Pega-RULES agents that incrementally update the search index files as changes are made to Rules-, Data-, and/or Work- instances. This information is useful for troubleshooting. You can view the agent name, number of entries currently in the queue, and the age of the oldest entry in the queue for each agent.

• Configuring automated search notifications

  You can periodically check the status of search agents and index files, and report on any events and issues that arise. The system sends out notifications when reindexing is complete or fails, when a period spot check fails, or when a full diagnostic check is complete or fails.

• Configuring index host nodes from the user interface

  In a multinode cluster system, the index files required for search can be hosted on one or more nodes. To add or remove an index host node interactively, complete the following steps.

• Removing index host nodes by using a direct connection to the database

  In a multinode cluster system, the index files required for search can be hosted on one or more nodes. To remove an index host node by using a direct connection to the database, complete the following steps.

• Enabling the indexing of classes
• Classifying nodes