Full Text Search - Search Index Host Node Setting - Single Node
Hello,
In the System search settings under the "Search Index Host Node Setting", we have to give the node and directory and node name.
My question is do we need to specify this row in a SINGLE node environment?
The info in the help is as follows : "Search Index Host Node Setting - In a multi-node cluster system, the Elasticsearch index files required for search may be hosted on one or more nodes."
If we don't give any path where would the index files be generated?
Further related-random questions :
- There is a DSS "indexing/explicitindexdir" to specify a path. Which value would take precedence while pega forms the index files?
- What is the significance of "initialization/explicittempdir" value in the prconfig file?
- While performing any search in DEV portal, a SOAP call with URL in the SearchSoapURI DSS is being used. What is this for?
TIA :)
Accepted Solution
Pegasystems Inc.
US
My question is do we need to specify this row in a SINGLE node environment?
- This specific behavior will vary by version. It may auto populate the fields when the first node starts after installation and indexing can just be enabled, but if that's not the case, then yes one row needs to be populated. In later versions by default, if the first node that starts does not have indexes built on it the indexes will start to building automatically. (Can be disabled via JVM argument)
If we don't give any path where would the index files be generated?
- The default path I believe is a "PegaSearchIndex" directory in the Pega temp directory.
There is a DSS "indexing/explicitindexdir" to specify a path. Which value would take precedence while pega forms the index files?
- That setting is applicable for Upgrades and should point to the directory where index files reside.
What is the significance of "initialization/explicittempdir" value in the prconfig file?
- ExplicitTempDir generally refers to the explicit temp directory used by the Pega application. However it's not in prconfig.xml, but defined somewhere in the application server (context.xml for Tomcat for example).
While performing any search in DEV portal, a SOAP call with URL in the SearchSoapURI DSS is being used. What is this for?
My question is do we need to specify this row in a SINGLE node environment?
- This specific behavior will vary by version. It may auto populate the fields when the first node starts after installation and indexing can just be enabled, but if that's not the case, then yes one row needs to be populated. In later versions by default, if the first node that starts does not have indexes built on it the indexes will start to building automatically. (Can be disabled via JVM argument)
If we don't give any path where would the index files be generated?
- The default path I believe is a "PegaSearchIndex" directory in the Pega temp directory.
There is a DSS "indexing/explicitindexdir" to specify a path. Which value would take precedence while pega forms the index files?
- That setting is applicable for Upgrades and should point to the directory where index files reside.
What is the significance of "initialization/explicittempdir" value in the prconfig file?
- ExplicitTempDir generally refers to the explicit temp directory used by the Pega application. However it's not in prconfig.xml, but defined somewhere in the application server (context.xml for Tomcat for example).
While performing any search in DEV portal, a SOAP call with URL in the SearchSoapURI DSS is being used. What is this for?
- I'm not sure how much it comes into play for a single node environment, but in a multi-node environment this would be used to contact a node that is hosting the indexes.