Home / Software AG / EntireX
① Product · Software AG
EntireX is the Software AG (now IBM) integration broker that wires COBOL and Natural to modern services. It often holds your Adabas and Natural estate together, which is exactly why the renewal needs a buyer who has measured the dependency first.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →EntireX is the integration broker that exposes mainframe programs as reusable services and APIs. It lets COBOL, Natural, PL/I, and Assembler logic be called from modern applications without rewriting the core, and it has long been the connective tissue between Software AG's Adabas and Natural estates and the world outside the frame. Ownership moved with the webMethods integration portfolio when IBM acquired that business from Software AG (now IBM) in 2024. The product mechanics described here held under Software AG and are the right baseline under IBM, but the contracting entity, support path, and price list are exactly the things that change with an acquisition, so they deserve a fresh read on your own paper.
On the mainframe, EntireX has commonly been licensed against z/OS capacity, an MSU or tier based charge that follows the machine rather than the number of services published. The broker and any distributed adapters can carry their own components, so a full EntireX footprint may span more than one line. The basis varies by contract vintage and by how the deal was originally bundled with Adabas and Natural, which is why a single assumed metric across the estate is usually wrong. Read the entitlement.
| Element | How EntireX is treated |
|---|---|
| Metric | z/OS capacity, MSU or tier based, on the mainframe component |
| Model | Perpetual plus maintenance or term, varies by vintage |
| Components | Broker plus adapters, sometimes separately licensed |
| Bundling | Frequently sold alongside Adabas and Natural |
| Cost driver | Licensed capacity and component count |
Directional summary. Confirm the contracting entity, metric, and components on your own EntireX order.
Three drivers set the EntireX number. Licensed capacity, because a capacity based charge tracks the machine and lifts with the estate even when the integration workload is flat. Dependency, because EntireX commonly carries live Natural and Adabas traffic, and the harder it is to switch off, the more pricing power the owner holds at renewal. And bundling, because the line is often invisible inside a larger Software AG (now IBM) agreement where it cannot be benchmarked against what the broker actually does. The combination of high switching cost and bundle opacity is the expensive part, not the raw metric.
The traps cluster around capacity and ownership transition. Capacity drift bills the broker against a machine that grew for unrelated reasons. Scope creep spreads the broker or its adapters onto LPARs the entitlement never covered, a common pattern as integration projects multiply. And the ownership transition itself is a trap of timing, because the moment a product changes hands is the moment terms get restated and bundles get reshaped, often on the new owner's standard paper rather than your negotiated one. Validating where EntireX actually runs and on what capacity is the defense, the discipline behind Software AG audit defense.
Start by reconciling licensed capacity against actual broker throughput and the LPARs EntireX genuinely runs on, because the entitlement frequently outruns the real footprint. Unbundle the line so it is benchmarked on its own rather than buried inside a larger integration or mainframe agreement, and cap uplift across the term. The decisive lever is exit math: EntireX dependence usually tracks Natural and Adabas dependence, so a costed view of reducing that reliance, whether through modernization or an alternative integration path, is what converts a captive renewal into a negotiated one. Build it before the contracting entity changes hands again. This is the core of our Software AG renewal work.
EntireX moved with the webMethods integration portfolio when IBM acquired that business from Software AG in 2024. Buyers still search both names, so the dual naming matters: it is the Software AG (now IBM) integration broker. The mechanics described here held under Software AG and are the right starting point under IBM, but confirm the current contracting entity, support path, and price list on your own paper, since post acquisition terms commonly shift.
EntireX is the integration broker connecting COBOL, Natural, PL/I, and Assembler programs to services and APIs. On the mainframe it has commonly been licensed against z/OS capacity, an MSU or tier based charge, sometimes with a separately licensed broker or adapter component on the distributed side. The exact basis varies by contract vintage, so the right move is to read the entitlement on your order rather than assume a single metric across the estate.
Two patterns recur. First, ownership transition is a moment vendors use to consolidate paper and reprice, so an EntireX line can be pulled toward an IBM agreement on IBM's terms. Second, EntireX is often load bearing for Natural and Adabas applications, which raises switching cost and weakens a buyer who has not built an alternative. Modeling the dependency and the exit cost before renewal is what restores leverage.
Reconcile licensed capacity against actual broker throughput and the LPARs it really runs on, cap uplift, and unbundle the line so it is benchmarked on its own rather than inside a larger integration or mainframe agreement. Where a modernization path reduces dependence on the broker, a costed exit study adds leverage. The strongest position is built before the contracting entity changes hands again.
Publisher hub: Software AG mainframe licensing. Related guide: Natural and Adabas modernization: license exit math. Related concept: MSU explained. Put it to work: Software AG audit defense.