Last Updated: Jan. 2014
Lead, WSO2 Governance Registry
Subash Chaturanga
Webinar Title
**
About the Presenter(s)
Subash Chaturanga
Senior Software Engineer
๏ Works with the integrations
technologies team and f...
**
About WSO2
๏ Global enterprise, founded in
2005 by acknowledged leaders in
XML, web services technologies,
standards an...
**
What WSO2 delivers
*
Outline
- Importance of a registry and a repository for an Enterprise Integration Platform
- Impact analysis on ESB arti...
*
Shared Repository for a service mediation platform
• Why need a shared repository ?
• Deployments are complex, usually d...
*
Shared Repository for a service mediation platform
• Advantages when G-Reg used as the repository
• Stored configs are s...
*
Impact Analysis of ESB artifacts
• Why ?
• Huge deployments
• Many proxy services,sequences,endpoints
• Many inter depen...
*
Impact Analysis of ESB artifacts
• How ?
• WSO2 G-Reg smoothly plugs into WSO2 ESB
• No need to share the data bases.
• ...
*
Environment-specific asset management of an ESB
cluster from a centralized G-Reg
• Advantages ?
• Single place to manage...
*
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 envi...
*
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 everyw...
*
Proper Governance on ESB artifacts (endpoints)
• General use case:
• A Service is defined (i.e WSDL document).
• In G-Re...
*
Demo
**
Business Model
**
More Information !
๏ Download - http://wso2.com/products/governance-registry/
Contact us !
Upcoming SlideShare
Loading in …5
×

Governance beyond ESB

550 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
550
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
38
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Governance beyond ESB

  1. 1. Last Updated: Jan. 2014 Lead, WSO2 Governance Registry Subash Chaturanga Webinar Title
  2. 2. ** About the Presenter(s) Subash Chaturanga Senior Software Engineer ๏ Works with the integrations technologies team and focuses on WSO2 Governance Registry. ๏ Committer of the Apache Software Foundation
  3. 3. ** 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
  4. 4. ** What WSO2 delivers
  5. 5. * 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)
  6. 6. * 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.
  7. 7. * 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
  8. 8. * 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
  9. 9. * 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.
  10. 10. * 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.
  11. 11. * Environment-specific asset management of an ESB cluster from a centralized G-Reg • One G-Reg per environment
  12. 12. * Environment-specific asset management of an ESB cluster from a centralized G-Reg • One Embedded Registry(G-Reg) per environment
  13. 13. * Environment-specific asset management of an ESB cluster from a centralized G-Reg • Shared G-Reg for all the environments
  14. 14. * 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
  15. 15. * 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.
  16. 16. * Demo
  17. 17. ** Business Model
  18. 18. ** More Information ! ๏ Download - http://wso2.com/products/governance-registry/
  19. 19. Contact us !

×