.NET can connect to WebSphere’s built-in JMS

Phil Willoughby of IBM dropped me a line.  Phil apparently works on the XMS stuff, I'm guessing out of IBM's Hursley lab.  Phil sez:

Re: http://blogs.msdn.com/dotnetinterop/archive/2005/11/04/488770.aspx

FYI, XMS can be used to connect directly to the WebSphere App Server embedded JMS system. There is no requirement to have WebSphere MQ, WebSphere Message Broker or WebSphere Business Integration Event Broker installed. Of course, if you're using another vendor's app server you would need to use WMQ or one of the brokers to bridge the gap.

Mark Phillips' developerworks article does a good job of explaining this:


Hey, that's good to know!   One more way to connect...


Comments (1)

  1. Alex Krapf says:

    For several years now, Codemesh has been offering JMS Courier to help C++ applications connect with JMS infrastructures. We have recently done a lot of work to bundle JMS/.NET connectivity in an easy to use package.

    JMS Courier for .NET ships as a couple of assemblies and assorted examples. It is based on Codemesh’s JuggerNET tool, which generates .NET proxies for Java types.

    Under the hood, the JMS Courier runtime will launch a JVM in the .NET process and handle all interactions transparently to the user. This works with all JMS API-compatible vendor implementations, as long as they can be discovered via JNDI (should be true for all implementations which you normally care about). Performance is absolutely comparable to the performance of a corresponding Java solution.

    All JMS features are accessible easily, including asynchronous callbacks (MessageListeners or ExceptionListeners). Inquiries are welcome, betas are available as of now.

    (nine seven eight 3 6 9 8 5 eight 3)

Skip to main content