I'm not sure what your goals are. Are you saying you're sending messages from a web server to a back-end database? Why wouldn't your web server just update the database itself?
In any case, take a look at the Wiki: http://www.jboss.org/wiki/Wiki.jsp?page=JBossMQ
Thanks for your reply.
I do not have direct access to this database, as it is not my main DB.
My goal is to be able to put a message onto a que (from my web server) and then allow it is be picked up by a custom server running on the database machine.
This is where IBM's MQ would come in as it would guarantee the delivery + collection and will allow me to wait until I get a response etc...
MQ Server1 <------------------------ Custom Server Process (Database)
And I was wondering if JBoss could do this instead of me having to buy a IBM MQ licence, which costs a lot!!!
Here's my first stab at designing such a thing:
1. Create a JBoss server on the database side. Create a queue and MDB. Have the JMS messages in the queue go into your database, not HSQLDB.
Currently, you need an JDBC XA datasource (e.g. Oracle, DB/2) to do 2-phase commit. Other DBs would work, but you may not have 100% transaction integrity.
2. You can deploy Tomcat or JBoss on the webserver side. Either way, it needs to be same version. Connect to the queue on the back-end. Use a temporary queue to get your ack. message back.
3. Fire away.
Cheers for your reply.
I think that I will just have to give JBoss a try and see whether or not it works for me. So I guess reading all of the documentation will get me off to a good start :) at least something to read while on the train to work.
All I need to make sure is that JBoss allows me to:
a: Let me put a message on a queue and then wait for a reply (real-time).
b: Put a message on the queue and not wait e.g. no reply needed.
c: Put a message on a queue and then for a action to be performed e.g. send an email, sms (to the specified problem, within the message) etc...
From what I have read so far JBoss looks like a really cool project.