Hi Alex, Not sure if I get your problem right: If you can not access server C remotely (NFS, SMB, FTP, …) you will have to run Camel locally on server C. You can connect to ActiveMQ on server A and consume from there and produce to a local file on C. I am not sure if it is a great idea to send files via a queue (however I have seen this in production)... If you could access C remotely you could deploy your camel routes to ActiveMQ directly, not needing a separate Camel instance.
Cheers, Thomas. Am 05.06.2014 um 14:07 schrieb alx <[email protected]>: > Hi, > I am new to Camel. > I was wondering if it is possible to deploy Camel so that I have one > ActiveMQ instance on server A and two Camel instances on servers B and C. > > I read about the file component which can write the body of a message to a > local file: I would like instead to have a file component running on server > C that consumes a message from a queue and writes the message body to a > local file (local to server C). The reason is that I have an application > running on server C that can only be integrated by providing files to its > local folder structure. > > Is this distributed approach the best way forward? If so, how do I deploy > it? If not, what do you advise? > > Thanks! > Alex > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/distributed-file-copy-tp5751920.html > Sent from the Camel - Users mailing list archive at Nabble.com.
signature.asc
Description: Message signed with OpenPGP using GPGMail
