We don't go around evangelising a rip-and-replace strategy.
If necessary they can be combined into a single workbench. 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.
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. Sure, we have a number of products which fit in across the whole swathe of an SOA.I heard this same statement from a customer earlier this week. The final entry in the series suggests that IBM has a problem with the SOA message – we just have too many products. So instead I want to talk about the series of articles on The Register by Phil Howard of Bloor Research. 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.
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.