webMethods has put out an updated intro document to 6.5 components located here - http://advantagebv.webmethods.com/bookshelf/_webMethods_Fabric/Fabric_6_5/Introduction_to_webMethods_Fabric_6.5_and_6.5.1.pdf
One interesting section of this document on Reliability is a bit of a pet peeve for me -
Anyone who has worked with the product knows it doesn’t work this way out of the box. It takes a serious amount of architecting at the IS and broker level to achieve this. It also takes architecting at the flow level to achieve this as well (think handling runtime failures with database connections, or ftp or http etc).
The other issue is the comment about distributed architecture. webMethods components tend to be pretty heavy for distributed architecture. And with the introduction of the my webMethods Server it is getting a bit worse(Eventually all administration of webMethods components will be done through the MwS which requires a one to one relationship with an IS Server). Yes you can distribute the individual components but again it takes a fair amount of architecting to achieve the right balance.
In the end, it can be done of course. My main issue is the tone of the document makes it sound a lot easier than it actually is.