This is just some thoughts on the whole thing. At the end the integration via the patchbay seems to have it's limitations, if the OpenJMS server goes down while Dynamo has a pool of connections, things don't work out too well, event to get that far, I had to make a subtle patch to the OpenJMS code. If I were doing a project with ATG and OpenJMS I'd probably take another route and have a custom component that exclusively connected to OpenJMS, opening a session each time a message was sent. Another approach would be have a scheduled component which checked in on the OpenJMS server periodically and ensured that the session pool was ok, and if not, restarted the MessagingManager component. As always comments are welcome! Much of the work needed to do this should be applicable for the integration of ATG Dynamo with other JMS providers such as IBM MQSeries, Open3 Technologies Open3 EMS and Sonic Software SonicMQ. Any JMS might also be used as a bridge JMS between two different application server clusters as well as connecting the application server to some other component. This document is written for those who already have some experience with ATG Dynamo, although it assumes no prior knowledge of OpenJMS. The examples given are for the Microsoft Windows platform, although both components are pure Java and run equally well if not better on UNIX platforms.
|
