IBM Impact 2009 was around the corner and the buzz, interest and on the ground implementation discussions of SOA continues.
My current involvement and hence the topic of interest to me was the federated governance within the enterprise. When we think about it, it is indeed a bit more complex than what it may seem like, initially.
There are different types of work products generated across BUSINESS, SOA GOVERNANCE (OR COE), DEVELOPMENT and OPERATIONS. This is further is complicated by different types of tools and domain specific practices. This distributed environment is successful and most efficient when there is a structured and consistent way to handle micro and macro level lifecycle of resources involved.
As far as "Services" are concerned, there are primarily three major categories that participate in the overall organizational governnace.
"Runtime" environment for services, thatis focused on services, mediations, policies and meta-data (likeversions, endpoints, relationships etc). "Development"environment of services has a specific perspective, which is more aboutimplementation, API, release cycles, technology decisions etc. Lastly,the "Operations" that deploys and maintains theservice and needs to deal with endpoints, mediations, security,maintenance, availability, provisioning, interfaces, configuration etc.The above governance "concerns" should also map to the overallSOA lifecycle that enterprises adapt.
Customers who are using some of IBM's products like RationalAsset Manager (Development), WebSphereServices Registry and Repository (Runtime) and Tivoli CCMDB (Operations) can begin to realize the benefits of federated governance early on.