The IQ Combined Services (Index and Query) are designed to work with Elastic Search present in the DXD Stack. Index service indexes the data in Elastic Search and Query Service is used to query the data out of the Elastic Search. Both the services operate on the same Elastic Search instance.
Currently, Index Service doesn't support OAuth authentication but ...
The first error shows you are supplying the parameters in the incorrect format.
Hope below steps should work for you -
Make sure you have installed elastic search 5.5 or 5.6 version running.
For windows environment use single hyphen (-). It should be like
.\installElasticSearchIndexes.ps1 -es-host "localhost" -es-port "9200" -es-scheme "http"
In this ...
I noticed in your installation error logs you have wrongly installed SDL Tridion Docs search functionality elasticsearch indexes installation script instead of XO elasticsearch installation script.
Documentation is indeed and it's correct but you have wrongly referred to the installation media folder for the script.
XO Installation script media ...
After Investigating the elastic search logs (path: c:\elasticsearch-7.7.0\logs\elasticsearch-service-x64-stderr.YYYY-MM-dd)
Error "the system property [es.path.conf] must be set" when starting the service registered
Refer to the link for the fix
The fix provided here [#57769] doesn't help since the culprit is not the same variable, I ...
In Sites 9 Regions are newly introduced to structure the content on a page in a better way. So the page is having a new structure now. The idea is while publishing the page we need to handle this region on the SI4T template. You can find the change in the pull request https://github.com/SI4T/SI4T/pull/21 . It will be merged in the next release I guess.
No, You can use the same elastic instance to have two different indexes for docs and sites.
OOTB - IQ-Index and IQ-Query services only supported for Docs.
Note: IQ services won’t work with the SI4T index for sites.
I hope it helps.
It was silly mistake during the deployer config. The XO deployer pipelins configs should have been placed after the Tridion-Commit-TX pipe line, instead I have placed the same at the end. Thanks Brian from SDL support for noticing the same.
A couple of failure points that you can look at for your implementation would be your start up parameters for your deployer to include es-host and es-port highlighted below.
--es.host=10.100.101.52 (Elasticsearch server)
--es.port=9200 (port number of the Elasticsearch)
A quick verification would be to also check if the add-on is deployed ...
Yes. As @Rai mentioned it's already handled in the SI4T refer to that link which rai mentioned in his comment.
In your custom elastic search deployer storage extention code, you can add one more exception catch for elastic search.
catch (ElasticsearchException e)
throw new IndexingException("...