Reply To: Engine to Weblogic connection – getting rid of MQ Series

[Osmand Christian]

Amy,

I am still working on this but if you have some time take a look at this.

This one is “topic”: http://www.oreilly.com/catalog/javmesser/chapter/ch02.html

Are you interested in “topic” or “queue” JMS client implementation?

Modification of this program (URL above) should get what you want – if you are looking for a “topic” communication.

A tricky way of accomplishing the task you asked (after state 11) is to kill the message after using the Java JMS client request to the Java Application. This has to be done in a custom way through Cloverleaf as it doesn’t provide a built in interface for JMS. There are other ways to do this too. If there is anyone who can do some java coding you could use Multithreading capability of Java and pass messages to JMS. In this case, you can send the data out of the engine (tcp/ip) to a Java based Multithread program and allow java to handle the rest of the work.

Do you also want to get a reply back from the Java Application? In that case we have to do something different. One way to do that is to send the reply to cloverleaf on a different port and keep a multithread connection waiting to receive any messages on the Cloverleaf side. This architecture is something I have in production now for SOAP replies and so I am sure we can do that.

I hope this helps..

Osmand C.

Dept. Health & Human Services,

State of North Carolina