… and being the techie that I am, decided to have a play with WebSphere Application Server Community Edition. I uninstalled the pre-release software I'd looked at previously, and followed a nice tutorial from the WebSphere Developer Technical Journal to get the Daytrader sample deployed and running.
All works well. The only thing I'm struggling with is that the process of installing the sample "magically" created some JMS destinations… but trying to configure them manually via the admin console causes stack traces in the log and no destinations get created. Probably just my install.
A few weeks ago I learned that Fedora Core 5 is slated to include an Open Source app server called JOnAS. Yesterday the Geronimo blog mentioned that RedHat and Novell are planning to ship Apache Geronimo and Apache Derby (nee IBM Cloudscape) in their Linux distributions. WAS CE is of course based on Geronimo, so this is great news.
Oh, and Sun are planning to ship Derby, too. Naturally it is their own implementation, dubbed "Java DB".
The software scene gets more and more interesting.
Technorati tags: Apache IBM Geronimo Linux Java
Tempted though I am to weigh in on the recent post by Rich Turner of Microsoft UK on the perceived differences in style between IBM and Microsoft, particularly in the consulting arena, Richard Brown seems to have it covered with his usual mix of good humour and sharp perception. Suffice to say that I believe Richard is absolutely right in saying that we don't all work for Global Services, and that MCS and IBM Software Services have very similar missions. I'll come back to this point later.
So instead I want to talk about the series of articles on The Register by Phil Howard of Bloor Research. The final entry in the series suggests that IBM has a problem with the SOA message – we just have too many products.
I heard this same statement from a customer earlier this week. Here are my thoughts on the matter:
- Sure, we have a number of products which fit in across the whole swathe of an SOA. Let's talk about at a few of the development tools, for example: Rational Software Architect, Rational Application Developer, WebSphere Integration Developer, WebSphere Business Modeler. These are all based on the Eclipse platform (as are all of our tools), and provide functionality appropriate to their target audience: architect, J2EE developer, ESB integration developer, business analyst. The look-and-feel is consistent. If necessary they can be combined into a single workbench. What's so scary about that? You can choose the products you want, and combine them as you wish.
- IBM is strongly behind open standards, and we go out of our way to ensure that our products conform to agreed open standards wherever possible. We don't go around evangelising a rip-and-replace strategy. We know that many customers have a technology soup already, and there are heritage applications and platforms that aren't going to be going away any time soon. I've been with IBM for 4 years, working with our WebSphere integration products, and literally every day of my time with the company to date has been about applying our technology to integration problems that customers face. By following a strategy based on open standards, the ability of our products to interoperate with those from other vendors is greatly increased. Again, you can pick and choose what you need from our portfolio to fit in with the needs of your business.
- What if we just had a single, "uber-product" for SOA? How much sense would that make? It just isn't reasonable, surely? And just how "simple" would such a product be? What we have is a set of software products which cover the challenges which customers are likely to face as they set about building an SOA. I also believe that we have a consistent message and that each of our software brands makes its own strong contribution as part of the SOA strategy. You need a development tool? Look at the Rational brand. You want to look at collaboration? That's Lotus. Monitoring, security, systems management? Tivoli products. We have excellent coverage; it doesn't matter which point you want to start from, we can help you to deliver an SOA.
The final point raised by the piece is that one of the really key aspects of implementing an SOA is that of the cultural impact, which I think we can talk about in terms of governance. Phil Howard argues that since this is more a business issue than an IT issue, it is outside the domain of IBM Software Group. I agree with him up to a point; but this is where we dovetail neatly (I hope!) back into the point about IBM Software Services and IBM Global Services. IBM Software Group may not be able to cause a cultural change simply through the software that we release*, but as a Software Services consultant I certainly go out of my way to talk about the business impact of SOA. It simply isn't going to work if the business decides to build an ESB and then the IT development groups fail to use it – you miss out on the benefits. Strong leadership and governance is critical. As a consultant part of my role is to not only transfer technical skills to our customers, but also some of our experience and understanding of the cultural impact of SOA on both business and IT people.
* unless… we came up with some kind of mind-control software… interesting… I'll have to talk to the guys in the labs… 🙂
Technorati tags: SOA ESB websphere IBM rational tivoli lotus Eclipse