Skip to content
Weik.ioUniversity
Try Weik.io

Connecting to another system

Camel 5 · 4:30

An integration that calls an outside HTTP service needs extra libraries. You declare them in integration.yaml for Weik.io to resolve from Maven Central when you publish. The video also covers kamelets.

Download the mp4Recorded on 2026.2

What it covers

  • Calling an example service and logging fields from its JSON reply
  • Declaring camel:http and camel:jackson in the dependencies list of integration.yaml
  • A dependency as a Camel component name or as mvn:group:artifact:version
  • Finding a misspelled dependency in the build log with weikio logs --build --version
  • Listing the project's kamelets with weikio get kamelets and on the project page
  • Writing kamelets to disk with weikio kamelets pull to run locally without the installation

Commands in this video

Terminal
$ weikio run ./hello
$ weikio logs sandbox/hello --build --version 0.1.6
$ weikio get kamelets
$ weikio kamelets pull ./kamelets
Transcript
  1. 0:02Until now, hello worked with its own files.
  2. 0:05Now the route gains a call to another system.
  3. 0:11The drawing shows the hello folder and your Weik.io installation,
  4. 0:15as the earlier videos left them.
  5. 0:17Weik.io keeps all of hello's published versions,
  6. 0:21with 0.1.4 on top carrying latest.
  7. 0:25The deployment runs 0.1.4 on agent dev,
  8. 0:29as a plain Java process.
  9. 0:32Each Java process sends its log lines,
  10. 0:35traces and metrics to the installation.
  11. 0:40The panel shows the two files you write: the route,
  12. 0:43and the manifest with its example fields commented out.
  13. 0:49The route gained an HTTPS call to a service.
  14. 0:53The manifest names the dependency camel:http,
  15. 0:57so the build ships it with the integration.
  16. 1:00A Camel component is listed as camel: and its name.
  17. 1:04weikio run, the hello folder, publishes it as a new version.
  18. 1:100.1.5 builds with its library resolved, so it is latest.
  19. 1:18The deployment follows latest,
  20. 1:20so agent dev runs it in seconds.
  21. 1:22The log now carries the service's answer.
  22. 1:28Each tick the Java process makes
  23. 1:30the call with its Authorization header.
  24. 1:35The example service answers with JSON,
  25. 1:38which the route logs as it came.
  26. 1:44Weik.io resolves the dependencies when it builds a version.
  27. 1:48The route reads the answer as JSON now,
  28. 1:51so the manifest gains a second component, camel:jakson.
  29. 1:56weikio run, the hello folder, starts the build again.
  30. 2:00The name is misspelled,
  31. 2:01so the build fails and the run stops.
  32. 2:040.1.6 stays with its build log. Latest stays on 0.1.5,
  33. 2:11the last version that built.
  34. 2:15Agent dev still runs 0.1.5, so the answer keeps arriving.
  35. 2:25weikio logs for hello reads the build log of version 0.1.6.
  36. 2:32The last error names the artifact
  37. 2:34the build could not download.
  38. 2:39Fix the name, then weikio run, the hello folder, again.
  39. 2:430.1.7 builds, so latest moves to it.
  40. 2:50The deployment follows latest, so agent dev moves to 0.1.7.
  41. 2:56The logged answer now arrives as JSON fields.
  42. 3:03The installation also ships ready-made route pieces,
  43. 3:07called kamelets.
  44. 3:08weikio get kamelets lists the
  45. 3:11project's kamelets and the platform's.
  46. 3:15The project shares a kamelet, erp-cart-source,
  47. 3:19so every version the project builds carries it.
  48. 3:22A kamelet file in the integration's folder takes
  49. 3:25precedence over the project's and the platform's.
  50. 3:28The listing stays the same,
  51. 3:30because weikio get kamelets reads the project, not the folder.
  52. 3:37The admin UI lists the same kamelets.
  53. 3:41The Add kamelet dialog stores a kamelet
  54. 3:44file or YAML as a project kamelet.
  55. 3:50The last step pulls these kamelets onto disk.
  56. 3:53weikio kamelets pull, into a kamelets folder,
  57. 3:58writes one file per kamelet.
  58. 4:04This video added a call, libraries and kamelets.
  59. 4:08The manifest names libraries, so a wrong name stops only the build.
  60. 4:13The route calls out and logs the answer.
  61. 4:16Kamelets come from the project, platform or folder.

Next in this track

Camel 6 · 3:14 Custom metrics Watched

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo