Hi Shay,
In our project we receive documents which we want to index from a queue (IBM
MQ server) and it will be nice to use JMS rather than using proprietary
class. Could you please advise as to how I can get this working using the
Plugin api and does elasticsearch provide JNDI, JMS related service?
Hi Shay,
In our project we receive documents which we want to index from a queue
(IBM MQ server) and it will be nice to use JMS rather than using proprietary
class. Could you please advise as to how I can get this working using the
Plugin api and does elasticsearch provide JNDI, JMS related service?
Hi Mahendra,
In case of JMS we lookup for connection/destination factories over a JNDI,
So how we can achieve this in ES server?
OR
Do we maintain our own connection/destination factories within the plugin?
Hi Shay,
In our project we receive documents which we want to index from a queue
(IBM MQ server) and it will be nice to use JMS rather than using proprietary
class. Could you please advise as to how I can get this working using the
Plugin api and does elasticsearch provide JNDI, JMS related service?
I suggest you start with the basics, don't write an elasticsearch plugin,
just write a standalone code registers with JMS and index data it receives.
Once you have that, then you can choose if you want to make it into a River
in elasticsearch, or run it yourself.
Hi Mahendra,
In case of JMS we lookup for connection/destination factories over a JNDI,
So how we can achieve this in ES server?
OR
Do we maintain our own connection/destination factories within the plugin?
Hi Shay,
In our project we receive documents which we want to index from a queue
(IBM MQ server) and it will be nice to use JMS rather than using proprietary
class. Could you please advise as to how I can get this working using the
Plugin api and does elasticsearch provide JNDI, JMS related service?
On Sat, Sep 17, 2011 at 3:36 AM, Shay Banon kimchy@gmail.com wrote:
I suggest you start with the basics, don't write an elasticsearch plugin,
just write a standalone code registers with JMS and index data it receives.
Once you have that, then you can choose if you want to make it into a River
in elasticsearch, or run it yourself.
Hi Mahendra,
In case of JMS we lookup for connection/destination factories over a JNDI,
So how we can achieve this in ES server?
OR
Do we maintain our own connection/destination factories within the plugin?
Hi Shay,
In our project we receive documents which we want to index from a queue
(IBM MQ server) and it will be nice to use JMS rather than using proprietary
class. Could you please advise as to how I can get this working using the
Plugin api and does elasticsearch provide JNDI, JMS related service?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.