Posts Tagged ‘Publish Subscribe’

IBM announces IBM MQ V8

April 22, 2014

Image

There are some things that come around every day. Good things, like new business and new customers. Other daily occurrences are not so good, like hardware failures, network problems, or security fixes to apply. Then there are some things that come around much less frequently, but they are worth waiting for. Good days like when a new version of IBM MQ is announced. Days like today.

That’s right. At IBM we are happy to announce IBM MQ V8. You can read the announcement letters here: Click here for the announcement letter for IBM MQ V8 on distributed platforms. Click here for the announcement letter for IBM MQ for z/OS V8. And click here for the announcement letter for the various IBM MQ V8 offerings on z/OS with a One Time Charge pricing metric.

There are a lot of new capabilities, and plenty of enhancements and improvements included in the announcements. At this point I will just call out a few of the high level items, and leave myself plenty of opportunity to come back on subsequent blogs and dive a little deeper into some of the new and improved areas.

Let’s start with one of the changes that maybe either big or small depending on your perspective. We are starting, with this version, to call this product IBM MQ, as opposed to WebSphere MQ, mirroring a change you may have seen in some other products in recent years. After all MQ connects your entire infrastructure, so referring to it as IBM MQ rather than WebSphere MQ is perhaps more indicative of that breadth of coverage. It does of course continue to work with all the previous releases of WebSphere MQ, and in fact when you order it and install it, you will still see it as WebSphere MQ, but over time, expect changes in the product to reflect the new branding, while continuing to deliver the same robust messaging infrastructure.

So what else is new? Plenty of course has changed for the better, and many of the changes can be grouped as enhancements to boost both security and scalability, improving support for standards, and also doing more to exploit the hardware being used. This changes should reflect an overall improvement in the ease of use of IBM MQ in this release, simplifying configuration and reducing operational tasks.

From a security point of view, some of the key changes include the authentication of userids defined in the operating system, or in LDAP for distributed platforms. More changes include support for multiple certificate authorities in a single queue manager, and the use of DNS Hostnames in Channel Authentication Records.

From a scalability point of view MQ is now better at scaling to the limits of a SMP machine. And there are various other enhancements, especially for publish-subscribe, including a change in the way clustering works for pub-sub. These changes in scalability are particularly designed to improve real-world scalability, rather than being tuned to demonstrate performance in confected examples.

Notable in new standards is support for JMS 2.0 with new messaging features and updates to the API. Also there are enhancements in Microsoft .NET support as well as WCF extensions. And for improved connectivity options, the function that was previously a part of MQ Telemetry Advanced is now a part of MQ Telemetry, giving customers more for less.

For our customers using MQ on z/OS there are some particularly notable enhancements that offer new capabilities and exploit some of hardware updates likely to be available. There is support for 64 bit buffer pools, and a wider log Relative Byte Address as well as support for the zEDC compression and Coupling Facility Flash. Likely to be of real interest is the announcement that we have removed the Client Attachment Feature, meaning that there will no longer be a charge to connect MQ Clients on other platforms to MQ on z/OS. This applies from today, not just on MQ V8 but on WMQ V7.0.1 and V7.1 as well.

As I said, there is quite a lot of new information to share here. I didn’t even get a chance to mention that the MQ AMS code is now integrated into the base on all platforms, and available on IBM i for the first time. Lots more detail to come so please come back for more, and hopefully I will see you at IBM Impact next week in fabulous Las Vegas.

Image

Life’s too short to drink bad coffee?

February 4, 2014

Image

It has been a lot longer than I wanted since I last wrote an entry on this blog. I guess I have been searching for inspiration. The problem of course being that I work on a lot of things that I can’t talk about until they are ready to announce. So what can I say about what we already have in the market?

I was struck last week with some inspiration. I don’t recommend getting your inspiration the same way, as I was off sick for a couple of days with a temperature of 104F, but it did give me a couple of days thinking time, on a restricted diet. One of the things I was missing was my espresso and cappuccino. I have, for reasons that don’t matter here, two separate espresso machines. A manual La Pavoni and a Gaggia Classic. For either to make decent espresso you need freshly ground coffee, ideally from freshly roasted beans.

Image

I buy my beans from a small UK roaster called hasbean, and have been for a number of years. But here’s the thing. Until a few months ago, I had just bought the same ‘espresso blend’ of beans from them. I went to their website, clicked on their ‘blends’ page, selected the espresso blend I chose, and bought it. Again and again. I was perfectly happy with my choice. The beans were roasted that day and posted out. I would drink my coffee and be happy. Except (and you knew that was coming) I gradually thought there might be something more. Maybe my coffee could be better. I knew it was already way better than the coffee providers on the high street. In fact it was rare I would drink a coffee outside the house that I liked as much as mine. But my feeling persisted. And maybe what I might have done would have been to find another roaster. But all of a sudden, when I was on the hasbean website about to buy some more coffee, I looked a little closer at the website – and clicked on one of the tabs for a specific coffee region…in this case I clicked on America. And there a whole world opened up. Yes there was Brazil, which I knew provided many of the beans in my chosen blend. But there were options for Bolivia, Guatemala, Colombia, El Salvador. The list went on. And click a country, and there was even more choice. Individual producers. Detailed notes of the crop, the harvest conditions, the processing method, and tasting notes. A whole world of choice ready to be roasted and posted.

This was what I had been missing, and it was there for me all along, right in front of my face. Now I am selecting a range of individual beans, drinking different, better coffee, but from the same roaster, and mostly at the same price I was paying. There was even an option to pay a little more for some exceptional beans. Truly a win-win.

So is this relevant for WebSphere MQ users? Well I did visit a long standing customer last month who admitted that they didn’t use any publish-subscribe. Now IBM has been suggesting trying out publish-subscribe for years. It is there in the product. There is no additional cost to use it. And for many uses, you get far more flexible deployments.

Then there is security. Changes made in the V7.1 release back in 2011 gave the product far more usable security, but still customers continue to use exits which now ought to be redundant thanks to the same or better function in the product. Then there are transactional clients, improvements in clustering, API options, etc. etc. And that’s before I even start mentioning Telemetry support, Managed File Transfer and Advanced Message Security options.

Now I understand that WebSphere MQ isn’t a cup of coffee, even if an espresso machine can be complex to use well. Applications connected with WebSphere MQ are systems that run for years, or even decades. And it can take quite a bit of work to consider changing them. But with features like multi-version install, and even the new ability to download the entire WebSphere MQ Advanced stack at no cost for development use, we have been working to make it easier to try new ways of using WebSphere MQ. So at no additional cost, you could be making your applications more flexible, more robust or more secure. You could be simplifying your administration tasks, and reducing the overhead of recurring operational activities. And for a little more you could be encrypting messages end to end without changing your applications, or using your MQ network to move your file data, and to make better use of it. I am pretty sure that with MQTT you could even hook up your coffee machine to your smartphone. 

Now that I have been trying the new coffees I won’t be going back to less variety. Why shouldn’t you be trying some of the good stuff too? Tomorrow morning I’ll be drinking for the first time some Colombian El Meridiano Rioblanco Washed. What are you going to be trying tomorrow?