Hi Narendra,

If the elastic search does not select the appropriate IP you can do the following - the port range is 9300-9399

Hope this helps.

See SA-24120

The following prconfig setting allows the IP address to be set to an appropriate value.

<env name="indexing/distributed/network/host" value="your_IP_address"/>

But if we have multiple hosts how will the above setting work?

 With elastic search, the indexing nodes open a communication port for communicate with both index-client and other indexer nodes.

As mentioned, by default, elastic looks for an available listen port in 9300-9399 range. You must validate that ports 9300-9399 are unblocked / available.

In pr_sys_Statusnodes - pyclusteraddress holds the hazelcast IP address/port, pyindexeraddress holds the elastic address/port.

Both Elastic Search and Hazelcast are distributed technologies added to Pega 7 platform from 7.1.7 onwards. Elastic Search is meant to upgrade our full text search capabilities whereas Hazelcast is meant to improve our clustering and remote invocation capabilities. 

But if we have multiple hosts how will the above setting work?

If there are multiple nodes on the same machine, then all of them need this setting but the port number will be chosen by each node to be different from the other. pyIndexerAddress column in pr_sys_statusnodes table will show which port number each node is using. 

Hi,

Can full “Rule Content Search” be achieved by Pega OOTB “Search” functionalities ?

For example ,  we want to search the extract Rule Name and its details where a StepPage (e.g "MystepPage") , a hardcoded condition check (e.g if(X==”abc”)), parameter value passed (e.g param.EmpID) etc (all these given as input)   is used throughout application.

If Pega OOTB Search functionalities provide these then please refer us how can we configure this  in my application?