Which area does what
Concept 3 · 3:39
Follow one company's supplier invoices through the areas of Weik.io. A transfer moves the PDFs every morning. When the transfer's run summary arrives, the integration that posts each invoice to the ERP starts.
This part of the video couldn't be loaded.
What it covers
- A managed file transfer that moves the PDFs, and its run summary
- An integration in Camel files that posts each invoice to the ERP
- An event that the integration publishes into a channel after each invoice
- The entity store that records which invoices an integration has handled
- The gateway in front of the invoice API and its rate limit for each partner
- Logs, metrics and traces that show why an integration fails
Commands in this video
This video explains with drawings and has no commands.
Transcript
- 0:01This video shows what the areas of Weik.io do with one company's supplier invoices.
- 0:11Supplier invoices arrive on the supplier's FTP server every morning,
- 0:16then have to end up in the ERP.
- 0:18Partners look them up during the day. The bank reports each payment.
- 0:27A transfer in managed file transfer moves the PDFs from the
- 0:31FTP server to the storage bucket at five every morning.
- 0:36Each run leaves a run summary with counts of files and errors.
- 0:43An integration posts each invoice to the ERP over HTTP,
- 0:48changing the data on the way.
- 0:51You write that work as Camel files, in Camel integrations.
- 0:55The integration starts when the transfer's run summary arrives.
- 1:05A schedule runs a command on an agent at set times.
- 1:08Each run leaves a run record with its exit value and whether it failed.
- 1:18The integration that posts invoices publishes an
- 1:21event into a channel in events after each invoice.
- 1:25Another integration reads that channel and reacts to every new invoice.
- 1:37With change tracking, each insert,
- 1:39update or delete in the ERP's invoice table becomes an event in a channel.
- 1:49The entity store records which invoices the integration has handled.
- 1:54So when the next morning's batch arrives, only the new invoice goes on to the ERP.
- 2:03Partners call the invoice API through the gateway, in API management.
- 2:09Each partner gets an API key with a rate limit: 60 calls a minute.
- 2:14Devtest and production answer on their own hostnames, and each has its own keys.
- 2:24The bank reports each payment through a webhook,
- 2:27which stores the message in a channel.
- 2:29An integration reading that channel reacts to the payment.
- 2:38Weik.io raises a problem in Observability when an integration's messages fail.
- 2:43Every Camel process sends logs, metrics and traces to Weik.io,
- 2:49so you can see why the integration fails.
- 2:56Managed file transfer moves the morning's PDFs and leaves a run summary,
- 3:01and Camel integrations post each invoice to the ERP,
- 3:04with a schedule running a command on an agent.
- 3:08In events, a channel carries an event per invoice,
- 3:12change tracking publishes ERP changes, and the entity store records posted invoices.
- 3:18API management gives each partner a key and a rate limit at the gateway,
- 3:24a webhook accepts the bank's call,
- 3:26and observability shows problems, logs, metrics and traces.
Next in this track
Concept 4 · 2:27 What to know before you start Watched