Bobby Woolf: WebSphere SOA and JEE in Practice
From archive: June 2006 X
There's a new Insight and outlook column in the developerWorks Architecture Zone: "Defining the most important IT architecture issues."
My answer is, "Aligning IT with business."
For previous columns, see Service Governance.[Read More]
IBM's Billy Newport has posted "WebSphere group membership overview."
I wouldn't have guessed from the title, but the topic of the posting is details about how the High Availability Manager in WAS 6.x works. The HA Manager is a major step forward, and part of the basis for WXD. It works by keeping the cluster members in contact with each other, electing where to run singletons, and holding new elections when outages are detected. Billy explains some of the details about how all this works.
Have you ever wondered, "Why use WAS 6 instead of some other J2EE app server? Aren't they all just J2EE?" One of the main capabilities that separates the J2EE app server men from the boys is clustering and high availability. WAS does this really well; a WAS application sees the results as what we call workload management (WLM), which provides load balancing and failover, which makes apps HA even when individual app servers or host machines are not so HA. It's interesting to read about how it all works.
For more info:
Sun, or at least one developer at Sun, has become a committer to the Eclipse open source project.
It's been announced:
Sun seems to have decided to participate in Eclipse. This is a big deal because historically the two big hold outs on the whole Eclipse phenomenon have been Sun and Microsoft. I still don't see Microsoft deciding to cooperate with a major effort in the Java community, but it's about time Sun finally has. Pretty much everyone else in the Java industry has joined Eclipse, but Sun kept insisting on supporting NetBeans and shunning Eclipse. Hopefully this contribution represents a change in direction.[Read More]