JMS: the confusion BEFORE writing my first Application.

[joel s]

I read in the sun jms doc that jms is the java interface to
Middleware, like MQ series.

Does this mean I actually need MQ series? ITs to expensive. Im
already in the programming world, so this is not a school project. My
boss came to me and told me that he would like to connect to a remote
MQ series machine. With it.

Now I have taken the channel and decided to write something at my desk
with out connecting to the remote mq. I mean, even if i didnt have to
do this project, i would still like to learn it.

I really thought that j2ee already had a queing facility built in so I
didnt need to buy mq series.

If i do need a middle where queue piece, then are there any free ones.

I thought i could go into the j2ee command line tool and just set up
the queues the way they have it in the example

Can you straighten out my confusion?

jodasi

 

[Michael Borgwardt]

I read in the sun jms doc that jms is the java interface to
Middleware, like MQ series.

Does this mean I actually need MQ series?

No, you need a messaging service that has a JMS-conforming interface.
MQSeries is one of these.

ITs to expensive. Im
already in the programming world, so this is not a school project. My
boss came to me and told me that he would like to connect to a remote
MQ series machine. With it.

Now I have taken the channel and decided to write something at my desk
with out connecting to the remote mq. I mean, even if i didnt have to
do this project, i would still like to learn it.

I really thought that j2ee already had a queing facility built in so I
didnt need to buy mq series.
If i do need a middle where queue piece, then are there any free ones.

A full J2EE server is required to have one, so the J2EE model implementation
should indeed include a JMS facility. Same with JBoss.

However, testing your program only against these might mean that you'll run
into unexpected problems when you run it against the MQSeries server. I'm
not sure how much room the JMS spec leaves for vendor specific quirks.
Try to assume nothing that isn't explicitly guaranteed by the JMS API
specification.

 

[Will Hartung]

I read in the sun jms doc that jms is the java interface to
Middleware, like MQ series.

Does this mean I actually need MQ series? ITs to expensive. Im
already in the programming world, so this is not a school project. My
boss came to me and told me that he would like to connect to a remote
MQ series machine. With it.

Yes, you'd use JMS to talk to something like MQ.

Now I have taken the channel and decided to write something at my desk
with out connecting to the remote mq. I mean, even if i didnt have to
do this project, i would still like to learn it.

I really thought that j2ee already had a queing facility built in so I
didnt need to buy mq series.

A compliant J2EE system has a JMS supported middleware as part of the
system. JBoss, Suns, Weblogic, etc. all have one.

If i do need a middle where queue piece, then are there any free ones.

You can download any of the above for free and use them. There are also
projects like OpenJMS which is simply the JMS part of the system (I think
Apache Geronimo uses OpenJMS in their J2EE suite). For example, if you
wanted JMS capabilities in a servlet based app, you could just use OpenJMS
and Tomcat rather than going full J2EE.

I thought i could go into the j2ee command line tool and just set up
the queues the way they have it in the example

Yea, they all are configured differently. It's server specific on how to
setup and talk to the JMS queues.

Can you straighten out my confusion?

Any of the above should get you started, and if your needs are basic, you
shouldn't have any real problems talking to MQ later on. But you will
eventually need to get a JMS provider for MQ (I assume you can get this from
their website, who knows), as each Middleware server has their own interface
wrapped with JMS. There are differences between implementations, but if you
only need the most basic of functionality (such as publishing a TEXT
message), that's will pretty much always work. As you look towards the more
advanced capabilties, you'll see differences.

Regards,

Will Hartung
([email protected])

 

[joel s]

thank you for your help Micheal.

Let me ask this then? which free/servers tools have the messaging
queuing services buit in?

 

[Sipayi]

Let me ask this then? which free/servers tools have the messaging
queuing services buit in?

There are many messaging servers.
http://directory.google.com/Top/Com...nguages/Java/Server-Side/Java_Message_Service
Some are downloadable to try.

Assumption: You want to read MQ messages through via JMS queues.
Disclaimer: My knowledge about this integration is an year old.

Integrating MQ with J2EE is a little involved a task. I have done it
with WebLogic, and there are various options one has to try/figure out
before arriving at a solution. MQ use to have a separate component
(MQJMS) then, do not know if it is still the option.
I would propose a divide and conquer strategy. If you know what is the
format of the message you need to handle, then
1. Try posting that message into the JMS queue, and have your
MDB/etc., handle it appropriately. You can write a JMS client for
this in plain Java. This can be done on your desktop. This is the
easiest portion
2. Figure out the most appropriate solution to integrate MQ with
the JMS server. (Ensure transactions are handled, etc., XA was not
supported by MQJMS if MQ and WLS were on different servers when I
worked with, think now it does)
3. Find out the format the message appears when received from MQ,
translate/manipulate the portion of code developed in step (1)
to understand this message .

HTH,
Siplin

 

[Michael Borgwardt]

thank you for your help Micheal.

Let me ask this then? which free/servers tools have the messaging
queuing services buit in?

As I said: the J2EE release from Sun and JBoss.

 

[joel s]

As I said: the J2EE release from Sun and JBoss.

thank you all for your help. I appreciate your time.