Elasticsearch on an existing jetty container


(Srividhya Umashanker) #1

I understand that there is a jetty plugin for elasticsearch, which enables
us to run ES in a jetty container instead of using Netty for HTTP.

Is there a way for us to bundle elasticsearch and run it on an existing
jetty instance, instead of spawning a new jetty instance?

The idea is for us to use a wrapper REST service (which contains business
model and logic), that talks to elasticsearch for indexing and searching
capabilities.
We may want to interact with ES cluster using the Java Client from the
wrapper REST service

For the monitoring and administration, we may want to enable HTTP in a
single node, and run it on the container where the wrapper REST service
exists.

Suggestions or experiences will greatly help!

Thanks

-Vidhya

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f5c53302-5eec-4b85-b6dd-8c750690b497%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #2

Look at the wares plugin. It enables building an ES node as a war that can
be deployed into a webapp container like Jetty, Tomcat, Glassfish, or
Wildfly, with executing a wrapper REST service, for example with Jersey.

I submitted some useful addings for ready-to-deploy

Of course you have to modify that for your favorite war deploy environment
and solution.

Jörg

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGxQ6TbFsA5rAJAwFScqmoqcqCcRYmEPFtsFZycq5D4pw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Srividhya Umashanker) #3

Do you have any documentation on this?

Look at the wares plugin. It enables building an ES node as a war that can
be deployed into a webapp container like Jetty, Tomcat, Glassfish, or
Wildfly, with executing a wrapper REST service, for example with Jersey.

https://github.com/elasticsearch/elasticsearch-transport-wares

I submitted some useful addings for ready-to-deploy
https://github.com/elasticsearch/elasticsearch-transport-wares/pull/8

Of course you have to modify that for your favorite war deploy environment
and solution.

Jörg

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fa4405a2-a091-403c-b2e1-9d256d0be587%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #4

Get wares plugin source, apply my patch
https://github.com/elasticsearch/elasticsearch-transport-wares/pull/8.patch
and enter "mvn war" for maven build to get started.

Jörg

On Fri, Jan 10, 2014 at 11:17 AM, Srividhya Umashanker <
srividhya.umashanker@gmail.com> wrote:

Do you have any documentation on this?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH3caGSGiWbkh6yG58wzDKprTGM2CYa1%3D0PHrjnYeWhVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #5