Governance Registry

We caught up with Maria Belkina of Russia’s Saint-Petersburg Information and Analytics Center after her presentation at WSO2Con 2011. There we discussed the government organization’s use of WSO2 Carbon middleware, including the WSO2 Enterprise Service Bus. Here is an edited version of our discussion. See video for full interview.

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.

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.

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.

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.