To carry Rogerio's question a little further, how much of this book is focused on specific tooling (such as Websphere) vs general principles which can be used for analysis and design regardless of implementation platform?
The book and the associated tooling are focused on working through Business Modeling, Service Identification and Service Specification - with support for SOA Governance. In these efforts we use a couple of simple Domain Specific Languages (Business Modeling and SoaML, both of which are extensions to UML) to help capture business domain and SOA domain details. The Business Modeling profile is generic to any usage scenario. The SoaML language is from the OMG and not tied to any vendor. The language can be used to describe any SOA solution, that will be deployed to any runtime.
So as far as the book and the related product go, we're not tied to any platform. The concepts and approach we discuss add value to any SOA analysis and design effort, regardless of the target platform.
Our product currently installs into Rational Software Architect for WebSphere (or RSA with the SOA Extension). This product has some features that are applicable to only WebSphere. However, they also support a wide range of application servers (WebLogic, Tomcat, JBoss, Jonas, Glassfish, and a few others).
And as the book is a free download - grab a copy and take a look :-)