Interlok

Adaptris


Integration anytime any place anywhere.


  1. Using the health-check management component

    Wrangling the output from health-check using jq

    3.10.0 introduced a new health-check management component which can be used to either report the overall status of all known adapters in that JVM or to report on a specific workflow/channel; reporting on a specific workflow/channel means that you must know what the unique IDs will be. What it doesn’t do is to filter by status so you can’t get a list of all the channels that aren’t started. However, you can still get the output you need if wrangle the JSON output using JQ. …


  2. Mass update of dependabot PRs

    What to do when a new log4j is released and everything has a new PR...

    All our open source projects love dependabot since this gives us a really easy way of keeping on top of version updates. What can be a little bit frustrating is when there’s a whole bunch of pull requests because something that’s relied on by many projects is updated. The usual culprit for us would be log4j / slf4j which causes a cascade of PR generation by dependabot. …


  3. Shared service lists in service tester

    How to use shared-components in service tester

    Testing shared services is possible in service tester and how to select them is covered in a previous post. But there may be case when the service that is being tested, contains a call to a shared service. …


  4. Portable Service Tester Configuration

    Making service tester configuration environment agnostic.

    Sometimes it isn’t obvious the changes that need to be made to service tester configuration so thats its portable across machines and build pipelines. …


  5. Interlok + AWS KMS

    Fun and games with AWS KMS interoperability

    As of 3.10.1 (the next release due Q2 2020); there is support for AWS KMS within Interlok for their key operations, namely encryption; decryption; signing; and signature verification. The AWS SDK is very easy to use, so producing the code itself didn’t take long; it took longer to write the unit tests as usual. When writing a new optional component, we normally make the decision that we expose the configuration to the user, so the user can decide how they want to interact with the system. …


  6. Interlok 3.10.0

    Interlok 3.10.0 has been released and is now available for download.

    Interlok 3.10.0 has reached GA. It is now available for download. …


  7. Multi-Payload Messages

    An introduction to multi-payload messages

    The Multi-Payload Adaptris Message is a new message type that supports having multiple payloads in a single message. Each payload can be accessed by its user-defined ID. …


  8. Interlok 3.9.3

    Interlok 3.9.3 has been released and is now available for download.

    Interlok 3.9.3 has reached GA. It is now available for download. …


  9. When to write custom code revisited

    Interlok is a bit like pick'n'mix; I prefer fizzy cola bottles, maybe you like flying saucers

    We pride ourselves on not having too much of an opinion about whether or not you should write code, or use configuration to achieve your integration. If you have, by instinct, a developer mindset then you’ll naturally gravitate towards writing code because that’s what you’re most familiar with. This is something that we get quite a lot from new customers where their technical team are primarily developers. I can do this in language X; but I can’t in Interlok; why should we bother using it. That’s one way of looking at it; we prefer to look at it in terms of what does Interlok give us that means we can spend more time on providing business value. …


  10. Abusing Interlok as a programming language

    Interlok configuration probably isn't Turing complete; but we can write code in XML...

    We’re busy migrating away from Bitbucket; not because there’s anything wrong with it; but because as an organisation that’s grown out of 6+ companies, you have to rationalise and standardise things like source control; we’re using GitHub, Bitbucket, multiple on-premise Gitlab instances, Azure TFS; you get the picture. Apparently we need a spreadsheet (it’s always a spreadsheet) of all the projects that are currently in Bitbucket and when they were last used. That’s right; it’s Interlok Hammer time. …