Ce contenu n'est pas disponible dans la langue sélectionnée.

Kaoto


Red Hat build of Apache Camel 4.4

Create and edit integrations based on Apache Camel with Kaoto

Abstract

This guide provides a comprehensive overview of Kaoto, a visual design tool tailored for creating Apache Camel integrations. It covers both the installation process and the utilization of Kaoto to expedite the development lifecycle.

Chapter 1. Overview of Kaoto

Important

The VS Code extensions for Apache Camel are listed as development support. For more information about the scope of development support, see Development Support Scope of Coverage for Red Hat Build of Apache Camel.

Kaoto is an acronym for Kamel Orchestration Tool. It is a low code and no code integration designer to create and edit integrations based on Apache Camel. Kaoto is extendable, flexible, and adaptable to different use cases. For more information about the history of Kaoto, see Statistics and History of Kaoto.

Kaoto offers a rich catalog of building blocks for use in graphical design. By default, Kaoto loads the official upstream Camel Catalog and Kamelet Catalog.

Benefits of using Kaoto can be listed as follows:

  • Enhanced Visual Development Experience

    By leveraging Kaoto’s visual designing capabilities, users can intuitively create, view, and edit Camel integrations through the user interface. This low-code/no-code approach significantly reduces the learning curve for new users and accelerates the development process for seasoned developers.

  • Comprehensive Component Catalog Accessibility

    Kaoto provides immediate access to a rich catalog of Camel components, enterprise integration patterns (EIPs), and Kamelets. This extensive Catalog enables developers to easily find and implement the necessary components for their integration solutions. By having these resources readily available, developers can focus more on solving business problems rather than spending time searching for and learning about different components.

  • Streamlined Integration Development Process

    The platform is designed with an efficient user experience in mind, optimizing the steps required to create comprehensive integrations. This efficiency is achieved through features like auto-completion, configuration forms, and interactive feedback mechanisms. As a result, developers can quickly assemble and configure integrations, reducing the overall development time. This streamlined process encourages experimentation and innovation by making it easier to prototype and test different approaches.

1.1. Why Kaoto?

  • Camel at Heart

    Using the power of Apache Camel: Kaoto utilizes the Apache Camel models and schemas to always offer you all available Camel features.

  • Local Development

    VS Code Extension: We provide Kaoto as an extension you can install from the Microsoft Marketplace and also from the Open VSX Marketplace.

  • LCNC: Low Code and No Code

    Care about developers: You can seamlessly switch between any IDE and Kaoto, allowing mixed teams and converting low-code integrators to developers.

  • FLOSS heart

    Free Libre and Open Source Forever: Truly open with no vendor lock-in. Use, reuse, share, modify, and resell to the users' needs.

Chapter 2. Installing Kaoto

Important

It is recommended to install the Extension Pack for Apache Camel by Red Hat. It will provide a set of tools to manage, edit, run, and debug Camel integrations in various contexts.

The following procedure explains how to install VS Code and other essential extensions required to get started with Kaoto.

  1. If you do not have Visual Studio Code installed, install it from here.
  2. Launch VS Code.
  3. Install the Extension Pack for Apache Camel by Red Hat into your Visual Studio Code instance.
  4. To run and debug Camel integrations using VS Code UI, install JBang CLI. Optionally, to run Camel integrations from the command line, install Camel CLI.
Important

Create and select a workspace folder where all the integration will be stored. Selecting a workspace is important to ensure all required commands will be available and behave correctly.

Chapter 3. Getting started with Kaoto

The following procedure explains how to create and store integrations with Kaoto.

  1. Open VS Code and select "Open Folder".

  2. In the folder selection dialog select the folder to store your integrations or create a new folder and select it.
  3. Open Command Palette (Ctrl+Shift+P), paste the following command, and press enter.

    Create a Camel route using YAML DSL
    Copy to Clipboard Toggle word wrap
  4. Provide a name for the new file without extension and press enter.

  5. The file is created with extension camel.yaml. (Here: demo.camel.yaml).

  6. Select the log step to configure the Message in the configuration panel.

  7. Using the icons below the route image, you can choose between a vertical/horizontal layout of the route, zoom in/out, etc. Open Catalog on the far right displays the Camel catalog. There are also several filtering options in the Catalog, which greatly simplifies finding what you need.
  8. To add a component to the Camel route, click on the dot pattern of an existing component or invoke the right-click context menu on the step and select "Append".

  9. The camel component Catalog will be displayed, click on the additional component and it will be added to the route.

  10. To remove the added component from the Camel route, click on the dot pattern of the existing component or invoke the right-click context menu on the step and select "Delete".

  11. The existing component will be removed from the route.

3.1. Running the Camel Route

To get started with simple routes, they can be launched with Camel JBang.

  1. With demo.camel.yaml open, click the button Run Camel Application with JBang in the editor quick action menu at the top right of the editor.

  2. The terminal will open with the running Camel route. It can take several seconds the first time for Camel JBang to initialize.

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat