As with so much of the landscape of service-oriented architecture, large vendors with extensive marketing departments have tried to prescribe how their software should be used to solve specific problems instead of investing in the bigger SOA picture.

Software is the enabler for the broader SOA project, but you need to have a baseline understanding in place before software becomes practical. At a minimum you need to know the problem you are solving before you choose software packages.

Dave Linthicum blogged about this subject this morning:

The fact of the matter is that SOA governance, and governance in general, is really a people and process thing, with technology only coming into play to automate the processes and support the people. If you don't establish that, you're going to fail at SOA governance and thus fail at SOA, no matter how much technology you invest in.