Managing ESB artifacts with the WSO2 Governance Registry

Like this? Share it with your network

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Can we leverage WSO2 governance registry features with other ESB or integration Products?
    Are you sure you want to
    Your message goes here
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 694 686 3 2 2 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Managing ESB artifacts using GovernanceRegistryArudsothy  Sriragu  (S  rArudsothy Sriragu(Senior Software Engineer-WSO2 Governance Registry)&Eranda Sooriyabandara(Senior Software Engineer-WSO2 Governance Registry)  Engineer-­‐WSO2  Governance  Registry)  &  Eranda  Sooriyabandara  (Senior  Software  Engineer-­‐WSO2  Governance  Registry)  
  • 2. About WSO2•  Providing the only complete open source componentized cloudplatform–  Dedicated to removing all the stumbling blocks to enterprise agility–  Enabling you to focus on business logic and business value•  Recognized by leading analyst firms as visionaries and leaders–  Gartner cites WSO2 as visionaries in all 3 categories of applicationinfrastructure–  Forrester places WSO2 in top 2 for API Management•  Global corporation with offices in USA, UK & Sri Lanka–  200+ employees and growing•  Business model of selling comprehensive support &maintenance for our products
  • 3. 150+ globally positioned support customers
  • 4. Agenda}  Enterprise Service Bus Artifacts}  Need of lifecycle management to manage ESB artifacts}  How Governance Registry manages ESB artifacts}  Demo}  Q&A
  • 5. Enterprise Service Bus Artifacts}  What does it mean by Enterprise Service Bus Artifacts?–  The Enterprise service related artifacts which are used by the ESBnamed as ESB artifacts, In other word these artifacts are used tomake a complete service invocation in an Enterprise.  }  Here are some example of enterprise service artifacts that canbe managed by WSO2 Governance Registry–  Proxy service–  WSDL–  Policy–  Endpoint  }  Therefore enterprises need to manage the above artifacts inSOA environment. When the ESB artifacts are managed theywill be called “Managed ESB Artifacts”
  • 6. Need of LC management to manage ESB artifacts}  In a typical SOA, the service artifacts are subjected to movethrough varies environment. Therefore there is a need for theenterprises to manage their service artifacts  }  When an ESB artifacts are moved from one environment toanother, the transition need to be controlled. Therefore theenterprises need a reliable stable lifecycle managementcapability.  }  Each state of the artifact is associated with its relevant set ofpeople until it goes to production. Therefore enterprises want amechanism to determine what needs to be done for the artifactsto move to production.      }  Gives a kind of feedback to the people who have beeninvolved, by analyzing the state of the artifact .    
  • 7. How Governance Registry manages ESB artifacts}  Define SCXML based customizable lifecycle configuration modelto manage ESB artifacts}  Checklist items determine whether the particular artifact can bemoved or not when state transition is taken place}  Move to next environment when promote as well as move back toprevious environment when demote}  Each state of an artifact is associated with a storage location inthe Governance registry}  The WSO2 Governance Registry provides the information aboutwhat needs to be carried out to transit the artifact back or forth
  • 8. Demo
  • 9. Demo
  • 10. Demo}  3 ESB instances for Dev, QA and Prod environments arerunning.}  Governance Registry has 3 storage location named Dev, QAand Prod associated with ESB Dev, QA and Prod instancesrespectively.}  Therefore ESB artifact in Dev environment has been mounted to“Dev” storage location in WSO2 Governance Registry. Similarconcept applies to ESB artifact in QA and Prod as well}  When “promote” ESB artifact move from Devà QA à Prod}  When “Demote” ESB artifact moves from Prod à QAà Dev
  • 11. Demo}  When a user add a service via the ESB dev instance, It will besaved into a location in ESB. Now it is in dev state}  A responsible user promotes the above service from dev to QA.Before promote, action will be validated against the checklistcompletion. If the checked items are adequate to promote, theartifact will be promoted to QA state}  Before promote, the artifact was mounted into a “dev” storagelocation in the Governance Registry}  After promote to QA state, artifact has been moved to QAstorage location in Governance Registry}  At the same time the artifact has been removed from the “Dev”ESB instance and stored into “QA” ESB instance
  • 12. References}}}}
  • 13. Questions and Answers        Q                  &                  A
  • 14. Engage with WSO2•  Helping you get the most out of your deployments•  From project evaluation and inception to developmentand going into production, WSO2 is your partner inensuring 100% project success
  • 15. Engage with WSO2•  Helping you get the most out of your deployments•  From project evaluation and inception to developmentand going into production, WSO2 is your partner inensuring 100% project success