The EAI Overview introduced us to some key terms and concepts, but now it is time to look at something in a little more detail. To help illustrate, let's look at a simple scenario.
File Processing SystemOnce again, let's keep things really simple for now. We will start to add complexity as we go. Right now have a need to create a file processing system that will do the following:
With Eclipse, we can create a new Maven Project using one of the available Camel Archetypes. The archetype we pick depends on the container we want to run it in and the DSL we want to use. Next we can create a route using our favourite DSL that contains the following:
File ProcessingAssuming that each of our application servers can access the same share or mount, we can do something like this:
Application AdaptersOne question still remaining is just how do we get these legacy systems to listen to a queue. One way is by creating an adapter that will listen to the queue and launch the application in a separate command line process. Since Apache Camel is just a library. We can do something like this: With Eclipse, we can create a new Maven Project using one of the available Camel Archetypes. Once again, the archetype we pick depends on the container we want to run it in and the DSL we want to use. Next we can create a route using our favourite DSL that contains the following:
|
Visit our Code Repository for samples and demos.
ARTICLES
All
|