Hi, You can setup two SU based on HTTP : one as provider, another one as consumer. The consumer targets the service/endpoint of the producer. The producer is connected to your existing WebService.
Regards JB -- Jean-Baptiste Onofré j...@nanthrax.net BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net On Wed 28/01/09 04:26, "angeloNZ" angelo.ange...@nz.fujitsu.com wrote: > > Hi guys, > > I'm a newbie with servicemix and I've walked through the tutorials on > the servicemix site. I'm still trying to wrap my head around how to best > choose the correct servicemix component for what I'm trying to do. > Basically, I'm trying to do a simple project as best explained by this > diagram: > > client --> proxy web service in servicemix --> external web service > provider > I want to create a proxy web service in the ESB that would in turn call > an external web service. The proxy web service will only forward the > request to the external web service and return whatever the external web > service returns back to the client. > > My client will be sending requests using SOAP. Can I get guidance as > to which servicemix bc and se components I need to use for my use case? I > have an idea that I need a consumer (facing client) and provider BC (facing > external web service) for this but I'm not sure what SE component to use > to do the forwarding or in case I need to so some routing decisions > later. > Any guidance would be appreciated. Thanks. > > Angelo > > > -- > View this message in context: http://www.nabble.com/Which-servicemix-components-to-use-for-my > -simple-use-case-tp21699274p21699274.html Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > >
