Managing artifacts of a service oriented solution is one of the most important features expected from any SOA middleware platform. In a typical service oriented project, SOA artifacts are subjected to move through multiple phases. Usually, separate environments are maintained for the activities associated with those phases.

Read the full story in Charitha's blog.

Governance is central to an effective enterprise SOA. It enables the transformation of business policies into metadata-based rules, and it assists in automating the validation and enforcement of policy compliance in both design-time and runtime environments. Today, complex IT scenarios with interactions spanning heterogeneous systems are placing greater demands than ever on SOA governance, since the constant changes to these systems open a deployment to greater uncertainty and risk. Having the right SOA governance model in place is critical to mitigating this risk and maximizing business performance.

As integration moves from SOA services to RESTful service APIs, do SOA governance practices still apply? Organizations desire to encourage API interactions and apply governance practices across their API partners.

Installing the registry and the ESB is pretty easy. You can find the download for the WSO2 registry here (http://wso2.org/downloads/governance-registry) and for Mule here (http://www.mulesoft.org/download-mule-esb-community-edition). Both come packaged in various formats which can just extract into the directory of your choice. Now we'll start these applications to see if they are installed correctly. For Mule you can use the following command: /bin/mule.bat, and for the registry: /bin/wso2server.bat. If you're not on windows there is also a /bin/mule and a /bin/wso2serversh which you can use.

Read the full story here.

When you have many services it is a good thing to register them somewhere so your consumers can easily find them, see what they are about, determine whether the service levels are good enough etc. When you look back at the heyday of SOA everyone was pusing registries (or repositories, but that terminology is a different subject). To fully do SOA you needed a UDDI registry to accompany your SOAP based services, defined by a WSDL and XML Schemas.

Read the full article here.

Part 1: Introduction to Configurable Governance Artifacts

This session aims at understanding the concepts and usage of Configurable Governance Artifacts within the context of extending registry functionalities. It will start with an in-dept introduction to Configurable Artifacts followed by configuration.

Enterprises look for governance solutions that can help manage their people, processes, and policies. Service-oriented architecture (SOA) governance brings the arsenal of tools and frameworks that help developers and administrators to more effectively and efficiently manage these aspects of the enterprise. In his WSO2Con 2011 session, Senaka discussed the key concepts of SOA governance, how to incorporate governance in the enterprise, and how the WSO2 Governance Registry can help manage application development, testing and deployment processes, as well as service lifecycles and assets. Here are highlights from his talk.

He is a member of the Apache Software Foundation (ASF), and also a Project Management Committee (PMC) member and committer for a number of projects at the ASF. Senaka founded WSO2 WSF/C++ during his internship at WSO2 in 2008.

Governance is part and parcel of rapidly evolving businesses. It is critical that you have the right processes and policies in place to ensure the smooth running of your business in a rapidly reshaping eco-system. Governance is not only about monitoring and managing your services once they have been developed. It is also about developing them right, and meeting stakeholder expectations.