| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Support for generic JMS Input and Output nodes |
« View previous topic :: View next topic » |
| Do you plan to integrate WMQI with JMS applications? |
| Yes |
|
90% |
[ 9 ] |
| No |
|
10% |
[ 1 ] |
|
| Total Votes : 10 |
|
| Author |
Message
|
| kolban |
 Posted: Mon Oct 07, 2002 8:48 am Post subject: Support for generic JMS Input and Output nodes |
 |
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
WMQI today has output capabilities via a number of nodes. Primarily, this is the MQOutput node which is tightly coupled with MQSeries.
The purpose of this post is to solicit feedback and desire for a couple of new nodes.
These nodes would send and retrieve messages from JMS destinations. Tentaively, these nodes would be called the JMSInput and JMSOutput nodes. They would be the functional and logical equivalents of the MQInput and MQOutput nodes.
The JMS nodes would not be bound to a particular JMS provider implementation but would work just fine with both IBM and non-IBM JMS implementations.
So ...
1. Do you need JMS and WMQI support?
2. Would these nodes be of use to you?
3. Which of the following support options would be acceptable:
- No support (asis), no source code
- No support (asis), with source code, IBM maintained source
- No support (asis), with open souce, community maintained
- IBM Formal Support
4. What time frame would you need this function? |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Oct 07, 2002 9:48 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi Neil,
Event though I am not using JMS I voted for "Yes". I think it is a great idea to have JMS Input and Output nodes. I've seen people having problems while outputting JMS message.
I can answer to 3rd question only,
3. - No support (asis), with open source, community maintained
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| howardfw |
| Posted: Mon Oct 07, 2002 9:57 am Post subject: |
|
|
Newbie
Joined: 08 May 2002
Posts: 3
Location: Minneapolis, MN
|
Neal,
Great idea. I would prefer Formal IBM support with the new nodes.
Howard |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Oct 08, 2002 2:09 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
We use JMS and WMQI together with MQinput and MQOutput nodes, but I'm not sure what new functionality you are thinking these new nodes would provide. Can you elaborate? Currently WMQI does not rely on JMS messages being from an IBM source, or does it?
Where does WebSphere MQ Event Broker fit in here?
("Provides direct mode of connection for Javaâ„¢ Messaging Service (JMS) clients for nonpersistent messaging--providing high scalability")
I guess I am missing the point, so what would you have JMSInput/JMSOutput nodes do?
Thanks,
Vicky |
|
| Back to top |
|
|
| kolban |
| Posted: Tue Oct 08, 2002 4:55 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Hey Vicky, how's yer sel, ya doin aw right then hen?
(Sorry, practicing Glaswegian)
The JMSInput node would wait for the arrival of a message on either a JMS queue or a JMS topic destination. On receipt of a message, the JMSInput node would then retrieve the message and build an appropriate WMQI message tree based on its contents. The message tree would then be propagated onwards to other WMQI nodes.
The JMSOutput node would take a message tree and make appropriate JMS calls to either send or publish the serialized (based on configuration of the node) contents of the message tree to the JMS destination.
Both the JMSInput and JMSOutput nodes would look and feel like JMS and not like MQSeries. They would have attributes/properties that looked like JMS attributes. For example, the queue/topic attributes would be defined as JNDI paths to retrieve the Queue or Topic managed object from JNDI namespace.
Since the proposed JMSInput and JMSOutput nodes would be implemented in Java and use only JMS APIs, they would work with any implementation of JMS ... include MQSeries, MQ Event Broker, ... others from IBM ... and others from 3rd parties. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Oct 08, 2002 5:05 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Thanks. I understand now.
We probably wouldn't use it here since we have different teams looking after JMS and MQ so we are happy to let the web side do the JNDI lookup and they are responsible for putting the message to the right queue or publishing and subscribing to the right topic.
However I can see advantages and vote yes with "No support (asis), with open souce, community maintained".
Cheers, Vicky |
|
| 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
|
|
|
|
