This document discusses how WSO2 Governance Registry can be used to manage ESB artifacts through their lifecycle. It defines customizable lifecycle models to control the transition of artifacts between development, QA, and production environments. Checklists ensure artifacts meet requirements before moving to the next stage. The registry tracks the location and state of each artifact as it progresses from one environment to another. A demo then illustrates how a sample artifact moves from development to QA to production while being managed by the registry.

1. Managing ESB artifacts using Governance
Registry
Arudsothy
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 cloud
platform
– 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 application
infrastructure
– 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 ESB
named as ESB artifacts, In other word these artifacts are used to
make a complete service invocation in an Enterprise.
} Here are some example of enterprise service artifacts that can
be managed by WSO2 Governance Registry
– Proxy service
– WSDL
– Policy
– Endpoint
} Therefore enterprises need to manage the above artifacts in
SOA environment. When the ESB artifacts are managed they
will be called “Managed ESB Artifacts”

6. Need of LC management to manage ESB artifacts
} In a typical SOA, the service artifacts are subjected to move
through varies environment. Therefore there is a need for the
enterprises to manage their service artifacts
} When an ESB artifacts are moved from one environment to
another, the transition need to be controlled. Therefore the
enterprises need a reliable stable lifecycle management
capability.
} Each state of the artifact is associated with its relevant set of
people until it goes to production. Therefore enterprises want a
mechanism to determine what needs to be done for the artifacts
to move to production.
} Gives a kind of feedback to the people who have been
involved, by analyzing the state of the artifact .

7. How Governance Registry manages ESB artifacts
} Define SCXML based customizable lifecycle configuration model
to manage ESB artifacts
} Checklist items determine whether the particular artifact can be
moved or not when state transition is taken place
} Move to next environment when promote as well as move back to
previous environment when demote
} Each state of an artifact is associated with a storage location in
the Governance registry
} The WSO2 Governance Registry provides the information about
what 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 are
running.
} Governance Registry has 3 storage location named Dev, QA
and Prod associated with ESB Dev, QA and Prod instances
respectively.
} Therefore ESB artifact in Dev environment has been mounted to
“Dev” storage location in WSO2 Governance Registry. Similar
concept 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 be
saved 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 checklist
completion. If the checked items are adequate to promote, the
artifact will be promoted to QA state
} Before promote, the artifact was mounted into a “dev” storage
location in the Governance Registry
} After promote to QA state, artifact has been moved to QA
storage 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
} http://docs.wso2.org/wiki/display/ESB460/Sharing+Registry
+Space+Among+Multiple+Products
} http://docs.wso2.org/wiki/display/Governance453/Remote
+Instance+and+Mount+Configuration+Details
} http://docs.wso2.org/wiki/display/Governance453/Lifecycles
} http://docs.wso2.org/wiki/display/ESB460/Remote+Registry
+Instance+Configuration

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 development
and going into production, WSO2 is your partner in
ensuring 100% project success

15. Engage with WSO2
• Helping you get the most out of your deployments
• From project evaluation and inception to development
and going into production, WSO2 is your partner in
ensuring 100% project success