D
dbeavon
Guest
Thanks for helping me dig into the reasoning for this. I didn't realize that there was a difference in the features supported by broker connect vs client connect. But we had found many other great benefits in using client connect, as I had hinted at earlier. The prerequisites are fewer, management is easier, system is overall more resilient (ie. no system-wide outages, and feels like one less point of failure than broker connect), etc. Regarding prerequisites for client connect: This is off the top of my head, and I don't know if this is 100% technically accurate but it feels like the prerequisite "client connect" are simply to do as follows: ensure that a version of the Java runtime installed that is compatible with your JMS client libraries, put the JMS client libraries in the classpath, optionally tweak [Adapter.CC] in JavaTools.properties if needed, and we're off ! ... (... this is based on my recollection of the the Sonic MQ provider, and there may be a bunch more setup work I'm overlooking for your new generic JMS) I think it is normally possible for an ABL solution to be deployed with client-connect" functionality *without* needing any configuration overhead or system-level admin privileges. It doesn't feel right that any ABL can't simply connect directly to a JMS provider without jumping thru the intermediate hoops. The existence of a "JMS adapter" in your Progress Explorer Framework" feels extremely bureaucratic. I expect it is an optimization (reduces the initial launch time of the "symbiont ", and reduces memory utilization), but for us it certainly introduced more problems than it solved. I wouldn't want to go back to that again. If/when there needs to be any optimizations, we can do them on our own (eg. determine when ABL client programs shouldn't talk directly to a broker but go thru a database table first). We would be very happy to start testing your generic JMS functionality right away, if we had some prospect of doing "client connect" once we get to production. We have been looking for a way to get out of the Sonic MQ product for quite a while.
Continue reading...
Continue reading...