Hi M, The simple architecture for Elastic Search that "just works" is to have it live inside of tomcat/JVM. Elastic Search calls that a Node Client. https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#node-client
You don't need to deploy this as a webapp, it lives inside of tomcat/JVM, I'm not sure. But when DSpace API starts it, it serves requests normally like elastic search in any other configuration. https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/statistics/ElasticSearchLogger.java#L598-L602 The external service is a Transport Client. You explicitly create a daemon on some server, listening on port 9200. The transport client route is useful for larger instances, with years of data, as you could have a dedicated server with lots of ram/cpu, and it will handle the load. A similar optimization to having an external / dedicated DB server or web server. If you want Elastic Search statistics on 1.8.x, it wasn't officially contributed to 1.8.x, it was added in DSpace 3.0. However, it was originally developed for an instance on 1.8.x though, Ohio State University Knowledge Bank <https://kb.osu.edu>. https://github.com/osulibraries/DSpace/tree/osukb/dspace-stats/src/main/java/org/dspace/statistics I think it would be easier to just upgrade your instance of DSpace, and then you get this feature, but you could try to backport it. My quick primer on Elastic Search Statistics for DSpace is that, in elastic search, data goes into an index/type, so typically dspace/stats (we only have statistics for DSpace in Elastic Search, it doesn't provide search/discovery). Data gets written as rows, its a nosql data store, so there is no need for a schema, but you can define a schema. Most queries to it are as facets. Date/Text Histograms, etc. I gave a talk on it a few years ago: http://or2013.net/sessions/usage-statistics-powered-elastic-search/ The core pieces of code for DSpace+ElasticSearch is: DSpace-API ElasticSearchLogger, and ElasticSearchEventListener https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/statistics XMLUI Statistics Aspect https://github.com/DSpace/DSpace/tree/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/statisticsElasticSearch It is helpful to understand that usages of objects in DSpace are considered EVENTS. And the EventListener is able to do a series of things when listening to events. i.e. Write a usage to SOLR Statistics, Write to dspace.log, Write a usage to Elastic Search statistics. ________________ Peter Dietz Longsight www.longsight.com pe...@longsight.com p: 740-599-5005 x809 On Thu, May 28, 2015 at 11:23 AM, Tim Donohue <tdono...@duraspace.org> wrote: > Hi, > > At this time, Elastic Search is only used as an alternative way to track > download/access/usage statistics (for XMLUI only). > > https://wiki.duraspace.org/display/DSDOC5x/Elasticsearch+Usage+Statistics > > However, this feature is disabled by default. DSpace provides two > options for internally tracking usage statistics: Apache Solr and > Elastic Search. By default, Apache Solr is utilized, as DSpace uses > Apache Solr also for all searching/browsing within the system. > > - Tim > > On 5/27/2015 8:05 PM, Maatari wrote: > > Hi, > > > > would anyone be able to briefly explain how is ElasticSearch integrated > > with Dspace? > > > > I red in a forum somewhere that the integration followed 2 approaches > > > > 1 - *As part of the Dspace deployment in tomcat.* This is what the > author of > > the post refers to as: *the Dspace-elasticSearch out-of-the box > > integration*. The problem with that statement is that I can not see in > the > > source of Dspace, any WebApp (such as the one for SOLR) from which the > > deployment would happen. The Bottom line is, I cannot see a code that > would > > starts or deploy it. > > > > 2- *As an external Service deployed by a third party.* Some cfg file > seems > > to attest that. > > > > > > I have a particular interest in the out-of-the box approach, that is, the > > approach in which elastic search would come shipped with Dspace. > > > > Could someone quickly explain how it works, and where to look to see it. > > > > Many thanks, > > > > -M- > > > > > > > > -- > > View this message in context: > http://dspace.2283337.n4.nabble.com/How-does-the-ElasticSearch-Dspace-integration-is-set-up-tp4678065.html > > Sent from the DSpace - Tech mailing list archive at Nabble.com. > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > DSpace-tech mailing list > > DSpace-tech@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
