D
dbeavon
Guest
It is pretty clear when I read the new 11.6 docs that the generic JMS support is limited to "broker connect": "Note: Generic JMS Adapter supports only the BrokerConnect mode." Can someone help me understand why the "client connect" mode isn't supported yet and whether it is likely to be supported some day? I thought "client connect" was analogous to "broker connect" and simply launched a "symbiont" adapter for each ABL client (instead of having to work thru a centralized "adapter-broker" within the bureaucratic "Progress Explorer Framework"). IMO, the act of sending a message to a remote JMS provider should be as simple as possible. While its not perfect, the "client connect" mode of sending and receiving messages is conceptually a lot more simple and easy to manage than broker connect. When connecting directly to a JMS provider from the ABL client via "client connect", there is one less "adapter/broker/middle-manage-er" that needs to be configured and maintained. And ultimately we end up with one less point of failure (a very, very good thing for messaging). Many years ago when we transitioned our Sonic MQ messaging from "broker connect" to "client connect" we saw overall messaging failures decrease dramatically. And when there are occasionally failures (in the JMS-aware "symbionts" ), they are NOT SYSTEM-WIDE (!!!) but local to specific ABL client(s). It means fewer urgent calls to restart the "Progress Explorer Framework (adapters/brokers/etc). With "client connect", any JMS-related problems that come up are normally solved on their own by quitting the ABL client (triming servers on the app server agents, or whatever). I am very hopeful that we will eventually see a "client connect" option for generic JMS messaging. This will allow us to finally migrate away from the pricey Aurea product.
Continue reading...
Continue reading...