| Author |
Message
|
| toadie |
 Posted: Tue Jun 14, 2005 1:55 pm Post subject: MQSeries newbie |
 |
|
Newbie
Joined: 14 Jun 2005
Posts: 5
|
Hi
We have a customer who wants us to connect to their MQSeries box. We are primarily Java/JMS (non WebSphere) shop. Our preference is to use a standard JMS client to submit / pull message out of MQSeries.
Does anyone have links to documentation on how to connect to MQSeries via standard J2EE JMS implementation?
Additional questions that I have are:
- what authentication model does MQSeries support when connecting via JMS client? (standard userid/password, Certificate, etc..)
- is the transport layer secure (e.g. via ssl) ?
- any gotchas in such an implementation?
Thanks. |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Jun 14, 2005 2:08 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The documentation link on the top of this page will take you to all the manuals.
You can take a look at Using Java/JMS manual on how to implement JMS against MQ as the JMS providers.
| Quote: |
| what authentication model does MQSeries support when connecting via JMS client? (standard userid/password, Certificate, etc..) |
You can use whichever you want to
| Quote: |
| - is the transport layer secure (e.g. via ssl) ? |
If you want you can secure it using SSL |
|
| Back to top |
|
|
| toadie |
| Posted: Tue Jun 14, 2005 6:13 pm Post subject: |
|
|
Newbie
Joined: 14 Jun 2005
Posts: 5
|
Hello
[quote="vennela"]The documentation link on the top of this page will take you to all the manuals.
You can take a look at Using Java/JMS manual on how to implement JMS against MQ as the JMS providers.
[quote]
unfortunately, the documentation link above points to a non-existing page. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 14, 2005 6:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| toadie wrote: |
Hello
| vennela wrote: |
The documentation link on the top of this page will take you to all the manuals.
You can take a look at Using Java/JMS manual on how to implement JMS against MQ as the JMS providers.
|
unfortunately, the documentation link above points to a non-existing page. |
Check out the cross platform Using java at
http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/index.html
As well if you are concerned about security use SSL.
And do a search on this site on the subject security hole...
Enjoy  |
|
| Back to top |
|
|
| toadie |
| Posted: Thu Jun 16, 2005 8:25 am Post subject: |
|
|
Newbie
Joined: 14 Jun 2005
Posts: 5
|
fjb_saper
Thanks for the link. I was hoping to find a way to talk to MQSeries via Java using a pure J2EE method (non com.ibm.mq.* classes), but unable
to find those info on the provided link.
I've read somewhere that MQSeries , now known as WebSphereMQ, supports a JMS based messaging interface. However, if the classes com.ibm.mq.* are required then I'd still be locked into a proprietary implementation.
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 16, 2005 8:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
All JMS implementations are "propriatary", unless they are open source. And even then, in your sense, they are still "proprietary".
That does not mean your code has to be tied to a particular implementation. That's the whole point of "standards" and using interfaces versus implementations.
If you write your code to be only and fully compliant to the JMS specification, then whatever JMS provider you use, the code should function. And you should be able to implement a WebSphere MQ JMS provider without making your code specific to that provider.
You will, however, have to install and configure WebSphere MQ, and your JMS runtime environment will have to link against the vendor specific implementation classes. This is similar to JDBC.
There is no such thing as the standard J2EE JMS implementation. There are many implementations that meet the J2EE JMS standard.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| toadie |
| Posted: Thu Jun 16, 2005 9:28 am Post subject: |
|
|
Newbie
Joined: 14 Jun 2005
Posts: 5
|
Jeff
What i meant was that I'd rather not have a dependency on com.ibm.mq.*
As far as the implementation of the JMS Server, yes, they are all proprietary internally, however, most would comply to JMS 1.0 or 1.1 specifications at the external API level.
| jefflowrey wrote: |
All JMS implementations are "propriatary", unless they are open source. And even then, in your sense, they are still "proprietary".
That does not mean your code has to be tied to a particular implementation. That's the whole point of "standards" and using interfaces versus implementations.
If you write your code to be only and fully compliant to the JMS specification, then whatever JMS provider you use, the code should function. And you should be able to implement a WebSphere MQ JMS provider without making your code specific to that provider.. |
What you are saying here is that it is possible to write a JMS Client that relies purely on javax.jms.* package and could communicate with MQSeries?
| jefflowrey wrote: |
| You will, however, have to install and configure WebSphere MQ, and your JMS runtime environment will have to link against the vendor specific implementation classes. This is similar to JDBC. .. |
If i am only interested in writing a JMS client to submit & pull msgs out of MQSeries, i wouldn't think I'd need WebSphere MQ do i?
| jefflowrey wrote: |
| There is no such thing as the standard J2EE JMS implementation. There are many implementations that meet the J2EE JMS standard. |
|
|
| Back to top |
|
|
| toadie |
| Posted: Thu Jun 16, 2005 9:42 am Post subject: |
|
|
Newbie
Joined: 14 Jun 2005
Posts: 5
|
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jun 16, 2005 9:54 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
|
|
