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.

A context can be defined as a construct that strictly binds the execution environment. As the WSO2 Carbon Context is a runtime container for your app(s), you gain the benefit of leveraging the Carbon Context runtime API to obtain contextual information about various actors utilizing your web apps and web services. For example, you may want to use registry cache for a particular user or tenant. The Carbon Context allows you to access 5 APIs and has several utility methods. Each time we create something user specific, we create a Carbon Context for that user to store specific things. This is valid for all WSO2 Carbon 3.2.2 based servers.

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.

Since 2010, Russia has been implementing an e-government initiative, “Electronic Russia.” The goal of this initiative is to create and integrate the information systems of different government authorities and enable online data exchange. In support of this effort, the Saint-Petersburg Information and Analytics Center has built an open source integration layer to link together the government agencies’ many legacy systems. In her presentation at WSO2Con, Ms. Belkina described the objectives and challenges of the e-Government initiative, as well as the combination of home-grown software, WSO2 middleware, and other open source software used to implement the integration layer. Here are highlights from her talk.

Since 2007 Maria Belkina has been working as a Java Programmer for an organization which is commited into developing software for e-Government not only in Saint-Petersburg, but in other parts of the country, too. Last year she started working as a project manager on a project that aims to create a fully functional infrastructure for providing state services to citizens on-line and integrating various information systems that are involved in these processes.

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.

User customization and extending functionality is a key ingredient of WSO2’s product stack. The WSO2 Governance Registry is one such product that enables users to extend existing functionality by adding custom features. In such scenarios users are provided with extending API s such as Handlers, Filters and Aspects.