Skip to content
Weik.ioUniversity
Try Weik.io

Camel integrations

6 videos · 21:53

Each video adds one step to the same integration, sandbox/hello, from the first publish to variables, secrets, dependencies, kamelets and custom metrics. You follow along on any installation with an online agent, and the Try Weik.io dev container is one.

Start the trackRead the Camel docs

Videos

  1. 1. Camel 1 · 3:15 Your first integration A folder of Apache Camel files on your machine becomes an integration running in devtest and logging to the terminal and the admin UI.Watched
  2. 2. Camel 2 · 3:36 Change it and run it again One command publishes an edited folder and moves the deployment to the new version, and every older version is kept.Watched
  3. 3. Camel 3 · 4:04 What a running integration is doing When a step of the hello integration starts failing, its logs, its failure counts and the trace of one message show what happened, in the terminal and in the admin UI.Watched
  4. 4. Camel 4 · 3:56 Where the values live Variables and secrets give an integration its values per environment, kept out of its files, and a new value takes effect at the next start.Watched
  5. 5. Camel 5 · 3:59 Connecting to another system An integration that calls an outside HTTP service needs extra libraries, declared in integration.yaml and resolved by the hub from Maven Central when you publish.Watched
  6. 6. Camel 6 · 3:03 Custom metrics An integration can count something of its own, such as invoices processed, with one more step in its route.Watched

Read in the docs

The Camel integrations group of the docs has the reference for this track. The videos teach these pages: