-
Configuration evolves, nothing stays the same
You can cut and paste old config; but you probably should investigate new features
One of the things that happen when you start using Interlok for any length of time is that you end up copying old configuration, templated or otherwise; it works, there aren’t any deprecation warnings, and it gets the job done. In some cases, what we might have done previously is different to how we’d approach the problem now. A case in point is the building up of complex metadata values. …
• by
Lewin Chan
-
Interlok 3.9.2
Interlok 3.9.2 has been released and is now available for download.
Interlok 3.9.2 has reached GA. It is now available for download. …
• by
Paul Higginson
-
The new PGP services
A collection of services that provide PGP encryption, decryption, signing, and verification.
Interlok PGP is a collection of services that provide an easy way to perform the major PGP functions: encryption, decryption, signing, and signature verification. It uses Bouncy Castle to do the heavy lifting. …
• by
Ashley Anderson
-
R.I.P. Dynamic Service Locator
Dynamic services have changed; plus ça change, plus c'est la même chose
In 3.8.4 we deprecated
dynamic-service-locator; this decision wasn’t taken lightly, but change and evolution is necessary so that you can get where you want to go. Originallydynamic-service-locatorcame about so that people could make changes to configuration independently of restarting. It was only really useful if your possible configurations didn’t require new components (e.g. you always dealt in XML, and never used JSON). In fact a lot of the time it was abused by people logging to the production system and modifying config directly which wasn’t nice. Even though it’s deprecated; changing the service chain that you execute based on various things at runtime is still possible within Interlok. …• by Lewin Chan
-
Testing Interlok interoperability with AWS
Mocking AWS interactions with localstack
One of the habits that most of our team have is to try and run everything on their local machine as much as possible to test behaviour and logic before doing any kind of deployment to something that isn’t directly within our control. It’s habit more than anything, coupled with the fact that we often do a lot of work while we’re not connected to the internet. Virtualisation, and container technologies like Docker are our best friends. …
• by Lewin Chan
-
Service testing my mappings
How can I be confident that my upgrade works?
Recently I was involved in a task to test any possibly impacts updating the version of Saxon could have on the Interlok’s xslt transformation service and it got me thinking that the service tester could also be very useful when updating any mappings from xslt 1.0 to 2.0 to make sure we still get the same output. …
• by
James Wickham
-
Interlok 3.9.1
Interlok 3.9.1 has been released and is now available for download.
Interlok 3.9.1 has reached GA. It is now available for download. …
• by Paul Higginson
-
How to manage multiple adapters
Once you're in production; what then?
Once you’ve developed your solution and deployed it then you’ll want to monitor it in production. Since all the runtime capabilities of Interlok are JMX based; our UI only uses publicly accessible JMX (there is no special sauce); you can leverage your existing JMX tools to manage Interlok. Of course the Interlok UI is perfectly capable of monitoring multiple Interlok instances which means you can use it as a monitoring tool in the absence of anything else. …
• by Lewin Chan
-
Battling with builds in Windows
Getting gradle builds in windows working.
More and more we are using build tools to assist in the creation of Interlok artefacts, until recently there were a few scenarios that didn’t work in windows this meant we had to use WSL to run our builds. …
• by
Matthew Warman
-
How to change the jetty work directory
The Interlok UI starts too slowly; I hate it!
Do you remember when you were at school; someone did something a little bit naughty and the teacher, rather than pinpointing the culprit, punishes the entire class/year/school. Corporate IT and antivirus programs are a bit like that sometimes. By default jetty will extract all web applications into a temporary folder (usually the system temporary folder). This can lead to long start times as your antivirus of course on-demand scans all the jar files, and sometimes (this is true of MS Defender on some of my test boxen) asks you to upload various jar files for analysis. …
• by Lewin Chan