Glossary

Open-source integration framework that facilitates connecting systems and exchanging data between them using a route-based model.

Unique identifier used to authenticate and authorize an application’s access to an API.

Authorization flow of OAuth 2.0 that requests an authorization code for later exchange for an access token. Provides additional security by avoiding direct credential sharing and protecting against token interception.

Authorization flow of OAuth 2.0 that uses unique cryptographic challenges to protect against interception attacks.

Core of Apache Camel responsible for managing integration between systems. It uses a Domain Specific Language or DSL to define and build integration routes.

Authorization flow of OAuth 2.0 that uses client credentials to directly obtain access tokens without requiring end-user interaction.

Security extension in Authorization Code with PKCE that protects applications and access tokens using code challenges.

Step responsible for integrating with external systems. Translates information in protocols like HTTP to consume or send data via APIs.

Apache Camel component that acts as a data entry point, initiating the integration flow. See also Trigger.

Periodic scheduling expression in the format: <second><minute> <hour> <day of the month> <month> <day of the week><year>. Allows the use of special characters like *, ?, -, ,, /, and L to define more complex scheduling patterns. For example, the expression 0 0 12 * * ? triggers at 12 PM (noon) every day.

Artifact referenced by data transformation EIPs to determine the input or output data format. It facilitates data conversion between formats like XML, JSON, CSV, and others.

Process that relates one or more fields from a source dataset to their equivalents in the destination. In addition to establishing relationships, it ensures interoperability between data in different formats.

Low-code integration construction through a visual interface, the canvas. See also Source.

Language designed for a specific domain that allows users to define and configure routes and integrations. Camel supports DSLs in various languages, such as Java, Groovy, YAML, XML, among others.

Represents a connection point where data can be sent or received within an integration flow. Defines how data is accessed and manipulated in a system. Endpoints are referenced in the DSL through URIs.

Integration patterns that describe common solutions to frequent problems encountered in system integration and communication between applications.
They help structure and optimize communication between applications by providing methods for message routing, data transformation, message aggregation and splitting, message filtering, and error handling.
For detailed information, visit Enterprise Integration Patterns.

Object that encapsulates the message and some metadata during the exchange of information between systems. Additionally, it provides utility methods for use in integrations, such as the ability to save and retrieve properties.

Way of writing instructions in EIPs that help process and manipulate data as it passes through an integration route. For example, the condition for a Choice can be written using languages like Groovy, JSONPath, JQ, etc.

Variables allow custom configuration of the flow and environment parameterization, eliminating the need to create a separate integration flow for each environment. In Source-type flows, they can be created from the Diagram tab and the Source Code tab. To apply variables, provide the variable name in braces within the component, as in the HTTPS component example: uri: https://{{variable name}}.

Set of tools that perform operations with data within the integration flow. They can divert the flow based on configured conditions (Choice), iterate elements (For Each), transform simple and complex data (JSON Transformation), and execute alternative routes when there are errors that do not return a status code (On Exception) (Diagram-type flows only).

Set of interconnected steps that execute an automated integration process. Every flow starts with a Trigger.

JSONata is an open-source query and transformation language designed for JSON data. It allows you to access, filter, transform, and format JSON data efficiently and intuitively.

Main file of the integration flow. In Source mode, you edit the YAML code directly. In Diagram mode, this content is visually generated on the canvas. See also Resources.

Minimum unit of data that is propagated and modified along a route. It consists of two main components: header and body.

Authorization protocol that allows users to grant access to protected resources via access tokens without sharing their credentials. Integrations support three OAuth 2.0 authorization flows:

• Authorization Code

• Client Credentials

• Authorization with PKCE

Open-source format used to describe and document APIs.

Apache Camel component that acts as a connector, sending data and messages to external systems.

Auxiliary files to main.yaml, used to store configurations, scripts, or supporting data (such as JSONata expressions). They are accessible via classpath and created in the Diagram and Source Code tabs. Example of use for the JSONata component: uri: jsonata:classpath:extractTotal.jsonata.

Defines the path a message follows within the integration system, showing the processing steps applied to the message as it travels from a source to a destination.

Construction of integration flows that combines a low-code approach with code customization using Camel YAML DSL. See also Diagram.

Element of the integration flow that performs a specific function (trigger, connector, transformation, etc.). The number of steps in a flow is unlimited.

Step that initiates the execution of the integration flow, usually associated with external events or schedules. See also Consumer.