Loading ...

Elasticsearch Installation | Communifire Documentation

Home » communifire documentation » Wiki » Documentation » On-Premise Installation » Elasticsearch Installation

Comments (5)

   
nickmcelligott

FYI: The Elastic Search Dynamic Properties are under Search Settings (not core) and there is no ElasticsearchServiceName key, but it wasn't needed.

8/5/2016 01:05 AM
 · 
by
   
vivek-thakur

Thanks  Nick Mcelligott for pointing these issues, we have fixed them and updated the wiki. Thanks again :)

8/5/2016 05:55 AM
 · 
by
   
anubhavshah

In our specific implementation, we could not depend on static IP (its possible that it can change as we drop and build servers on the fly). So i had to include the following to get it to work:

network.bind_host: 0.0.0.0
network.publish_host: <your external address>

10/14/2016 07:54 PM
 · 
by
   
anubhavshah

Is the JDK necessary, or can the JRE suffice? Currently i have it working with JRE. But we do have an issue where subsequent updates to JRE is not updating the JAVA_HOME variable. How are updates handled for even the JDK?

2/9/2017 07:49 PM
 · 
by
   
vivek-thakur

JDK is recommened.

2/27/2017 04:51 AM
 · 
by
   
agandha

How do you use this to create a search solution that search and index across the network on different servers on a load balanced web farm? 

10/26/2017 06:16 PM
 · 
by
   
agandha

Is it compatible with Elastic Search 6? Please advise.

3/8/2018 11:59 PM
 · 
by
   
mtrujillo

Communifire is not compatible with any other versions of Elastic Search besides 2.3. In the upcoming Communifire version (6.0), Communifire will be compatible with Elastic Search 6.

3/9/2018 02:52 AM
 · 
by
   
mtrujillo

Elastic Search can act as a central service for search data, you would host Elastic Search on it's own server or you can use a 3rd party Elastic Search hosting provider such as Amazon Web Services to store your search data. Once the service is setup, you would configure Communifire(on each web server in your web farm) to connect to the URL of your service in System Properties > ElasticsearchServer. You would need to study Elastic Search documentation to learn how to populate the service with non-Communifire content. I'm not sure if Communifire can retrieve and link to non-Communifire content stored in Elastic Search,  Vivek Thakur would be the best person to answer this. Can you please chime in Vivek?

3/9/2018 03:04 AM
 · 
by
   
vivek-thakur

You are right Matt. Elasticsearch settings need to be configured for every server on the web farm. Communifire cannot link to non-Communifire Elasticsearch data.

3/9/2018 03:24 AM
 · 
by
   
agandha

This link is broken:

3/8/2018 09:26 PM
 · 
by
   
mtrujillo

Looks like Elastic took down the page, I've updated the link.

3/9/2018 02:51 AM
 · 
by

Pages

Intranet Software