IBM webMethods

We design, build, upgrade and operate integrations on IBM webMethods: Integration Server, API Gateway, Universal Messaging, and B2B with Trading Networks. We work self-managed on Kubernetes and Red Hat OpenShift, and on IBM Integration SaaS. Each plan names your versions and the dates IBM publishes for them.

The task.

Your integration layer connects systems that other teams own. Partners, core systems and ServiceNow all depend on it. When it changes, every interface around it must keep working.

If your estate is on 10.15, standard support ends on 31 October 2027. The upgrade, a move to containers and a licence decision can arrive together. You need one plan that covers all three.

Camunda 8 Java 25 IBMwebMethods ServiceNow
Fig. 1. IBM webMethods Integration Server answers the Java worker and passes the call on to ServiceNow. The red dot is the process token, at the end event. A schematic, not a client system.

What we do.

  1. 01

    Integration Server

    Flow services, adapters and packages, designed, reviewed and tested. Package dependencies stay explicit, so each package deploys on its own.

  2. 02

    API Gateway

    Your APIs published through IBM webMethods API Gateway. Policies handle authentication, throttling and logging in one place.

  3. 03

    Universal Messaging

    Publish and subscribe on Universal Messaging, including the move from Broker. We map each Broker client, document type and trigger before anything moves.

  4. 04

    B2B and Trading Networks

    Partner profiles, document types and processing rules in Trading Networks. Each partner flow is tested with sample messages before cutover.

  5. 05

    Self-managed or IBM Integration SaaS

    Self-managed on Kubernetes or Red Hat OpenShift, or IBM Integration SaaS. We set out what each option changes for your team.

  6. 06

    Operations and handover

    Monitoring, deployment pipelines and runbooks. Your team takes the system over with documentation it can use.

Typical engagements.

  • Version upgrade

    From 10.x to 11.1 or 12.1. An inventory comes first, and the cutover is planned with you.

  • Platform review

    A written review of your versions, packages, adapters, interfaces and risks. You get the options and the risks of each.

  • Move to containers

    Integration Server and Universal Messaging moved to Kubernetes or Red Hat OpenShift, with pipelines and runbooks.

  • Embedded engineers

    Our engineers join your integration team. They work on your platform and to your release cycle.

Versions and dates.

From the vendors' published pages, checked on 17 October 2026.

IBM completed its acquisition of webMethods from Software AG on 1 July 2024.

The current self-managed release is IBM webMethods Integration 12.1.

Standard support for IBM webMethods 10.15 ends on 31 October 2027; initial extended support runs to 31 October 2028, and help on usage and known defects to 31 October 2030.

We checked these dates on 17 October 2026 and check them again every quarter.

  1. 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 are a bank, insurer or transport company in DACH with IBM webMethods in production.
  • You have an internal team that will take the system over.
  • You face a published date, such as 31 October 2027 for 10.15.

Not a fit

  • You want licences resold, with no engineering work.
  • You need people placed, with no technical lead on your side.
  • You want production changed before a copy of it has been tested.

Questions.

Which IBM webMethods products do you work on?

We work on Integration Server, API Gateway, Universal Messaging and Trading Networks. We deploy them self-managed on Kubernetes and Red Hat OpenShift, and work on IBM Integration SaaS.

Who owns IBM webMethods now?

IBM owns webMethods: it completed the acquisition from Software AG on 1 July 2024. The current self-managed release is IBM webMethods Integration 12.1, and the iPaaS is IBM Integration SaaS.

Does our 10.15 estate stop working in October 2027?

Your 10.15 estate keeps running after 31 October 2027: that date ends IBM’s standard support, not the software. Initial extended support runs to 31 October 2028, and help on usage and known defects to 31 October 2030. The risk of running it without standard support is yours.

Can IBM webMethods run on Red Hat OpenShift?

Yes, IBM webMethods runs self-managed on Kubernetes, and we deploy it to Red Hat OpenShift as well. We build the images, the pipelines and the runbooks with your team.

Can we work with you in German?

Yes, workshops and documentation can be in English or German.

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.

Talk to an architect