
Camel integrations
Weik.io
- 1
3:15Your first integration (Camel 1)
Weik.io
A folder of Apache Camel files on your machine becomes an integration running in devtest and logging to the terminal and the admin UI. It needs a Weik.io installation with an online agent.
- 2
3:36Change it and run it again (Camel 2)
Weik.io
One command publishes an edited folder and moves the deployment to the new version, and every older version is kept. The same folder can also run on your own machine, publishing nothing.
- 3
4:04What a running integration is doing (Camel 3)
Weik.io
A failing step in the hello integration shows how to read what a running integration does, from its logs and failure counts to the trace of one message, in the terminal and the admin UI.
- 4
3:56Where the values live (Camel 4)
Weik.io
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. A key the file itself defines is not overridden.
- 5
3:59Connecting to another system (Camel 5)
Weik.io
An integration that calls an outside HTTP service needs extra libraries, declared in integration.yaml and resolved by the hub from Maven Central at publish. Kamelets, Camel's reusable building blocks, are covered too.
- 6
3:03Custom metrics (Camel 6)
Weik.io
An integration can count something of its own, such as invoices processed, with one more step in its route. The Weik.io CLI and the admin UI show that counter beside the integration's other figures.