Weblogic JMS with .NET

This came out last month, I just learned about it from an email from Jesus today. WebLogic Server 10gR3 now has an officially-supported .NET client for its JMS provider.   Very cool.  Some of you might be wondering, just what does that mean?  It means there is a queue mechanism in the WebLogic Server, for a long time…

3

PowerShell CMDLets for WebSphere MQ – administer queues on Windows or Linux

Last year, I wrote about the idea of PowerShell CmdLets for WebSphere MQ.  PowerShell is a beautiful scripting environment, you see, and it allows you to load any managed class library and then call into it.  This is what allows me to, for example, create zip files within Powershell.  But there are of course a zillion…

1

JMS Adapters for .NET & BizTalk

Love it!  I previously posted about a beta of the JNBridge JMS Adapters.  I just got a form email from the company that they’ve publicly released their adapters.  There’s a version of the adpater for .NET apps – this allows any .NET app to connect to any JMS resource.  Think about that.  It’s really useful.  If…

2

The SOAP-over-JMS spec and interop

In a previous post, I wrote about a WCF Channel for MQ that IBM is building.  Some customers had asked about this project and its implementation, specifically around the interop implications if other JMS providers, other than MQ that is, were used in an environment. To be clear the WCF Channel for MQ is ……

6

Custom WCF Channel for IBM MQ

IBM have shipped an early version of a Custom WCF Channel for MQ.  The dev team in Hursley contacted me to solicit feedback. It’s apparently pretty simple now, supporting only SOAP one-way messaging, but they say if there is sufficient interest and feedback, they will consider developing it further and perhaps adding it to the…

10

IBM’s new MQ Blog includes some good .NET stuff

The MQ Engineers at IBM’s Hursley Lab (near Winchester, England) now have a blog.  (By the way, the Hursley campus is just gorgeous.) The blog is pretty new, started only last month, as far as I can tell, but it is already chock-full of interesting, high-content posts.   I learned about it when Saket Rungta of IBM…

2

.NET Logic triggered by IBM MQ Messages

I did not know about this. With WebSphere MQ v6, IBM introduced something called the “.NET Monitor” feature.  The .NET Monitor, in MQ, is similar to a WebSphere MQ “trigger monitor.” The doc says, developers can create .NET components and register them with the .NET Monitor.  When a message is received on a monitored queue,…

0

.NET integration with WebSphere Queues – Another Update

The IBM Message Service Client for .NET has been UpdatedPart of an ongoing series on JMS and .NET interop Another update on IBM SupportPac IA9H, the IBM Message Service Client for .NET, aka “XMS .NET”. First, it’s supported! Woohoo! IA9H has graduated into a “category 3” SupportPac, which means if you use it with a…

2

IBM Message Service Client for .NET

IBM Message Service Client for .NET Part of an ongoing series of posts on JMS-to-.NET interop Philip Willoughby of IBM’s Hursley Lab writes that IBM have released IBM Message Service Client for .NET (also known as XMS for .NET) as a category 2 SupportPac – IA9H is the moniker for the SupportPac tifosi out there….

0

.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…

1