Glossary

A

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

API Key | Unique identifier used to authenticate and authorize an application's access to an API.

Authorization Code | OAuth 2.0 authorization flow 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 Code with PKCE | OAuth 2.0 authorization flow that uses unique cryptographic challenges to protect against interception attacks.

C

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

Canvas | Legacy design type with limited functionalities for building integrations in a low-code manner.

Client Credentials | OAuth 2.0 authorization flow that uses client credentials to obtain access tokens directly, without the need for end-user interaction.

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

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

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

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

D

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

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

Data Source | Allows you to connect your integration flows to databases using the JDBC component. You configure and save database access credentials only once, facilitating their reuse across different integration flows.

Diagram & Source Code | Integration flow construction approach that combines a low-code approach with code customization using Camel YAML DSL.

Domain-Specific Language (DSL) | 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.

E

Endpoint | 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.

Enterprise Integration Patterns (EIPs) | Integration patterns that describe common solutions to frequent problems encountered in integration systems 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.

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

Expression Language | Way of writing instructions in EIPs that help process and manipulate data as they pass through an integration route. For example, the condition for a Choice can be written using languages such as Groovy, JSONPath, JQ, etc.

F

Flow Variables | Variables allow for customized flow configuration 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, enter the variable name in curly braces within the component, as in the HTTPS component example: uri: https://{{variable name}}.

G

General Tools | Set of tools that perform operations with data within the integration flow. They can deviate 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 don't return a status code (On Exception) (Canvas-type flows only).

I

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

J

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

M

main.yaml | Main integration flow file, visible in the Source Code tab. This is where you directly edit the YAML code. In the Diagram tab, this content is generated visually. See also Resources.

Message | Minimum unit of data that is propagated and modified throughout a route. It is formed by two main components: header and body.

O

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

• Authorization Code • Client Credentials • Authorization with PKCE

Open API | Open-source format used to describe and document APIs.

P

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

R

Resources | 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. Usage example for the JSONata component: uri: jsonata:classpath:extractTotal.jsonata.

Route | 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.

S

Step | Integration flow element that performs a specific function (trigger, connector, transformation, etc.). The number of steps in a flow is unlimited.

T

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