Introduction to g reg 4.6.0

1,555 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,555
On SlideShare
0
From Embeds
0
Number of Embeds
373
Actions
Shares
0
Downloads
69
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Introduction to g reg 4.6.0

  1. 1. Last Updated: Jan. 2014 Introducing the WSO2 Governance Registry for SOA Governance Subash Chaturanga Lead, WSO2 Governance Registry
  2. 2. 2 About the Presenter(s) Subash Chaturanga Senior Software Engineer ! •Works with the Platform Technologies team and focuses on WSO2 Governance Registry. •Committer of the Apache Software Foundation
  3. 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. 4 What WSO2 delivers
  5. 5. 5 What We’ll Learn Today • What is Governance Registry • Architecture • Key features and how they meet SOA goals • What’s coming up
  6. 6. 6 The WSO2 Platform
  7. 7. 7 Governance Registry • Two Main Aspects • Resource Repository/Registry • Governance Framework
  8. 8. In Action Governance Registry Plays a Vital Role in the Carbon Platform
  9. 9. 9 Governance as a Service https://governance.stratoslive.wso2.com
  10. 10. 10 Architecture Features – Structure and Composition
  11. 11. 11 Architecture Storage Model – Database Schema • Simple Storage Model (17-table schema) • JIRA has 90 for an example • Simplicity ! Speed
  12. 12. 12 Key Features Strengths of Governance Registry • RXT Files • Lifecycles • Federation • Repository • Collaboration • Search • APIs & Extension Points • Tooling
  13. 13. 13 RXT FILES Section 1
  14. 14. 14 .RXT Files • Artifact Details • Media Type/Key • UI Labels • Icon Set • Storage Path • Listing User Interface • Column Configurations • Data Source • Hyperlink
  15. 15. 15 .RXT Files • Relationships • Dependency (Source/Target) • Association (Source/Target/Type) • Artifact Layout • Groups/Tables • Fields • Menu Configurations • Add Menu • List Menu • Configure Menu
  16. 16. 16 .RXT Files
  17. 17. 17 LIFECYCLES Section 2
  18. 18. 18 Lifecycles • Typically many resources in your Registry, such as service descriptions, should progress through a series of "lifecycle stages". ! • For instance, a service may start off as "created", then after quality assurance has confirmed that the service works as expected should be moved to "tested" stage.
  19. 19. 19 Lifecycles
  20. 20. 20 Lifecycle Management (LCM) • WSO2 Governance Registry has an extensible architecture to support LCM. • The default LCM allows users to promote, demote lifecycle states of a given resource. Furthermore, it can be configured to use checklists as well. • Users can develop their own lifecycle through simple configuration. – Custom states, Check List – Scripting support
  21. 21. 21 Lifecycles in action
  22. 22. 22 Lifecycle Configuration • Configurable through GUI. • Based on OASIS SCXML.
  23. 23. 23 Developing Custom Behaviour ● “Aspect” is one of the three extension points that provide a flexible, plug-in approach to link resources and to allow users to encode their own governance rules and policies in WSO2 Governance Registry. ● A Lifecycle is a specialised aspect. ● You can develop an aspect to perform desired actions.
  24. 24. 24 FEDERATION Section 3
  25. 25. 25 Federated Deployments • Configuration Registry Model
  26. 26. 26 Federated Deployments • Governance Registry Model
  27. 27. 27 Federated Deployments • Hybrid Model
  28. 28. 28 REPOSITORY Section 4
  29. 29. 29 Repository for Storing Data
  30. 30. 30 Collections & Resources • Collections & Resources • A node on the Repository can either be a Collection or a Resource. • Resource <=> File • Collection <=> Directory/Folder • Copying collection/resource to another path • Feed • Resource-level caching for performance
  31. 31. 31 Media Types • Identifies the type of the resource/collection • Can leave unspecified → will get default media type • Configured via mime.types, which is populated into repository at first start-up • Once the server has been started, configuration has to be done through Management Console
  32. 32. 32 Properties • Key-Value pairs
  33. 33. 33 Associations • An association is defined as a function of – Source Resource – Target Resource – Association Type
  34. 34. 34 Associations • A resource can have associations to other resources. • Association can be made with – A Registry path of a resource – A web URL
  35. 35. 35 Symbolic Links • Symbolic link is a link to an existing resource. You can view and navigate a symbolic link like you are viewing and navigating the original resource. • The symbolic link behave similar to – File shortcuts in Windows – Soft Links/Symbolic links in Linux
  36. 36. 36 Remote Links • A resource in a remote registry can be mounted as a resource in the current registry. We call the mounted resource as the remote link. • This can be defined as a symbolic link across registry.
  37. 37. 37 Versioning • The resource in the registry can be versioned, so you can later view history and restore an older version. • You can configure whether the resources (only non-collection) should be automatically versioned or not. – Properties – Comments – Tags – Ratings
  38. 38. 38 Configure Auto-Versioning • Change the following line in registry.xml ! • This is by default 'true', which mean by default all the changes are versioned. • The collections can not be auto versioned. But you can manually create versions (or snapshots).
  39. 39. 39 Configure What to Version • You have to set this configuration before the first run (When database doesn't have any data)
  40. 40. 40 Creating Checkpoints • You can create a checkpoint by accessing the resource and clicking the 'Create Checkpoint' link in the resource information panel.
  41. 41. 41 Permissions • Each resource/collection contains a set of permissions ●Read ●Write ●Delete ●Authorize • Permissions are role-based
  42. 42. 42 Permissions • Permissions are inherited • Allow has more priority than Deny • Special users •admin •system • Special roles •everyone •anonymous
  43. 43. 43 Retention • One user gets to define retentions for a resource in a FCFS manner. Ability to Deny operations for a given period.
  44. 44. 44 COLLABORATION Section 5
  45. 45. 45 Collaboration
  46. 46. 46 Comments • Adding Comments • Comment Feeds – https://<server>:<port>/registry/atom/<resource>;comments • Searching resources using comments
  47. 47. 47 Tags • Adding Tags • Searching resources using Tags
  48. 48. 48 Ratings • My Rating • Average Rating
  49. 49. 49 SEARCH Section 6
  50. 50. 50 Searching • Tag Search – Can search only the resources that contain the tag you are searching. ! • Advanced Search – Search using resource name, created date range, updated date range, tags, comments, property name, property value. ! • Content Search – Using Apache Lucene and Apache Solr
  51. 51. 51 Searching • Lifecycle Search – Can search for all resources having a particular lifecycle
  52. 52. 52 Searching • Activities Search – Can filter and read activities that were done on the resource repository.
  53. 53. 53 Filtering • Service Filter – The Basic and Advanced Filters can be used to filter the list of displayed services.
  54. 54. 54 Connectors to external world Section 7
  55. 55. Connectors • WSO2 – WSO2 API Manager – WSO2 Enterprise Service Bus – WSO2 Business Activity Monitor – WSO2 Complex Event Processing Server ! • Non-WSO2 – Oracle Service Bus – Alfresco OpenCMIS
  56. 56. 54 APIS & EXTENSION POINTS Section 7
  57. 57. 55 Home-grown APIs • Registry APIs – Registry WebService API (SOAP/REST) – Registry AtomPub API – Registry Management API (Admin API) – Registry Host Object (JavaScript) – Registry REST API ! • Governance APIs – Java Governance API – CRUD API for Configurable Governance Artifacts
  58. 58. 56 Home-grown APIs • Other Connector APIs – Registry Java Management Extensions (JMX) API – Registry Software Configuration Management (SCM) Plugin for Apache Maven
  59. 59. 57 Extension Points • Repository Extensions – Handlers – Filters – Aspects – Custom User Interfaces – SCM Connections – Query Processors
  60. 60. 58 Extension Points • Registry Extensions – Custom Reports – Scheduled Tasks – Statistics Collector – Custom Registry Provider for Federation
  61. 61. 59 Extension Points • Governance Framework Extensions – Configurable Governance Artifacts (RXT) – Lifecycle Operation Validators – Lifecycle Transition Executors – Lifecycle Transition User Interfaces – Lifecycle Transition Scripts – Custom Notifications
  62. 62. 60 Extensibility
  63. 63. TOOLING Section 8
  64. 64. 62 Developer Studio • WSO2 Registry Perspective
  65. 65. 63 Developer Studio • Resources Project
  66. 66. 64 OTHER FEATURES Section 9
  67. 67. 65 Other Features • Reporting • Task Scheduling • Subscriptions & Notifications
  68. 68. 61 Building a Connected Business • WSO2 governance platform extensibility helps you to ! build your own connected business! ! • To build a connected business you need an environment that is:! ! • Integrated! • Accessible! • Collaborative! • Adaptive!
  69. 69. 66 QUESTIONS ?
  70. 70. 5 Business Model
  71. 71. 6 More Information ! ๏ Include links to product downloads, white paper downloads , etc.
  72. 72. Contact us !

×