IBM webMethods upgrade from 10.x
We upgrade IBM webMethods 10.x estates to 11.1 or 12.1, before standard support for 10.15 ends on 31 October 2027. We start with an inventory of packages, adapters, Trading Networks assets and Broker use. Then we plan the path, test it on a copy of your environment and cut over with you.
The task.
Standard support for IBM webMethods 10.15 ends on 31 October 2027. Your estate keeps running after that date. What changes is the support IBM gives you, and the risk you carry.
An upgrade touches more than the version number. Packages, adapters, Trading Networks partners and Broker clients each need a path. Your partners and core systems expect every interface to behave as before.
What we do.
- 01
Inventory
We list every package, adapter, Trading Networks asset and Broker client, with their dependencies. You see what moves as is, what changes and what goes.
- 02
Target and path
We choose 11.1 or 12.1 with you. The plan names each step, its test and its fallback.
- 03
Broker to Universal Messaging
Broker clients, document types and triggers move to Universal Messaging. Publish and subscribe are tested before the switch.
- 04
Containers
If you move to Kubernetes or Red Hat OpenShift, we build the images, the pipelines and the runbooks. Configuration moves out of the server and into version control.
- 05
Licence options
When your licence terms change with the upgrade, we set out the options. Self-managed 12.1 and IBM Integration SaaS change different things for your team.
- 06
Test and cutover
We test on a copy of your environment, with sample messages from your partners. Cutover happens on a date agreed with you, with a rollback plan.
Typical engagements.
Upgrade assessment
We map your versions, packages, interfaces and risks. You get a written assessment with options.
Full upgrade
We own the upgrade as a fixed scope: target, path, tests and cutover. Each increment ends with a tested release.
Upgrade with your team
Our engineers work inside your team on your platform. Your engineers carry out the upgrade with us and keep the knowledge.
Versions and dates.
From the vendors' published pages, checked on 17 October 2026.
Standard support for IBM webMethods 10.15 ends on 31 October 2027.
Initial extended support runs to 31 October 2028; from then to 31 October 2030, IBM helps with usage and known defects only.
None of these dates is a legal deadline: the software keeps running, and the risk of running it without standard support is yours.
The upgrade targets are 11.1 and 12.1, the current self-managed release; we checked the dates on 17 October 2026.
- Standard or open-source support ends
- Extended support
- Limited support
- Last checked 17 October 2026
- 31 October 2027 :
IBM webMethods 10.15 reaches end of support; initial extended support to 31 October 2028, then usage and known-defect help only, to 31 October 2030.
Is this for you?
A good fit
- You have IBM webMethods 10.x in production and must plan for 31 October 2027.
- Your internal team will take the estate over after cutover.
- You can give us a copy of your environment to test on.
Not a fit
- You want licences resold, with no upgrade work.
- You need people placed, with no technical lead on your side.
- You want the upgrade done without a test on a copy first.
Questions.
How do you upgrade IBM webMethods 10.x?
We upgrade IBM webMethods 10.x estates to 11.1 or 12.1. We start with an inventory of packages, adapters, Trading Networks assets and Broker use. Then we plan the path, test it on a copy of your environment and cut over with you. Standard support for 10.15 ends on 31 October 2027.
What happens after 31 October 2027?
After 31 October 2027, IBM webMethods 10.15 has no standard support, but it keeps running. Initial extended support runs to 31 October 2028. From then to 31 October 2030, IBM helps with usage and known defects only.
Should we move to 11.1 or 12.1?
The choice between 11.1 and 12.1 depends on your licence, your platform and your interfaces. 12.1 is the current self-managed release. The written assessment sets out both paths, with the risks of each.
What happens to our Broker in the upgrade?
In the upgrade, Broker use moves to Universal Messaging. We map each Broker client, document type and trigger, then test publish and subscribe on Universal Messaging before the switch.
Can we move to containers in the same project?
Yes, the move to Kubernetes or Red Hat OpenShift can be part of the upgrade or a step after it. We plan the order with you, so one change is tested at a time.
Which version are you on?
Tell us the platform, the version and what has to change. We reply with questions or a proposed next step.
Plan your upgrade