Case Studies of WSO2 Greg and ESB

I am trying to use Greg to store the endpoint URL for services deployed in containers other than WSO2 (Weblogic / JBoss). I would like to use the WSO2 ESB to mediate and route data through these endpoints.

However, when I look at the WSB2 ESB samples, it is not clear how I instruct the ESB to use WSO2 Greg. The following is the xml used to use the ESB in a registry deployed to the file system.

<definitions xmlns="http://ws.apache.org/ns/synapse"> <registry provider="org.wso2.carbon.mediation.registry.ESBRegistry"> <parameter name="root">file:./repository/samples/resources/</parameter> <parameter name="cachableDuration">15000</parameter> </registry> </definitions> 

My guess is that the registry tag provider element should probably be overridden by the web service address providing access to Greg.

When all is said and done, I would like to create simple BPMN configuration files that connect to Greg, get the URIs and URLs for the services used by this file, and then refer to them as properties later on the BPMN route.

First question: is this a standard configuration, or is there a better way to integrate the WSO ESB and Greg.

The second question: are there any examples that I can refer to that will answer this question?

+4
source share
2 answers

Please refer to the documentation.

[1] http://wso2.org/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances

[2] http://docs.wso2.org/wiki/display/ESB460/Storing+Various+WSO2+Enterprise+Service+Bus+Configurations

These include how you can store and use the WSO2 management registry at a high level.

If you need to manage endpoints through an API in the management registry, this will help.

[3] http://docs.wso2.org/wiki/display/Governance453/Endpoints+with+Governance+API

[4] http://docs.wso2.org/wiki/display/Governance453/Endpoint+Look-up+Sample

This thread later includes some tips on how you can access custom stored properties in the registry.

[5] How to access the system property from the WSO2 ESB and registry

+3
source

The WSO2 Management Register is a metadata repository, so you can use it to store SOA artifacts (WSDL, schemas, policies, mediation, customs artifacts, etc.) of your deployment. After that, you can manage these artifacts through the management registry. You can find more detailed information in the ESB documentation [1].

[1] http://docs.wso2.org/wiki/display/ESB460/Config+and+Governance+Partitions+in+a+Remote+Registry

Thanks and respect,

Ajith

0
source

All Articles