Getting Started with Camel Quarkus Extensions
TECHNOLOGY PREVIEW - Getting Started with Camel Quarkus Extensions
Chapter 1. TECHNOLOGY PREVIEW - Getting Started with Camel Quarkus Extensions
Camel Quarkus is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.
These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview.
This guide introduces Red Hat Integration - Camel Quarkus Extensions, how to get started building a quickstart Camel Quarkus application and how to deploy the application on OpenShift.
Red Hat provides Maven repositories that host the content we ship with our products. These repositories are available to download from the software downloads page.
For Camel Quarkus the following repositories are required:
Installation of Camel Quarkus in offline mode is not supported in this release.
1.1. Camel Quarkus overview
The Camel Quarkus project brings the integration capabilities of Apache Camel and its vast component library to the Quarkus runtime.
The benefits of using Camel Quarkus include the following:
- Enables users to take advantage of the performance benefits, developer joy and the container first ethos which Quarkus provides.
- Provides Quarkus extensions for many of the Apache Camel components.
- Takes advantage of the many performance improvements made in Camel 3, which results in a lower memory footprint, less reliance on reflection and faster startup times.
You can define Camel routes using the Java DSL.
1.2. Deploying Quarkus applications on OpenShift
To learn how to deploy your Camel Quarkus applications on OpenShift, please refer to the Deploying your Quarkus applications on Red Hat OpenShift Container Platform guide.
1.3. Getting started with the file consumer quickstart example
You can download or clone the quickstarts from the Camel Quarkus Examples Git repository. The example is in the
Extract the contents of the zip file or clone the repository to a local folder, for example a new folder named
You can run this Camel Quarkus example in development mode on your local machine from the command line. Using development mode, you can iterate quickly on integrations in development and get fast feedback on your code. Please refer to the Development mode section of the Camel Quarkus User guide for more details.
If you need to configure container resource limits or enable the Quarkus Kubernetes client to trust self signed certificates, you can find these configuration options in the
cluster adminaccess to the OpenShift cluster.
You have access to an SFTP server and you have set the server properties (which are prefixed by
ftp) in the application properties configuration file:
Use Maven to build the example application in development mode:
$ cd quickstarts/file-bindy-ftp $ mvn clean compile quarkus:dev
The application triggers the timer component every 10 seconds, generates some random “books” data and creates a CSV file in a temporary directory with 100 entries. The following message is displayed in the console:
[route1] (Camel (camel-1) thread #3 - timer://generateBooks) Generating randomized books CSV data
Next, the CSV file is read by a file consumer and Bindy is used to marshal the individual data rows into Book objects:
[route2] (Camel (camel-1) thread #1 - file:///tmp/books) Reading books CSV data from 89A0EE24CB03A69-0000000000000000
Next the collection of Book objects is split into individual items and is aggregated based on the genre property:
[route3] (Camel (camel-1) thread #0 - AggregateTimeoutChecker) Processed 34 books for genre 'Action' [route3] (Camel (camel-1) thread #0 - AggregateTimeoutChecker) Processed 31 books for genre 'Crime' [route3] (Camel (camel-1) thread #0 - AggregateTimeoutChecker) Processed 35 books for genre 'Horror'
Finally, the aggregated book collections are unmarshalled back to CSV format and uploaded to the test FTP server.
[route4] (Camel (camel-1) thread #2 - seda://processed) Uploaded books-Action-89A0EE24CB03A69-0000000000000069.csv [route4] (Camel (camel-1) thread #2 - seda://processed) Uploaded books-Crime-89A0EE24CB03A69-0000000000000069.csv [route4] (Camel (camel-1) thread #2 - seda://processed) Uploaded books-Horror-89A0EE24CB03A69-0000000000000069.csv
To run the application in JVM mode, enter the following commands:
$ mvn clean package -DskipTests $ java -jar target/*-runner.jar
You can build and deploy the example application to OpenShift, by entering the following command:
$ mvn clean package -DskipTests -Dquarkus.kubernetes.deploy=true
Check that the pods are running:
$oc get pods NAME READY STATUS RESTARTS AGE camel-quarkus-examples-file-bindy-ftp-1-d72mb 1/1 Running 0 5m15s ssh-server-deployment-5f6f685658-jtr9n 1/1 Running 0 5m28s
Optional: Enter the following command to monitor the application log:
oc logs -f camel-quarkus-examples-file-bindy-ftp-5d48f4d85c-sjl8k