Integration Platform Support
We look after the integration platform you already run. We build the new interfaces your business needs, and keep the platform itself patched, upgraded and supported, especially when the people who knew it have moved on and replacements are hard to find.
Integration platforms outlive their teams
An integration platform often runs for ten years or more, and everything depends on it: orders, invoices, stock, customer data. The administrators and developers who set it up move on, and specialists for that particular platform are scarce. Upgrades get postponed, versions drop out of vendor support, patches pile up, and every new interface becomes a risk to the ones that already work.
Where our experience is
iWay Service Manager
TIBCO, formerly Information BuildersChannels, process flows and adapters; configuration, upgrades and the interfaces built on it.
webMethods
Integration Server and related componentsPackages and flow services, adapters and triggers, fix management and version upgrades.
Azure Integration Services
Microsoft AzureLogic Apps, Service Bus, API Management, Event Grid and Functions, including deployment and monitoring.
Apache Camel
Open sourceRoutes and components on Spring Boot, Quarkus or Karaf; Camel and Java version upgrades.
Adeptia
Adeptia ConnectPartner and data integrations, mappings and connections, and platform upgrades.
Another platform?
Updates, upgrades and new interfaces are much the same work on any integration platform. Ask us about yours.
Three parts, one platform
New connections and changes to existing ones, built with your integration team or on its behalf.
- Analysis with the system owners on both sides: data, volumes, timing, errors
- Mappings, connectors and APIs built to your platform's own conventions
- Error handling and monitoring designed in, not added after the first incident
- Tested, documented and handed over to whoever runs it next
Keeping the platform on supported versions: updates and upgrades planned, tested and carried out.
- A lifecycle calendar: vendor support dates, planned patches and upgrades
- Every change tested against the interfaces that already run
- Upgrades rehearsed on a test environment, with a rollback plan
The day-to-day running of the platform, at the support hours and response times we agree with you.
- Monitoring, failed messages and incidents, with the cause found and fixed
- Users and access, certificates, backups, performance and capacity
- Changes made through your own change process
Updates and upgrades without the risk
Postponed upgrades are how a platform ends up unsupported. We make them routine: small, tested and planned, so each one is a normal piece of maintenance rather than a project.
Upgrade assessment
Which versions you run, how long the vendor still supports them, what an upgrade changes, and which interfaces it touches.
Regression tests
Tests for the interfaces you already have, run before and after every patch or upgrade, so a change is accepted on evidence.
Patches and updates
Security patches, connector updates, certificates and the runtime underneath, on a schedule instead of when something breaks.
Major upgrades
Planned and rehearsed on a test environment, with a cutover plan, a rollback plan and a quiet moment agreed with the business.
Migrations
When a platform reaches the end of its life: moving the interfaces to its successor or to a new platform, one flow at a time.
Documentation
Runbooks, interface descriptions and upgrade notes, kept up to date as part of the work, not written afterwards.
Alongside your team, or in place of a vacancy
Extend your team
Our specialists work in your team's backlog, tools and change process: extra capacity for a busy period, a major upgrade or a set of new interfaces.
Cover the role
When you can't fill an administrator or developer position, we take on the administration and lifecycle of the platform for as long as you need, and hand it over when you've hired.
Either way, what we learn about your platform is written down in your own documentation. You stay in control of it, and you are never dependent on us either.
In three steps
An inventory of the interfaces, versions, vendor support dates, documentation and the risks that need attention first.
Urgent patches, monitoring that tells you about problems before your users do, and runbooks for the most common incidents.
An agreed monthly capacity for new interfaces and changes, the lifecycle calendar, and administration and support.