Dynamic JMS endpoints revisited

This is a long overdue update to a previous post on achieving dynamic JMS endpoints in WebSphere ESB. As several people have commented, WebSphere ESB 6.2 added support for dynamic endpoints for all of the bindings types as documented in the InfoCenter. A couple of points to note:

  1. The syntax of the endpoint URI used for the JMS bindings uses JNDI names to refer to the resources and is therefore not truly dynamic in the sense that JMS destinations need to have been pre-configured for all of the messaging provider destinations to which you might want to send.
  2. For a native MQ binding, you can currently only modify the queue dynamically and not the queue manager to which you can connect.

Comments are closed.