Last Updated: Jan. 2014

Lead, WSO2 Governance RegistrySubash Chaturanga

Webinar Title

**

About the Presenter(s)

Subash ChaturangaSenior Software Engineer

๏ Works with the integrationstechnologies team and focuses on WSO2 Governance Registry.๏ Committer of the Apache Software Foundation

**

About WSO2๏ Global enterprise, founded in

2005 by acknowledged leaders in XML, web services technologies, standards and open source

๏ Provides only open source platform-as-a-service for private, public and hybrid cloud deployments

๏ All WSO2 products are 100% open source and released under the Apache License Version 2.0.

๏ Is an Active Member of OASIS, Cloud Security Alliance, OSGi Alliance, AMQP Working Group, OpenID Foundation and W3C.

๏ Driven by Innovation

๏ Launched first open source API Management solution in 2012

๏ Launched App Factory in 2Q 2013

๏ Launched Enterprise Store and first open source Mobile solution in 4Q 2013

**

What WSO2 delivers

*

Outline

- Importance of a registry and a repository for an Enterprise Integration Platform - Impact analysis on ESB artifacts through G-Reg - Environment-specific asset management of an ESB cluster from a centralized G-Reg- Why and how you should apply proper governance on ESB artifacts (endpoints)

*

Shared Repository for a service mediation platform

• Why need a shared repository ?• Deployments are complex, usually distributed and clustered • Nodes in a homogeneous cluster have similar configs• Why duplicate same config in each node• Define configs in one place and federate them.

*

Shared Repository for a service mediation platform

• Advantages when G-Reg used as the repository• Stored configs are secured.• Stored configs can be properly maintained. • Stored configs an be remotely accessed and edit.• Updated configs reflected on the fly across the cluster

*

Impact Analysis of ESB artifacts

• Why ?• Huge deployments• Many proxy services,sequences,endpoints• Many inter dependencies• One change in sequence might affect to several proxy services

*

Impact Analysis of ESB artifacts

• How ?• WSO2 G-Reg smoothly plugs into WSO2 ESB• No need to share the data bases.• G-Reg only pulls ESB deployment meta data, but no pushing.

*

Environment-specific asset management of an ESB cluster from a centralized G-Reg

• Advantages ?• Single place to manage artifacts across WSO2 server clusters• No need to touch ESB proxy service configs when deployment environment

changes.• Update artifacts on the fly and make them available across the clusters without

any server downtime.• Role based authorization for ESB artifacts.

*

Environment-specific asset management of an ESB cluster from a centralized G-Reg

• One G-Reg per environment

*

Environment-specific asset management of an ESB cluster from a centralized G-Reg

• One Embedded Registry(G-Reg) per environment

*

Environment-specific asset management of an ESB cluster from a centralized G-Reg

• Shared G-Reg for all the environments

*

Environment-specific asset management of an ESB cluster from a centralized G-Reg

• Build Once• Deploy everything everywhere from a centralized place

• C-Apps • WSO2 Developer Studio

*

Proper Governance on ESB artifacts (endpoints)

• General use case:• A Service is defined (i.e WSDL document).• In G-Reg a corresponding service catalog is generated.• Service is attached to a design time governance lifecycle.• Service evolved through Development, Testing and Production states with

all design time governance policies.• Production Proxy service in ESB cluster is eligible to serve requests only

when the backend service is production ready.

*

Demo

**

Business Model

**

More Information !

๏ Download - http://wso2.com/products/governance-registry/

Contact us !