# Elasticsearch on an existing jetty container

**URL:** <https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192>\
**Category:** Elasticsearch\
**Created:** [January 10, 2014, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192 "2014-01-10T08:33:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Srividhya\_Umashanker](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@Srividhya\_Umashanker](https://discuss.elastic.co/u/Srividhya_Umashanker)\
**Post date:** [January 10, 2014, 8:33am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192/1 "2014-01-10T08:33:22Z")

</div>

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](mailto: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](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](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 10, 2014, 9:14am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192/2 "2014-01-10T09:14:26Z")

</div>

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.

> **[elastic/elasticsearch-transport-wares](https://github.com/elastic/elasticsearch-transport-wares)**
>
> elasticsearch-transport-wares - Servlet transport for Elasticsearch

I submitted some useful addings for ready-to-deploy

> <https://github.com/elastic/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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGxQ6TbFsA5rAJAwFScqmoqcqCcRYmEPFtsFZycq5D4pw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGxQ6TbFsA5rAJAwFScqmoqcqCcRYmEPFtsFZycq5D4pw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Srividhya\_Umashanker](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@Srividhya\_Umashanker](https://discuss.elastic.co/u/Srividhya_Umashanker)\
**Post date:** [January 10, 2014, 10:17am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192/3 "2014-01-10T10:17:21Z")

</div>

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.
> 
> [GitHub - elastic/elasticsearch-transport-wares: Servlet transport for Elasticsearch](https://github.com/elasticsearch/elasticsearch-transport-wares)
> 
> I submitted some useful addings for ready-to-deploy  
> [Create a ready-to-deploy es.war webapp for better out-of-the-box experience by jprante · Pull Request #8 · elastic/elasticsearch-transport-wares · GitHub](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](mailto: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](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](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 10, 2014, 10:43am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192/4 "2014-01-10T10:43:06Z")

</div>

Get wares plugin source, apply my patch  
[https://github.com/elasticsearch/elasticsearch-transport-wares/pull/8.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](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH3caGSGiWbkh6yG58wzDKprTGM2CYa1%3D0PHrjnYeWhVQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH3caGSGiWbkh6yG58wzDKprTGM2CYa1%3D0PHrjnYeWhVQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:57am UTC](https://discuss.elastic.co/t/elasticsearch-on-an-existing-jetty-container/15192/5 "2017-07-06T01:57:26Z")

</div>


