Some random points: 1. Expose your service components over HTTP/S using SOAP or REST. Synapse integrates well with HTTP endpoints. 2. Synapse can integrate with any registry/repository implementation through a custom hook. See [1] for the interface that you need to implement. 3. If you want to package Synapse as a part of your application, you can turn it into a webapp or start it as a service using the ServerManager API [2]. Personally I'd prefer the second approach because it allows you to take advantage of the NIO HTTP transport of Synapse.
Thanks, Hiranya On Nov 7, 2012, at 7:56 AM, Kenneth Ohaeri <[email protected]> wrote: > Our solution to our customers comes as a shrink wrap software. In the > software we have several service components (using SCA development > approach), one repository manager that serves the other application > nodes with security and metadata. The entire composite applications > run on a portal front-end in three tier architecture (web, application > and reposity-manager/data store). We just wanted to use ESB to enable > mediation among them and leverage ESB capabilities to perform cross > component and web communications. > > We have our own security model that would be implemented as a service > within the composite applications. The ESB would be the hub for > routing from one node to the other as well as for routing requests > between the services or group of services between the nodes. > > I would greatly appreciate it if you can offer your suggestions about > how we can use Synapse to implement our solution as I describe it. Any > suggestions you provide would be greatly appreciated. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Hiranya Jayathilaka Mayhem Lab/RACE Lab; Dept. of Computer Science, UCSB; http://cs.ucsb.edu E-mail: [email protected]; Mobile: +1 (805) 895-7443 Blog: http://techfeast-hiranya.blogspot.com
