ES and JMS


Below are the queries regarding JMS and MOMs in context with wm…
1)we know that ES 5.0 provides support for JMS. In a project circumstance/design scenario when is that we go for implementing jms with ES??
2)To have a better idea, can anyone list the differences between MOM(message oriented middlewares) and EAI products like webMethods, seeBeyond?

You can always develop integration components (using webMethods developer or Enterprise Integrator) that allow you to do a Req-Reply and Pub-Sub with Enterprise broker. These integration components will work only with webMethods broker. If for some reason, your enterprise decides on changing your messaging system (from webMethods to MQ or Tibco or whatever for whatever reason), your entire code base becomes not usable. It is recommended to go with JMS compliant code base if you want to develop non-proprietary EAI code base that can be used with multiple messaging systems (aka JMS providers). The development of source and target side components using tools like webMethods developer is fairly simple (using GUI based development tools) instead of developing JMS compliant clients (essentially java code) that do the same when it comes to JMS.

Hi Nani :

My previous message addresses only part 1 of your question.


MqM Series provides a async queueing methodology but does not support Data transformation, cloning, or logging. These is probably more but those are the big one. Those functions are provided or extended in a Distributed Middleware package such as webMethods. There are middleware systems that are layered on top of MQM that do provide that functionality but they focus on MQM as an Interface layer rather then a Broker Service that addresses multiple communication methods such as Flatfiles, EJB’s, and various API technologies.