| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Publish/Subscribe and MQSI |
« View previous topic :: View next topic » |
| Author |
Message
|
| saxofun |
 Posted: Thu Nov 14, 2002 7:27 am Post subject: JMS Publish/Subscribe and MQSI |
 |
|
Newbie
Joined: 30 Jul 2002
Posts: 5
|
Hello together
Is there a possibility to code a publish/subscribe JMS-Application
that isn't using JNDI? When yes, is there a howto around?
My second Problem is, that I found many howtos with MQ and
Brokersupportpac MA0C. But is there also a hwoto with the
MQSI-Broker instead of the MQ-Broker?
Thanks in advance,
Marc  |
|
| Back to top |
|
 |
| amigupta1978 |
| Posted: Fri Nov 15, 2002 1:47 am Post subject: |
|
|
Centurion
Joined: 22 Jan 2002
Posts: 132
Location: India
|
Hi,
Regarding your second question, I think JMS publish/subscribe should work fine with MQSI broker too. Only difference between the MQ Broker and MQSI broker is that they use different input streams for the publish/subscribe. But these all are at system level so I think u mite not be any trouble.
Rgds,
Amit
_________________
IBM certified MQseries Specialist
IBM certified WMQI Specialist |
|
| Back to top |
|
|
| kingdon |
| Posted: Fri Nov 15, 2002 2:56 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Using JNDI to obtain TopicConnectionFactories and Topics is only a recommendation, not a requirement. If it is more appropriate for a given application you can create these objects in-line, although this will make your code less portable than if you use JNDI. See chapter 10 of the "Using Java" book (somewhat confusingly called the Second Edition, Oct 2002 - I still think of it as version 11) for the basics of creating the factories, chapter 11 for how to create a Topic and chapter 14 for details of the methods on MQTopicConnectionFactory and MQTopic that you can use to configure these objects.
For connecting to MQSI or MQ Event Broker have a look at Appendix D of the "Using Java" book.
Note that that are more differences between MA0C and MQSI/Event Broker than the name of the input streams!
You get the ability to run message selectors on the server, providing greater flexibility in the trade off between client cpu cycles/server cpu cycles and network traffic.
Event Broker features the 'direct' transport, allowing for very high performance, high scalability connections for non-persistent messages.
Regards,
James. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
