IBM WebSphere Application Server — WAS traditional, in IBM's current nomenclature — is one of the foundational Java EE application servers in enterprise middleware history. Deployed at banks, insurance companies, telecoms, utilities, and government agencies from the late 1990s onwards, WebSphere AS became the runtime environment on which an entire generation of enterprise Java applications was built. IBM's current strategy is to migrate this installed base to WebSphere Liberty — a lighter-weight, container-compatible runtime — and ultimately to IBM Cloud and Red Hat OpenShift. The problem for the installed base: application migration from WAS traditional to Liberty is not a re-deployment. It is a re-architecture.
For organisations running WAS Network Deployment (WAS ND) 8.5.x, 9.0.x, or WAS Base in production — particularly where the application portfolio includes EJB 2.x components, PME extensions, JCA adapters, or tightly-coupled MDB configurations — migration to Liberty requires significant application rework that may cost £200K–£2M+ per application cluster. Third-party support for IBM WebSphere Application Server traditional delivers 50–64% saving against IBM Software & Support fees, covering your existing WAS environment without requiring Liberty migration, without IBM's Passport Advantage ELA bundling, and without Subscription & Support renewal pressure that conflates middleware support with cloud migration urgency.
Running IBM software? Third-party support cuts IBM costs by 50–90%. Free cost analysis, no obligation.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
WAS 8.5.x (traditional): IBM end of support reached April 2024 — standard support ended, Extended Lifecycle Support (ELS) available at premium surcharge. WAS 9.0.x (traditional): IBM end of standard support December 2025. ELS extension available through December 2027 at approximately 20–30% surcharge on top of standard S&S. WAS Liberty: Active development — IBM's strategic runtime, separate product. Third-party support covers WAS traditional 8.5.x and 9.0.x at substantially lower total cost than IBM's Extended Lifecycle Support surcharge, without migration obligation. See our IBM WebSphere support guide for the full product lifecycle analysis.
IBM Liberty Migration — What IBM Does Not Model in Its TCO
IBM's WebSphere Liberty pitch is technically sound as a runtime architecture. Liberty's modular OSGi framework, microcontainer deployment model, and OpenShift compatibility make it a credible platform for new Java application development. What IBM's migration TCO calculators consistently omit is the application remediation cost for existing WAS traditional workloads that rely on specifications deprecated or removed between Java EE 7 (WAS ND 9.0) and Jakarta EE 9/10 (Liberty 22.x+).
The specific technical debt categories that drive WAS-to-Liberty migration cost: EJB 2.x entity beans (removed in Jakarta EE 9 — must be rewritten as JPA or CDI); proprietary IBM PME extensions (ManagedBeansModule, DataPowerIntegration, WorkManager — Liberty equivalents require configuration re-architecture); WAS security framework (LTPA, TAI, JAAS/JACC — Liberty security model uses OIDC/JWT natively, requiring federated identity reconfiguration); JCA resource adapter deployment (ra.xml binding differences between WAS and Liberty container); and clustering/DR model (WAS ND cell topology has no direct equivalent in Liberty — replaced by OpenShift pod replication, requiring infrastructure transformation alongside the application layer). Our IBM WebSphere end-of-support guide covers each of these migration cost categories in detail.
IBM WebSphere AS Version Matrix — TPS Eligibility
| WAS Version | IBM Support Status (2026) | TPS Available | Primary Deployment Cohort |
|---|---|---|---|
| WAS 7.0 (Java EE 5) | EOS Apr 2015 — no IBM support | ✓ Yes | Legacy banking/insurance (EJB 2.x, struts) |
| WAS 8.0 (Java EE 6) | EOS Jun 2017 — no IBM support | ✓ Yes | Mid-tier enterprise — pre-Liberty migration |
| WAS 8.5.x ND/Base | EOS Apr 2024 — ELS premium | ✓ Yes — high TPS demand | Banking, telecoms, NHS, utilities (2012–2018 deployment vintage) |
| WAS 8.5.5.x (fix packs) | EOS Apr 2024 — ELS premium | ✓ Yes — largest active TPS cohort | Same as WAS 8.5.x — fix pack update path |
| WAS 9.0.x ND/Base | EOS Dec 2025 → ELS to Dec 2027 | ✓ Yes | Newer deployments, Java EE 7 certified |
| WAS Liberty (any version) | IBM Active — strategic runtime | N/A — IBM strategic product | New deployments, OpenShift workloads |
What GoVendorFree TPS Covers for IBM WebSphere Application Server
GoVendorFree's IBM TPS covers the full WAS traditional stack — the application server runtime, cell and cluster topology, and integrated IBM middleware components. Coverage includes:
- WAS ND Cell and Cluster: Deployment Manager (dmgr), node agents, application server profiles, horizontal and vertical cluster topology, and session persistence (memory-to-memory and database-backed)
- WAS Application Deployment: EAR/WAR/RAR deployment, class loader management, shared library configuration, and application lifecycle management (start/stop, rollback, hot deployment)
- WAS Security Framework: LTPA/LTPA2 configuration, trust association interceptors (TAI), JAAS LoginModule configuration, JACC provider integration, SSL/TLS certificate management, and federated repository (LDAP/AD) integration
- WAS Messaging: IBM MQ integration via WAS JMS provider, WebSphere Messaging Engine (SIBus) — single and multi-bus topologies, and MDB lifecycle management (see also IBM MQ TPS guide)
- WAS Performance and Diagnostics: Heap dump and garbage collection analysis (IBM Java 6/7/8 GC), thread dump analysis, JDBC connection pool tuning, and WAS PMI/Tivoli Performance Viewer configuration
- WAS Database Connectivity: JDBC provider configuration (DB2, Oracle, SQL Server, Informix), XA transaction support, and connection pooling tuning for high-concurrency application servers
- WAS Integration: JAX-WS and JAX-RPC web service endpoint stability, WSRR (WebSphere Service Registry and Repository) integration troubleshooting, and DataPower Gateway integration for API management scenarios
- CVE and Security Advisory: Independent security advisory for WAS CVEs — providing compensating controls guidance for organisations that cannot patch on IBM's fix pack schedule, and WAS security hardening documentation for PCI DSS / DORA compliance
IBM Passport Advantage ELA — The Bundling Problem for WAS Customers
Many large WAS ND customers acquired their WebSphere licences as part of an IBM Passport Advantage Enterprise Licence Agreement (ELA) — bundled with other IBM software including DB2, IBM MQ, Tivoli products, and in some cases IBM Security components. The Passport Advantage ELA renewal process bundles all IBM software support costs into a single annual invoice, making it difficult to identify the WAS-specific support cost as a discrete line item and to make a targeted decision to exit WAS support while retaining IBM support on other products.
GoVendorFree specialises in IBM Passport Advantage ELA unbundling — identifying the WAS-specific S&S cost within the ELA, negotiating a partial exit from IBM support for WAS ND while retaining IBM S&S on products where continued IBM support is commercially justified, and implementing TPS for the WAS environment as a standalone cost-reduction exercise. This unbundling approach is covered in detail in our IBM Passport Advantage alternatives guide.