As Bill has already noted, many (all?) of the developerWorks blogs are now on Roller.
So the blog looks and works the same, but with a few differences. All the old URLs still work, but now map to new, simpler, better URLs. This blog's URL is now http://www.ibm.com/developerworks/blogs/page/woolf. Each posting's URL now has the posting's title in it, instead of a database UID, such as http://www.ibm.com/developerworks/blogs/page/woolf?entry=we_re_now_on_roller. (I'll have to try naming two postings the same to see what happens. What if you rename a posting?) In the column on the right is a new section, Recent Entries, which gives a nice compact list of my latest postings; less scrolling to look them over. There's also a new search box at the top of the blog page, just below my bio, which does a nice job of finding postings just on my blog. (Will I no longer need to Google ""something interesting" woolf site:ibm.com"?!)
So, bare with us as we learn to blog all over again. In many ways, Roller is better, offers us more editing features that you'll never see but we'll appreciate, and is certainly much more standard than what dW was using before. But like all things worth knowing, there is a learning curve. Should be interesting.
Bobby Woolf: WebSphere SOA and JEE in Practice
From archive: March 2006 X
A phrase IBM is throwing around a fair bit is "information as a service." What does that mean?
Information as a service (IaaS?) is part of our service-oriented architecture (SOA) approach. In our SOA Reference Architecture diagram, this is the Information Services block.
The idea is that in an SOA,
A good example is the way many companies store the info for a single customer in several different databases, because different apps want their own customer attributes and because they all want local access to the customer from the local database they manage. Such spread out, duplicated data makes it a real challenge to create, delete, or update a customer. So one approach is to define a customer management service, with operations like create, delete, and update. Expose that service on an ESB, and you can invoke it from anywhere, it'll run anywhere it's hosted, and it'll do whatever steps are necessary (whether that's two steps or 200) to update the databases. If tomorrow you add another database, modify the service to update that database as well and the service consumers never need to know the difference.
Some sources for more info:
A reader pointed me to his blog, which has a really interesting premise.
The blog is Leadership by Numbers, authored by Jack Dausman. Thanks to Jack for pointing me/us all to it in his comment on Social Network Analysis. I don't know Jack and have only looked at his blog a little bit, but I love the premise:
As kids, we made art with paint-by-number kits. Simply matching the outline numbers with an oil paint gave us the illusion of mastery. Today, I'm in IT management in Washington, DC: consulting, systems administration, development & training. And, I still see a lot of paint-by-number projects which try to be the real thing. IT leadership is about reading the numbers, then going outside the lines and taking risks.
Now that is an excellent analogy for how I feel about heavyweight software methodologies! All too often, people are following all the steps but totally missing the point of producing good software. One colleague recently told me, "Sub-average programmers aren't successful with agile methodologies." I responded, "As compared to what? Sub-average programmers certainly aren't successful with heavyweight methodologies! They're not successful with anything; that's what makes them sub-average." Paint-by-numbers doesn't make you an artist, and methodologies by themselves don't make you good at developing software.
For more thoughts along these lines, check out how complicated use cases have gotten.
WebSphere Application Server Support has issued a security flash: Security: Possible security exposure with JSP source code on IBM WebSphere Application Server Version 5 (PK13792 and PK20181) (Reference #1231377)
I don't know any more about this problem than what the flash says, but to summarize:
To get notified of announcements like this in the future, subscribe to IBM's RSS feed for WAS.
To learn more about WAS support, see Keeping WAS Up-To-Date and Working with IBM Support.