Camel integrations
6 videos · 23:30
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.
Videos
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. Camel 2 · 4:01 Change it and run it again weikio runpublishes an edited folder and moves the deployment to the new version, and every older version is kept.Watched
3. Camel 3 · 4:24 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. Camel 4 · 4:37 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. Camel 5 · 3:59 Connecting to another system An integration that calls an outside HTTP service needs extra libraries, declared in integration.yamland resolved by Weik.io from Maven Central when you publish.Watched
6. Camel 6 · 3:14 Custom metrics An integration can count something of its own, such as invoices processed, with a 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:
- Your first integration
Taught in Camel 1
- Integration folders and routes
Taught in Camel 1
- Versions and the developer loop
Taught in Camel 2
- Logs, metrics and traces
Taught in Camel 3
- Variables and secrets
Taught in Camel 4
- Dependencies and kamelets
Taught in Camel 5
- Custom metrics
Taught in Camel 6