1 Reply Latest reply on Mar 13, 2013 5:34 AM by davsclaus

Governance Registry and FuseESB

rcarotenuto Feb 25, 2013 5:45 AM

Hi,

I would like to use the "service registry" concept (example: UDDI) for discovery at run time the endpoint of the service.

I would like that Camel makes a query to the registry to get the physical endpoint.

It is feasible?!

In the perspective of registry/repository, ie to store WSDL/artifacts , how can FuseESB accomplish this (as WSO2 ESB)?

Thanks a lot,

Raffaele

1. Re: Governance Registry and FuseESB

davsclaus Mar 13, 2013 5:34 AM (in response to rcarotenuto)

Hi

Fuse ESB / JBoss Fuse does not come with a UDDI registry out of the box.
The JBoss SOA-P product is a SOA stack and has SOA governance and whatnot.

And JBoss recently announced a new SOA governance product S-RAMP
http://jboss-overlord.blogspot.se/2013/03/release-s-ramp-011-adds-governance.html

In Fuse ESB we use Fuse Fabric as our registry, as it has a distributed registry. For example you ask about how to lookup in a registry to find a physical location. This is built-in out of the box in Fuse Fabric.

For example we have a Camel fabric component that does exactly that. This allows you to send a message to a "fabric:foo" endpoint and then at runtime that gets mapped into a physical endpoint.
http://fuse.fusesource.org/fabric/docs/overview.html#Camel_Fabric

eg for example you can expose a service from a server with the name "foo" and then have clients be able to send messages to "foo" by just sending a message to "fabric:foo" then Fabric handles to lookup to see the physical endpoints and round robin select a live endpoint and use that. This allows you to have containers come and go without affecting the clients.

There is a example of this use-case here
https://github.com/fusesource/fuse/tree/master/fabric/fabric-examples/fabric-camel-cluster-loadbalancing

I am very sorry for the late reply.
Actions