Posts Tagged ‘WebSphere’

All aboard the 9.1.x CD train. First stop is IBM MQ V9.1.1.

November 27, 2018


I am sure everyone knows the phrase about buses. If you miss one, don’t worry. There’ll be another one along in a minute. And while it could be said that applies to Continuous Delivery releases, I think it is more like getting on board a train. The destination is the next Long Term Support release, and you think you know what stops will be coming up. But maybe you don’t know exactly what you will find at each destination. You know there will be something new to discover at each stop. You could almost think of the train growing at each stop with the content of each new continuous delivery release, ready to be delivered finally to the Long Term Support destination.


Which brings us to the latest MQ CD release, MQ V9.1.1, announcing today, which is the first CD release in the 9.1.x set of releases. The experience we have of our 9.0.x CD releases is that we have seen a lot of interest from customers. Some have been able to move quickly to take up the CD stream into their environments and run them in production, at least for some of their queue managers. Others have been able to experiment with the new features in their test environments to see whether it is worth their while adopting the content early. And there seems to be a larger set of users who, while they haven’t been adopting the CD content into the production systems, the earlier availability and visibility of the new content has helped them move much more rapidly to adoption and use of the MQ V9.1 LTS release than we might have previously expected. I have personally talked with a lot of existing MQ customers who have either already started using MQ V9.1 LTS or are planning to move to use it very shortly.

Screenshot 2018-11-27 at 08.47.09

The MQ V9.1.1 release isn’t a destination in itself. It is the first part of our continuing journey. The MQ team works to accommodate a mix of strategic development priorities into releases to move the MQ offering forward, as well as other customer driven priorities, and reacting to and supporting other offerings and platforms as they change and adapt. Let’s find out how this mix has shaped the release. As well as suggesting you read the announcement content in the announcement letter, I will call out a few of the interesting new features.


One important new set of capabilities, driven by customer requests, is around the choice and negotiation of the use of TLS ciphers. Security of the MQ environment is hugely important in the current environment and is likely to remain a key area of focus. The importance of security and data protection is one reason customers are moving to MQ Advanced or MQ Appliance as a way to get the end to end encryption in MQ AMS. But this release focusing on enhancement to the security used in the TLS ciphers – used for encryption on the wire, not encryption at rest. As time passes, some ciphers become less secure and customers need to take prompt action in their environments to ensure the ciphers they use are updated to meet their own business requirements as well as the needs of the different systems.

In MQ v9.1.1 the choice of ciphers can be negotiated dynamically from a set or ‘whitelist’ available on each MQ channel. This reduces the potential for downtime and administrative overhead through faster movement to new ciphers when an old cipher is deprecated. Weaker ciphers can be removed from the list of allowable ciphers without needing to wait for a security fix update from IBM.


Another update driven by customer requests is the new support in MQ V9.1.1 for .NET Core for Windows. Customers who choose .NET as a framework for running applications on Windows environments have been looking to move to .NET Core. Following a number of requests, we have now added support for .NET Core for Windows environments to help support those customers.


As we have seen in the 9.0.x CD stream, one of the important set of capabilities that was added was the REST API for Admin for MQ. And at the end of that set of releases we started to look at adding REST API calls for the administration of MQ Managed File Transfer features, available with MQ Advanced and MQ Appliance. Many customers find it value to ingest and move data through MQ, even when the starting point or destination for this data is a file on the file system. To MQ, it is all just data moving in MQ messages. Therefore, from an administration point of view, it is important to offer similar features and controls for managing the movement of this data through MQ as is available for MQ exchanges of application data. In MQ V9.1.1 the MQ MFT feature gains REST API calls to list the resource monitors as an alternative to previous methods.


A further update is to provide support for pausing message delivery to Message Driven Beans running in WebSphere Liberty, in addition to the support previously made available for WebSphere Application Server.


The MQ V9.1.1 release offers a good foundation to start the journey through the various 9.1.x CD releases. There was a mix of updates driven by customer needs, wider platform and offering support as well as some functions to enhance longer term MQ strategic plans. We are now pulling out of this station and heading to the next one. Hitch up the V9.1.1 wagon to your V9.1 MQ train, hop on board and enjoy the ride.



The Paradox of Choice – the best Managed File Transfer solution?

March 18, 2014



We all know the feeling – you are shopping, maybe for some food. You have a vague idea of what you want until you are confronted by reality – dozens or even hundreds of different options. Which is better for you? Which will better meet your needs? It becomes harder to make a choice if there are too many choices. When I am out for dinner at a restaurant I suffer much the same dilemma. I love Cherry Pie for dessert, but what about the refreshing creaminess of Ice Cream? It might seem a simple choice but it would be easier to make a decision if the menu was more restricted.  


This was explored in a very interesting book by Barry Schwartz called ‘The Paradox of Choice – why more is less’. I highly recommend a read of it.

This applies quite widely in other areas. Take for example how you want to deal with files in your business. Let’s face it; you have files, filled with business critical data, on every system in your enterprise. And you need to move the files, or at least the data inside them, across your enterprise to consume the data elsewhere. So you plan to move them, only this creates your first dilemma – should you use simple FTP even though you know it can be unreliable and insecure, and you never really know what happens to your files. Or should you use a managed file transfer solution?

Well hopefully, your business cares about the files and the data enough to look at a managed file transfer solution. After all you don’t want to create a management and security headache when trying to move the files, and you certainly don’t want to troubleshoot what has gone wrong every day, and maintain hundreds of FTP scripts.

So you want a managed file transfer solution – but which one? This opens up a whole different solution set. Do you want a bespoke solution, dedicated to file transfers, or one that is maybe multi-tasking – perhaps a function built out from another piece of infrastructure that might be more adaptable for some of your use cases, even though the dedicated solution looks good for other use cases?

Many customers today might look at their existing solution providers such as IBM who has been providing middleware for this type of solution for many years. And here there has been a choice to be made:

IBM Sterling Connect:Direct, a market leading managed file transfer solution with years of expertise as a dedicated offering in this space, with a secure protocol and purpose built tooling to provide all a business needs when moving files, extended with IBM Sterling Control Center for event based monitoring of file transfers. Looks good for a dedicated solution.

IBM MQ Managed File Transfer, an extension to the widely used IBM MQ messaging middleware offering. This also provides file transfer, moving the files as messages over MQ, but also allows not just file to file transfer but also file-to-message and message-to-file transfers which can help the business make faster use of the data being moved. A highly adaptable solution, but also supported by IBM Sterling Control Center as a management and monitoring dashboard.

So even from IBM you would need to make a choice, even though you could probably adapt both offerings to meet your needs. But it would be nice to not have to choose, but to use whichever offering was best for any particular use case.

On March 11th 2014, IBM announced that it was solving this dilemma of too much choice by combining the two offerings of IBM Sterling Connect:Direct and IBM MQ MFT, and also including IBM Sterling Control Center. Now there is just one solution to buy for Managed File Transfer. And when you buy it you don’t have to choose which to use, as you get entitlement to both offerings included, as well as Control Center. No more choosing between Cherry Pie or Ice Cream, as you can have both.


A smaller number of choices in this case is definitely better. You can read more about this offering in the announcement letter here. Dig in.

WebSphere MQ Advanced for Developers – another exciting step forward

March 19, 2013

Yes. It’s that time again. Another blog entry, so we must have something new to say about WebSphere MQ. And yes we do.

I’m very pleased that we have another announcement to make today. WebSphere MQ Advanced for Developers. You can read the announcement letter itself here. But in the meantime what are the key points you really ought to know?

1)     This is an exciting new development in that we have added a new way to buy licenses of WebSphere MQ, and indeed the entire WebSphere MQ Advanced stack, but priced for individual developer deployment and use. We continue to have both the separate WebSphere MQ licenses and WebSphere MQ Advanced licenses, which are both priced by PVU, and suitable for production and testing. But this new licensing option is priced per ‘Authorised User Single Install’ which effectively means a fixed price per developer that wants to use it for their development use. We believe that by making the WebSphere MQ portfolio more available for developers, giving them individual access we will increase their skills, improve their ability to use WebSphere MQ in innovative ways, and also speed the time to develop more productive applications. Read the announcement letter and get the new part from Friday 22nd March.

2)     As part of this announcement we are also taking advantage of the opportunity to bring everyone up to date on the enhancements we have been making to the support for connecting to M2M devices and mobiles. Over the last couple of months IBM has been publishing new Messaging Clients to support Android and iOS mobile devices. These have been published on our new Messaging Community on developerWorks. This announcement has been timed to coincide with the first fixpack for WebSphere MQ V7.5 which adds in additional function that also allows connectivity from MQTT clients over WebSockets. This creates new opportunities for building new types of applications that can connect to the enterprise over WebSockets, which we expect to be very popular, especially when combined with the new Javascript API which supports both this style of connection as well as supporting the clients on Android or iOS devices. These clients support our Worklight offering, and with IBM MobileFirst this is a very exciting time to be adding this type of support.

3)     Finally as part of this update IBM has also made some changes to the licensing to support High Availability with WebSphere MQ. In recent years WebSphere MQ added its own approach for High Availability – called Multi-Instance Queue Managers, which allowed WebSphere MQ to automatically watch itself and failover if required. An additional ‘Idle Standby’ license was required for the failover system, which was substantially cheaper than a full license. In this update we have extended these Idle Standby licenses to also apply to other configurations that provide automatic failover – such as PowerHA, or 3rd party configurations like Veritas. Now the failover systems in these environments can also be licensed with the Idle Standby parts.

Hopefully these look like a good set of updates – and they have kept us busy working towards them. Don’t forget you can download the free trial for WebSphere MQ here. And visit the Messaging Community to find more stuff, including the Messaging Clients for M2M and Mobile. And look for a webcast from me on the Global WebSphere Community on April 11th.

New post, new job role, long time passed

August 20, 2010

So just a quick note here. I changed roles earlier this year to move back into Product Management for WebSphere Message Broker after a number of years in Marketing. It is funny how both roles have similarities but also substantial differences. I am getting a lot more visibility to customers and sales reps in the new role which is really good, but am continuing to work closely with marketing to make sure we get the right material produced. Keeps me busy – and apologies to those who I respond to later than I should.

Was good talking a bit with Gartner earlier in the year on a couple of occasions – and hearing all the customer interest in cloud – not an area that will be going away in a hurry I think.

It has been very stimulating to work on strategy for both extending current offerings and looking at the opportunity in new segments. Lots I could say here but clearly not going to in public!

I plan to talk to some customers in Istanbul next month as part of a Hursley Comes to you event and there will also be more customer interactions in 4Q which i am looking forward to. All this while trying to get through all the Product Management day to day pieces of work – which I had better get back to.

Focus and prioritization are becoming the watchword….will try to write something more soon

More on Tough Questions from ESBCON8

August 28, 2009

So following up on yesterday’s first Tough Question from ESBCON8, lets move to the 2nd question

Question 2:Today’s ESBs are more business-aware, supporting critical events  (with EDA, CEP, even BPM).   How are your customers using these benefits?

First off, do I agree with the statement, aligning ESBs with Events? I would have to say yes – we have seen our customers use WebSphere Message Broker for many years as a mechanism to detect and respond to Events passing through it, making use of the processing and aggregation capabilities it provides. Although this was very powerful and a great advance to increase visibility and agility, its use tended to be restricted to more technical events. The addition to the product line of WebSphere Business Events enabled business users to determine the critical events they were interested in, greatly extending the usability of Business Event Processing. This move to an event driven architecture very much builds on the existence of an ESB, across which all data flows. This assumption of the presence of an ESB is what we discussed yesterday in the first Tough Question.

So on the basis that an ESB exists, and business is now able to see and respond to events as they take place in real-time, how are customers using these? The event processing delivered by WebSphere Business Events allows businesses in many cases to take the step step towards BPM, allowing their businesses to leverage their existing IT infrastructure to rapidly deploy business changes, streamlining processing, increasing automation and reducing bottlenecks, all while gaining better insight to what is actually happening in their business to help drive further improvements. Some customers already see this success.

As Event Processing builds on the Connectivity of an ESB they are likely to already have, they are able to quickly see benefits and then use further tools such as ILOG for Business Rules to adapt and respond to changing needs.

Tough Questions on ESBs from ESBCON8

August 27, 2009

So it has been a week since ESBCON8 went out. You can still register and listen to it here – I think you will find it worth the time. All three CTOs had a lot of interesting points to make – Although clearly the solo presentations are a core part of ESBCON, the section I enjoyed listening to the most is the “5 Tough Questions”. This head-to-head section covers a lot of different points and you get to hear a more impromptu set of answers. Lets review the first of the 5 Tough Questions from the event this time:

Question 1:Gartner recently released a study that says 70% of all enterprise SOA starts with ESBs. What do your customers find are the most popular reasons for using ESBs as a foundation technology?

Perhaps the most fundamental question for an audience interested in ESBs…The discussion today of SOA seems to be in a state of transition. Is SOA dead? Absolutely not. If anything the discussion has moved on from SOA, in the same way it moved on from the frenzy of discussion around ESBs in the last couple of years because there is no point to a discussion over whether SOA is useful or important. The answer is obvious and everywhere. SOA is now assumed – the question is what’s next?

IBM is already telling this story of what’s next – with Smarter Planet and Smart Work, all building on the solid foundation of robust reliable and agile business and IT alignment provided by SOA, with an ESB at the heart of the infrastructure. This is the reasons so many projects have an ESB as their starting point, is that an ESB is a fundamental, essential component for the infrastructure to whatever project you are looking to implement, so starting with this is a given, especially as so many parts of the business can make use of it, thus increasing time-to-value.

If projects don’t start with an ESB, they are likely to start with a Registry/Repository, trying to put SOA Governance in place before too many services escape into the wild. SOA does offer business the ability to see and respond better to events, but also provides the capability for just as much chaos as exists in architectures already.

So – SOA isn’t dead, and an ESB is fairly clearly an obvious place to start in enhancing your business infrastructure – putting in place the ability for you to Work Smart for a Smarter Planet.

I will take a look at the other Tough Questions shortly. And I am sure I will come back to Smarter Planet and Smart Work

ESBCON 8 – Looking ahead to a great event

August 20, 2009

Later today the most recent ESBCON event will go live. This long running multi-vendor virtual conference takes some leaders from the major ESB vendors and has them give brief solo presentations, as well as putting them on the spot asking them 5 tough questions.

For IBM we have Jerry Cuomo, WebSphere CTO, presenting. Other vendors Sun Microsystems and Progress Software also have their CTOs presenting at the event.

After the event I will look to give my own thoughts on the 5 Tough Questions. However as a lead in lets look at some of the Tough Questions that could have been asked but didn’t make the cut to the Final Five.

Some of the initial thinking could have included questions such as:

  • What benefits do ESBs with SCA (Service Component Architecture) offer users? What skills does IT need to tap into SCA benefits?
  • How large can I scale an integration/SOA project with a single ESB?
  • Discuss technologies and patterns for scaling ESBs, in terms of traffic load, number of nodes or even multi-site integration?
  • Discuss trends in real-time visibility and management for IT and business users?
  • How does your ESB manage integrations end-to-end (include support for Remote Integration, High-Availability, Governance, Auditing or Identity Management)

Now some of these questions got adapted to end up contributing to the actual questions asked, but they do reflect important points, even with duplication and the different technical levels being probed. The questions on scaling are clearly important – after all who wants to deploy an ESB which if successful will undoubtedly require the ESB to handle increasing traffic loads and be physically and logically deployed and managed more widely across the enterprise.

Also important is the aspect of real-time visibility for both IT and business users. This is growing in importance, with all traffic moving through the ESB it becomes easier to understand how and where to track business data as business events take place, and also for the IT side of the business to track and control the use and performance of systems. This visibility aspect is one of the key unsung benefits that can be seen from a successful ESB deployment. I will make a point of saying ‘successful’ there as it is easy to think of an ESB deployment to meet a singular need that is then not used further to extract that data that can so enrich a business.

It will be interesting to see how the CTOs fare on the real questions, and I will look forward to reviewing that after the event

Sensors, events, automation and what-not

July 21, 2009

Just time for a quick update before my next phone-call. I have been working a lot on various decks looking at industry solutions that use or leverage WebSphere MQ and ESB solutions from IBM. A number of them, certainly in engineering industries such as Chemical and Petroleum, or Energy and Utilities, already use solutions like WebSphere Sensor Events or have the potential to use them in the future. And there are also clear benefits to other industries like Retail or distribution. All sorts really – at Impact I sat in a very good session talking about how Airbus uses RFID sensors to keep track of the parts of planes they are building. After all it is so easy to lose an Airbus A380…

We have referred to this as the Internet of Things. There is a great example of this from Andy Stanford-Clark and his house that Tweets. But the more I read about this, the more interesting I can see this getting. Clearly this requires some level of investment from businesses to leverage, but the greater the connectivity throughout their infrastructure, the more opportunities will arise. The economy today drives businesses to look to cut costs and drive growth. Extending connectivity through these devices and increasing business awareness truly looks to be transformative. I will look to give more examples and cover this more going forward

Reuse, cross charging and the Cloud

July 1, 2009

One of the big topics of discussion at the Gartner SOA event in London last week was, unsurprisingly, Cloud Computing – it is everyone’s favourite hot topic this year. One session by Yefim Natis really focused on some of the implications of this – and before he started I made a couple of notes to myself to test as to whether he would answer them.

The first was whether Cloud could solve the cross-charging issue (I will explain this in a moment) and the second was whether Cloud would present a good opportunity for WebSphere Service Registry and Repository. Both of these issues were items that were nagging at me from listening both to clients in the Vendor showcase and also to other Gartner analysts.

The big one was cross-charging – Massimo Pezzini had addressed this as a critical issue to the future of SOA. There was a conflict of interest for those parts of the business who provided services. For the good of the business they were encouraged to make the business services they provided as reusable and shareable as possible. However then as their reuse grew as the uptake of SOA spread in an organization, who then was responsible for the costs associated with not just the initial work to create a reusable service but also then the increase in traffic as it became a fundamental part of multiple composite applications. The service providing department would become a cost center, faced with ever increasing costs and demands for improved SLAs. This could drive future work to be made highly specialized to avoid this issue, impacting the ability of SOA to really be successful.

Now in IBM we have always been keenly aware of the cross-charging issue, as this has always been important to our mainframe/System z customers. Our products such as WebSphere Message Broker, which functions as a highly capable ESB,  have therefore included capabilities to identify and charge users for their use of the environment. But of course in a Cloud – an elastic shared use environment – it is explicitly designed for resource allocation and tracking the user and use. Yefim in his session then proposed that deploying these shareable services in the Cloud, with its ability to track and charge for use could lead to these service providers being seen as profit centers instead of cost centers. Now being a profit center when providing internal services is one thing – moving money from one pot to another within a business does not a profit make. But combine shareable services in the cloud with a move to more dynamic multi-enterprise B2B, sharing the costs with partners, and some of the investment decisions can make sense, as well as streamlining your business connections and processes. A good thought for the future.

The other question I had was around WebSphere Service Registry and Repository (WSRR). I had talked to quite a number of clients at the show who were deploying, or starting to deploy assets connected to one or other of our ESBs – and they were trying to figure out whether this truly made them more dynamic. Of course it does simplify your connectivity to use an ESB but then are you just swapping one change regimen for another? I got a good response talking to them about using WSRR to hold each service step, and to search for the service location through WSRR rather than defining its location in the ESB flow – this allows for very simple updates and changes to services without any disruption to the running processes and ESB flow.

Now of course when the services are defined as ‘in the cloud’ this is the ultimate requirement for flexibility – they will never have a fixed location or definition  anywhere other than the cloud so use of a registry to store and locate these will be essential, as well as the other facets it provdes such as identifying rogue services and enforcing business policies. This says to me that when we are talking to our clients about using the cloud, we need to be sure to discuss the use of ESBs and also WSRR.

Lots to do. Should be interesting!

Attending the Gartner SOA/ADI event in London

June 29, 2009

It was nice to get out of the office/home office routine last week to visit the Gartner SOA/ADI conference – this was the second year I have been to this show and it is always worthwhile. The event seemed to be very busy with the keynote sessions pretty full and some very interested customers from all over Europe and beyond attending to listen to the sessions and also talk to the vendors attending – of whom IBM was one – as a premier sponsor. At pretty much the start of the event there was a vendor panel from the premier sponsors who participated in a quickfire session to review their thoughts regarding a number of Gartner predictions for the future – there was broad agreement with many of the thoughts, although there was a level of scepticism regarding whether the scale of uptake for some of the technologies would be as high as was contended. The state of the economy was judged to be a likely factor in IT change decisions – which is of course to be expected.

The other Gartner sessions I attended were certainly very interesting. A theme which seemed to run through the 2 days was the coming growth in multi-enterprise B2B driven by the need for e-invoicing. And the complexity and business risk associated with this will also drive the need for strong SOA Governance. SOA Governance was one of the key starting points for companies starting SOA implementations, but by far the most common starting point was an ESB – which of course makes a lot of sense as an ESB is a great boon to business whether it is part of a larger SOA deployment or simply looking to improve connectivity.

We had a great stream of different businesses coming to the IBM stand in the Vendor showcase. Due to the focus of the show, all were highly knowledgable about middleware and many were already WebSphere customers, involved in projects, either at early stages or deploying. I had a number of discussions with almost everyone about whether they use FTP as a part of their existing infrastructure, and whether the new WMQ File Transfer Edition product could be of benefit to them – we got some encouraging interest.

Also a popular discussion topic was our WebSphere DataPower appliances – they of course have many uses throughout the enterprise and I had involved discussions about what benefits they provided depending on the type of deployment and where they were being used. And finally an interesting topic for discussion was the brand new WebSphere Cloudburst appliance – there is huge interest in Cloud and this seems a very timely and innovative solution for customers. Hopefully next time we will have a box on display!