Chapter 13. Running and deploying Camel
This chapter covers
- Starting Camel
- Starting and stopping routes at runtime
- Shutting down Camel
- Deploying Camel
In the previous chapter, you learned all about monitoring and managing Camel. We’ll now shift focus to another topic that’s important to master: running and deploying Camel applications.
We’ll start with the topic of running Camel—you’ll need to fully understand how to start, run, and shut down Camel reliably and safely, which is imperative in a production environment. We’ll also review various options you can use to tweak how Camel and routes are started. We’ll continue on this path, looking at how you can dynamically start and stop routes at runtime. Your applications won’t run forever, so we’ll spend some time focusing on how to shut down Camel in a safe manner.
The other part of the chapter covers various strategies for deploying Camel. We’ll take a look at four common runtime environments supported by Camel.
As we discuss these topics, we’ll work through an example involving Rider Auto Parts. You’ve been asked to help move a recently developed application safely into production. The application receives inventory updates from suppliers, provided via a web service or files. Figure 13.1 shows a high-level diagram of the application.
Figure 13.1. A Rider Auto Parts application accepting incoming inventory updates from either files or a web service
