At the registration, you will be asked to provide a username and password for the admin account. Use this credential to login as admin for the Stratos services and surf through the products. Here is a brief introduction on all the products currently available.

• Stratos Governance: Store and govern your services, wsdls, schemas, policies and other SOA artifacts
• Stratos Identity: Manage user bases, authentication mechanisms, permissions and all the identity aspects of your enterprise.
• Stratos Application Server: Host your web apps, web services and manage their QoS aspects like security, reliability.
• Stratos Gadgets Server: Write and host gadgets complaint with Google gadget standards.
• Stratos Mashup Server: Write mashup using scripting languages like javascript.
• Stratos Business Activity Monitor: Monitor activities of your services.
• Stratos Enterprise Service Bus: Coming soon with message routing, intermediate message transformations, task scheduling and many more features.

With this release WSO2 bring complete SOA stack to the cloud, Now your enterprise can enjoy the power of SOA without the hassle of maintaining your own SOA infrastructure.

ESB:

• Priority based mediation through priority executors
• WS-Discovery support and dynamic endpoint discovery
• Message Relay for efficient pass through of messages
• Component manager to install and uninstall features (provisioning support)
• Common Internet File System (CIFS) support through the VFS transport
• File locking functionality in the VFS transport to support concurrent polling
• Smooks mediator for efficient message transformation
• Enrich mediator for smart message manipulation
• OAuth mediator for 2-legged OAuth support
• Default endpoint UI
• Hot deploy and hot update configuration elements (sequences, endpoints, proxy services etc)
• Transport level statistics collection and monitoring
• POX security support
• Dependency detection and alerting for mediation configuration elements
• Mediation statistics API and custom mediation statistics consumers
• Multiple certificate/identity support in the NHTTP transport sender
• Improved logging capabilities for the NHTTP transport
• Templates based proxy service development in the UI
• Dashboard to monitor server environment and runtime
• Easy creation and management capabilities for dynamic sequences and endpoints
• Pagination to service management, endpoint management and sequence management UIs
• Obtaining resources like WSDL’s through web proxy servers

Governance Registry

• Gadgets for impact analysis on services and registry resources
• WSDL custom view
• Dynamic Handler configuration
• Handler simulator
• Tree-based Resource view
• API to govern SOA artifacts
• Complete Web Services API for Registry
• Improved options for Service discovery
• WS-Discovery support
• Scripting support for lifecycle management
• Improved P2 based provisioning and feature management support
• Support for adding remote mounts
• Platform, and Group/Cluster based deployment model
• Support for multiple server instances
• E-mail verification for subscriptions
• Support for deleting tags and comments
• Support for PostgreSQL and DB2 DBMS
• Paged activity and resource search
• Hierarchical permission model with granular and extensible permissions
• Ability to upload metadata (in addition to importing)
• Governance Archive for uploading WSDLs and Schemas with imports
• Ability to update resource content by uploading
• Rich text editor for editing text resources
• XML editor for editing handler, lifecycle and service UI configurations

Web Service Application Server (WSO2 WSAS):

• Component Manager – The UI tool to install/uninstall Carbon featrues.
• Various bug fixes & enhancements including architectural improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2 Carbon & other projects.
• Equinox P2 based provisioning support – extend your WSAS instance by installin new P2 features. See P2 based provisioning in WSO2 Carbon
• Hierarchical service support for Axis2 services, JAX-WS services, Spring services & Jar services
• Report generation for deployed services

Identity Server:

• SAML 2.0 based Single Sign-on support
• OAuth Support
• Support for bulk-user import
• Various bug fixes and enhancements including architectural improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2 Carbon and other projects.

Here I’m talking about how to use a popular feature available in Governance Registry, inside WSO2 Governance as a Service. i.e. Remote Registry Client. With Remote Registry Client, you can access the resources in registry programatically. It uses atom/pub protocol to communicate with the registry server.

Here is an example of using Remote Registry Client. I assumed I have an account with domain name ‘example.com’ with a user name ‘example_user’ (‘example_password’). You have to change this to valid values before running this code, You can create an account in Governance as a Service freely for a limited use.

import java.net.URL;
import org.wso2.carbon.registry.core.Registry;
import org.wso2.carbon.registry.core.Resource;
import org.wso2.carbon.registry.app.RemoteRegistry;

class RegistryDemo {
    public static void main(String[] args) throws Exception {

        // calls the registry with the authentication information
        callRemoteRegistry("http://governance.cloud.wso2.com/registry",
                   "example_username@example.com", "example_password");
    }

    public static void callRemoteRegistry(String url, String username,
                       String password) throws Exception {

        Registry myRegistry = new RemoteRegistry(new URL(url), username, password);
        if (!myRegistry.resourceExists("/demoResource")) {

            Resource r = myRegistry.newResource();
            r.setContent("demo content");
            myRegistry.put("/demoResource", r);
        }

        Resource r = myRegistry.get("/demoResource");
        byte[] contentBytes = (byte[])r.getContent();
        String content = new String(contentBytes);
        System.out.println("Content: " + content);
    }
}

In order to identify your account, you have to provide the domain name of your organization. I will demonstrate how to create an account using the “ws.dimuthu.org” as my domain name.

1. First go to http://governance.cloud.wso2.com from a web browser and click the ‘Register’ button. You will be asked to enter the domain name as the first step.

Enter the domain

After that, you have the option of validating the ownership of the domain right at the registration process, or you can skip the validation and continue to the next step in which case your domain will be appended ‘-trial’ suffix. You can validate the ownership of the domain later at any stage.

Here I want to validate the domain right now, so I click ‘Take me to the domain ownership confirmation page straight-away’ and click the ‘Submit’ button.

2. This will redirect you to the domain ownership validation page. You can validate the ownership of your domain in one of two ways.

Method i). Just create a text file named ‘wso2gaas.txt’ in the web root of your domain and enter the given text. This is the most simplest method of two.

Validate domain name using Textfile

Method ii). You can put a DNS entry according to the given instructions. This is a little tedious approch to validate the domain. In fact it may take a while to propagate the new DNS information, so you may have to wait hours without refreshing the page until you finally validate the domain ownership.

Click the continue button after the domain validation done. Then you will be redirected to a page requesting more information.

3. Tenant Registration Page

Tenant Registration

4) After this step, you will be notified to check for your email which will contain a mail with a link to proceed with the registration. There you will be able to select a theme for your organization and finalize creating your account. Login to the admin account for your tenant with the credential you provided a the time of the registration.

The domain ownership validation was introduced to WSO2 Governance as a Service account registration only now. So for organizations who have already have account will have a message similar to this when they are trying to login to their account.

Info box at login

So the account I have registered using the domain name ‘example.com’ has been renamed to ‘example.com-trial’. As the instruction of the message says you can go to the account management page after the login and validate the domain ownership.

Account Management Page

• ESBS and SOA
• SOA Security
• Mashups and Business Process Management for SOA
• SOA Governance
• SOA with C, C++, PHP
• SOA Architecture Pattern

Visit here to find more details about the event, http://wso2.com/events/2009-us-soa-workshop/?soaotad=10072009

• WSO2 Governance Registry 3.0.1
• WSO2 ESB 2.1.1
• WOS2 Web Services Application Server (WSAS) 3.1.1
• WSO2 Identity Server (IS) 2.0.1
• WSO2 Mashup Server 2.0.0

Although the version numbers say this is minor patch release (Other than the Mashup Server which is shipping as a major release), in fact there are new features and improvements. Some basic new features shares among all of these products are

1. Improved registry level transaction Support.
2. Improved Support for deploying on top of Application Servers other than tomcat like WebSphere, WebLogic, and
   JBoss.
3. Support for Eclipse P2 based provisioning. (Yes, you can add/remove features from these WSO2 products , see https://wso2.org/wiki/display/carbon/p2-based-provisioning-support for more details)
4. Improved Remote Registry model

1. The New Name – s/Registry/Governance Registry

The product name itself changed from ‘Registry’ to ‘Governance Registry’ (abbreviated as ‘G-Reg’). As it may hint you, now the product is more focused on the ‘Governance’ aspects than just the ‘registry’ or a ‘repository’ aspects. In early releases, it mainly used to store, retrieve configurations and persistence data that the other products would need. Now you can govern these resources (Services, Policies, Processes, People) inside the G-Reg itself. It has emerged to become a complete tool that help you in governing your SOA platform.

2. Separate Views for Add/View/Remove Services

In G-Reg ‘Services’ along with Service MetaData (policies, wsdls, schemas) are distinguished from other resources, as they are the key resources in a SOA platform. You will be able to add/list/view services directly from the main menu in the G-Reg UI.

Add Service Metadata

When adding a service you will be prompted to provide additional details on the services. As they will help users in discovering these services. The fields of these details are configurable as you will change them according to the policies and requirements of your organizations, but the defaults will be adequate for most of the scenarios.  Additionally G-Reg will do WS-I validation as you add WSDLs, Schemas.
Note that this is an additional view you will get as you can still discover services on a tree view arranged according to their namespaces using the registry browser as in previous releases.

3. Service Life cycle Management with Check-lists

Managing service lifecycle is a core part of governing services. G-Reg provides you this functionality with a simple user interface.

Lifecycle states can be promoted or demoted. The state transition can be ‘Designing’ -> ‘Developing’ -> ‘Testing’ -> ‘Deployed’. You can enforce a validation of a checklist in promoting the state to the next level. This states and the associated check-list items are highly configurable as you will change them to suit to the process of your organizations as you wish.

And G-Reg is shipped with a sample that extend the lifecycle management functionality by making it distributed. In there as you promote or demote the state, the service resource will move its position. The user guide on ‘Distributed Life Cycle Management Sample’ will describe how to use this functionality in more details. This will be really useful if you are enforcing a structured permission model in managing lifecycles. For an example you can enforce only developer role will be able to modify, check or promote a service in the ‘Developing’ state and QA role has permission in promoting a service in ‘Testing’ state and so on.

4. Business Activity Monitoring (BAM)

This is a brand new feature provide in G-Reg. You may find the user guide on ‘BAM’ will be really helpful in configuring the servers you want to monitor. But in order to view the monitoring data you have to go to the dashboard, which is the next new feature.

5. Dashboard

For most of the you, this will be the coolest feature in the new G-Reg., an eye-catching dashboard filled with bunch of Gadgets.

Dashboard

The dashboard provides you the information related to runtime governance as well as design-time governance as described in the ‘Dashboard’ user guide.

6. Eventing and Notifications

If you want you to notified when a resource is updated or a lifecycle state of a service is changed, this feature will be really helpful. Look at the ‘Eventing and Notifications’ user guide on how you can get notified and the built-in events that you can listen.

7. Mount Remote Resources – Federating Registries

If you are maintaining two separate registry instances, this feature will enable you to share resources among them. In G-Reg you can create links to resources in remote registries (remote-links) as well as to the resources in the same registry (sym-links). Here is the user guide for ‘Sym Links and Remote Links’ to read more details of the subject.

8. User Profiles
The new G-Reg has the ability to keep multiple user profiles per user. A simple how to on creating profiles can be found in the user guide on ‘User Profiles’.

9. Checkin/Checkout with Local Filesystem

The new G-Reg is shipped with a command line tool that allows you to checkin and checkout registry resources with your local filesystem. If you are familiar with a version control system like subversion, the checkin/checkout commands will not be much difficult to you.

Checking out a resource is simple as (the following command is what you typed in linux, in windows you will use the checkin-client.bat instead).

./checkin-client.sh co / -u user -p user_pw

And to checkin,

./checkin-client.sh ci -u user -p user_pw

Similarly you can use this tool to create backups or move resource or resource hierarchy off-line. Here is a complete user guide on ‘Checkin-Client’.

10. Performance Boost

Last but not least, the new G-Reg is performing very fast than its predecessor. In the performance test, it was seen each primitive operation in the registry is at least 10% faster in this release, where as some operations are performing much faster (for an example, ‘Add Collection’ operation seemed 50% faster). And the remote registry calls also optimized by keeping a local cache (http-level-caching).

This was a list of most notable new features in addition to the bunch of the features that was already there in the previous releases. You will be able to download WSO2 Governance Registry freely from the product website, http://wso2.org/projects/governance-registry and evaulate these features as you want.