What to know before you start
Concept 4 · 2:28
Find out how a Weik.io integration is put together before you write your first one. Its routes are Camel files in YAML, XML or Java, and a route that Camel refuses fails the publish.
This part of the video couldn't be loaded.
What it covers
- Short documents that configure a transfer, a schedule, a channel or change tracking
- Route files in YAML, XML or Java, kamelet files and a README
- A channel between two integrations, with a kamelet at each end
- A manifest for a version number, a specific Camel version or requirements
- A rollback to the previous version when a release goes wrong in production
- A Git pipeline that publishes each change and restores documents changed by hand
Commands in this video
This video explains with drawings and types no commands.
Transcript
- 0:01This video shows what to know before you write your first Weik.io integration.
- 0:10You configure a transfer, a schedule,
- 0:13a channel or change tracking in a short document,
- 0:16with no Camel in it.
- 0:22You add route files in YAML, XML or Java and kamelet files to the folder.
- 0:32A README appears on the integration's page in the admin UI.
- 0:40A route starts where a message comes in.
- 0:43One step adds the ERP's key to the message,
- 0:47then the next step sends the message to the ERP.
- 0:54The route ends at a kamelet that publishes into the channel.
- 0:58The integration that reads the channel starts at a kamelet.
- 1:02Weik.io finds a kamelet file by its file name.
- 1:10Without a manifest, the integration takes its name from the folder.
- 1:14You add the manifest for a version number, a specific Camel version or requirements.
- 1:23When you publish, Camel checks every route,
- 1:26so a route Camel refuses fails the publish with Camel's message.
- 1:31A changed folder needs a new version number.
- 1:39For development, you publish and deploy the change together,
- 1:42then follow the deployment's logs.
- 1:51When a release goes wrong in production, roll it back to the previous version.
- 1:59The project's folder is in a Git repository.
- 2:02A pipeline publishes each change to your Weik.io installation.
- 2:08The next publish from Git restores any document you changed by hand.