What Is webMethods?

What is the webMethods platform?

webMethods is the connective layer of an enterprise IT estate. It is not a single application that replaces your systems; it is the software that makes your existing systems work together, so an order created in one system can reach the ERP automatically, a partner can exchange documents with you reliably, and a file can move between systems without anyone writing a one-off script. Rather than connecting every system directly to every other one, it routes that traffic through one governed layer you can monitor, secure and control.

What does webMethods cover?

webMethods covers four broad areas of integration: application integration, connecting core business systems so data flows between them automatically; API management, building, publishing and securing APIs for internal teams and external partners; B2B integration, exchanging business documents with trading partners using EDI and similar standards; and managed file transfer, moving files between systems securely and with a full audit trail. Most organisations adopt it not because they have no integrations, but because they have too many fragile ones, and they want a single platform to replace that sprawl.

The core components

A few parts do most of the work: the Integration Server, the runtime that executes the integrations; API Gateway, which publishes, secures and monitors APIs; Trading Networks, which manages partner relationships and document exchange; and ActiveTransfer, which handles managed file transfer. Most projects start with the Integration Server and add the others as needs grow.

Is webMethods cloud or on-premises?

Both. webMethods began as on-premises software and is now also delivered as an integration platform as a service, so it supports on-premises, cloud and hybrid deployments. Many enterprises run a hybrid model: core systems on their own infrastructure, newer applications in the cloud, and webMethods connecting the two. The right topology depends on where your data has to live, not on a default.

When webMethods is a good fit

webMethods is a good fit when:

•      you have many enterprise systems that must stay in sync,

•      you need B2B or EDI integration,

•      you need governance and auditability,

•      you operate across hybrid infrastructure.

It may be heavier than you need when:

•      you only require a few simple SaaS-to-SaaS automations,

•      you do not need enterprise governance,

•      your integration estate is small.

For more on where it fits, see Why webMethods?.

Who uses webMethods

webMethods is built for organisations with many systems that have to stay in sync, typically larger companies in manufacturing, banking, telecom, retail and logistics, where manual data syncing is not realistic. For example, a global nutrition, health and beauty manufacturer used webMethods to connect five factories on four continents to a single SAP core, which you can read about in our One SAP, Five Factories case study.

Is webMethods still supported now it is part of IBM?

Yes. IBM completed its acquisition of webMethods from Software AG on 1 July 2024, and support and training have since moved to IBM. Existing deployments keep running; this is continuity, not a forced migration. IGT Systems is an IBM partner, and was a Software AG partner before that, so the roadmap and support sit on a stable footing.

You can see how IGT applies webMethods on our webMethods integration page.

Considering webMethods for your enterprise stack? See how IGT Systems approaches webMethods integration.

See also: Why webMethods?  ·  What integrates with webMethods?

Sources

•      IBM: Completes Acquisition of StreamSets and webMethods (1 July 2024)