03 August 2005

IBM and JMS-to-.NET interop

IBM's .NET Managed client for JMS

Today I received a comment on a prior entry of this blog. It is noteworthy so I thought I would re-post it here.

As previously mentioned in a previous blog entry (JMS Interop, revisited), there is a demand for .Net and JMS interop.

IBM Message Service Client for .NET (informally known as XMS) has now started an open Beta programme.

XMS is a non-Java implementation of the Java Message Service (JMS) API, currently implemented to work with the IBM WebSphere Messaging portfolio. Specifically, it is a fully managed .NET API that can be used by applications to send and receive JMS messages via IBM WebSphere Business Integration Brokers over Real-time Transport or via the default messaging provider within IBM WebSphere Application Server v6.

We welcome you to download XMS from: http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=message,

Try it out, and give us your feedback via: news://news.software.ibm.com/ibm.software.websphere.mq.beta.

Cool!

First question I have is, does it work with plain old WebSphere MQ?   I don't know what the term "WebSphere Business Integration Brokers" includes. I think there are some premium products like WBI Server, and WBI Message Broker and WBI Event Broker, and I guess all of those are included in "WBI Brokers". But what about just MQ? [ note added 4 Aug 2005 : The readme for this XMS.NET thing apparently states NB. Interaction with IBM WebSphere MQ is not supported in this release but is currently under development. So I think you need one of the higher-end MQ or WBI products, for now. ]

Anyone trying this out?  I am interested in feedback, too!  Comment on the blog or contact me privately.  I'd love to hear if this thing is useful. 
Filed under: , , , ,
 

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# All About Interop said:
TIBCO apparently has implemented the JMS API in .NET. 

TIBCO Enterprise Message Service...
03 August 05 at 11:58 AM
# IanB said:
XMS for .Net currently does not support WebSphere MQ, but we are working on it. We expect to have early releases of that support later this year, completing the work early next year.

You are correct with your definition of "WebSphere Business Integration Brokers". The IBM Message Service Client for .Net supports connection to a [WebSphere Business Integration (WBI) Event Broker|http://www.ibm.com/software/integration/wbieventbroker/] using the real-time transport. [WBI Message Broker|http://www.ibm.com/software/integration/wbimessagebroker/] builds on WBI Event Broker, while [WBI Server|http://www.ibm.com/software/integration/wbiserver/] is a product suite which incorporates WBI Message Broker. Therefore XMS .Net currently supports all these products.
03 August 05 at 12:46 PM
# IanB said:
Tried to post this a couple of days ago, but hasn't appeared.

We are currently working on support for WebSphere MQ and expect to have early releases of that support available later this year, completing the work early next year.

You are correct with your definition of "WebSphere Business Integration Brokers". The IBM Message Service Client for .Net supports connection to a [WebSphere Business Integration (WBI) Event Broker|http://www.ibm.com/software/integration/wbieventbroker/] using the real-time transport. [WBI Message Broker|http://www.ibm.com/software/integration/wbimessagebroker/] builds on WBI Event Broker, while [WBI Server|http://www.ibm.com/software/integration/wbiserver/] is a product suite which incorporates WBI Message Broker. Therefore XMS will support all these products.
05 August 05 at 6:09 AM
# All About Interop : JMS Interop, revisited said:

PingBack from http://blogs.msdn.com/dotnetinterop/archive/2005/04/20/jms-interop-revisited.aspx

09 August 07 at 8:33 PM

Leave a Comment

Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.

(required) 
(optional)
(required) 
Page view tracker