Glossary

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

Unique identifier that allows an application to access an API and is used for authentication and access control.

An OAuth 2.0 authorization flow that requests an authorization code to exchange for an access token, providing additional security to protected resources and token interception.

An OAuth 2.0 authorization flow that prevents code interception with unique cryptographic challenges for each authorization request.

Core of Apache Camel, responsible for managing integration between systems. In it, the routing mechanism uses a DSL (Domain-Specific Language) to define and build routes.

A General Tool that performs a flow deviation within an integration based on conditions you can configure.

An OAuth 2.0 authorization flow that uses client credentials to directly obtain access tokens without requiring any end-user interaction.

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

A step that connects to third-party applications, translating information into specific protocols, such as the HTTP protocol, to interact with APIs.

Component of Apache Camel that receives events and data from external sources (see Trigger).

A string that defines periodic scheduling following a specific format: <minute> <hour> <day of month> <month> <day of week>.

A process that matches one or more fields from a source dataset to their equivalents in the target. In addition to establishing relationships, it ensures interoperability between data in different formats.

A type of integration flow design that enables low-code integration building through the Flow visual interface. This model uses triggers, connectors, and tools available on the canvas, simplifying development and making integration configuration more intuitive. The other available design is Source.

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

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.

A string that contains information applicable to the steps of the integration flow.

Alternative flow that is activated in case of error (except status code errors) in the execution of the integration flow. It begins in the step On Exception.

A way to write 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 such as Groovy, JSONPath, JQ etc.

A General Tool repetition method that executes the same code for each element of a list (array).

A set of tools that performs 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).

A set of interconnected steps that automate a process of integration between systems. The execution of the integration flow starts at the mandatory Start step and ends at the End step.

A General Tool that transforms simple and complex JSON data using JSONata language.

Authorization protocol that allows users to grant access to protected resources via access tokens without sharing their credentials.

A General Tool that executes alternative routes when there are errors that don’t return a status code. This way, the execution of the integration flow is not interrupted.

Open source format used to describe and document APIs.

Component of Apache Camel that sends data and messages to external systems (see Connector).

Defines the path that a message follows within the integration system, showing the processing steps applied to the message as it travels from a source to a destination. In diagram-type flows, it is the field where we select the combination of the HTTP method and the path that the step will use.

A type of integration flow design that allows the construction of integrations via code using the CAMEL YAML DSL. This model uses Camel components and EIPs to build the integration routes. The other available design is Diagram.

Component of the integration flow that can have different functions, such as a trigger or a connector. There is no limit to the quantity of steps that you can add to an integration flow.

Step that starts the execution of the integration flow and automatically replaces the Start step on the canvas.