This blog entry is about how to use the OW2-Dragon SOA Governance with the OW2-PEtALS ESB.
Thanks to the flexible Fractal architecture PEtALS is based on, I have implemented the Dragon API and integrated it into a custom PEtALS distribution.
Here are some screenshots of my tests, I used the JSR181 Service Engine (based on PEtALS CDK and Axis2) to ‘quickly’ create a collection of JBI services with real WSDL descriptions which will be used in Dragon.
All the resources needed (PEtALS, Dragon and JBI artifacts) and their download links are listed at the bottom of this article.
At startup, PEtALS exposes the Dragon API implementation as a web service at http://localhost:9001/petals/ws/DragonService. This address is the one which as to used to fill the ‘Add Runtime Manager’ Dragon section.
Figure 2 – Sysnchronize execution environments
I just did a quick test and try to search all the services which have an operation which starts by ‘get’. Going to the ‘Search Service’ section and entering ‘get*’ in the search field returns me a list of compliant services.
The Dragon Web Application : http://download.forge.objectweb.org/dragon/dragon-0.9.1.war
The PEtALS-Dragon Enabled standalone distribution : http://maven.objectweb.org/maven2-snapshot/org/ow2/petals/petals-standalone-dragon/1.0-SNAPSHOT/petals-standalone-dragon-1.0-20090116.150059-1-light.zip