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.
On Thu, Sep 15, 2011 at 6:54 PM, lalit mishra email@example.com wrote:
In case of JMS we lookup for connection/destination factories over a JNDI,
So how we can achieve this in ES server?
Do we maintain our own connection/destination factories within the plugin?
On Tue, Sep 13, 2011 at 10:58 AM, Mahendra M firstname.lastname@example.org wrote:
Maybe you can have a look at the RabbitMQ plugin and use that to build the
JMS river. IIRC, JMS and AMQP are pretty similar.
On Tue, Sep 13, 2011 at 6:51 AM, lalit mishra email@example.com:
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?