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
Traditional WAS vs. WebSphere Liberty: IBM's Transition Strategy
IBM's WebSphere product line has two primary components. WebSphere Application Server (WAS) Network Deployment — the traditional Java EE application server that has been the backbone of enterprise middleware since the late 1990s — and WebSphere Liberty, the lightweight, modular application server built on the Open Liberty open-source project.
IBM's commercial strategy is clear: Liberty is the future; traditional WAS is maintenance mode. IBM has progressively reduced investment in WAS ND, moved end-of-support dates forward, and designed Liberty as a subscription product under the IBM WebSphere Hybrid Edition and IBM Cloud Pak for Applications umbrellas. The intent is to drive perpetual WAS licence holders toward annual subscription billing.
The numbers are significant. WAS ND licences — particularly at the high end of multi-processor environments running critical applications in banking, insurance, and telecommunications — represent annual support costs of £100,000–£2M+ for large deployments. IBM's Liberty subscription pricing at equivalent scale is typically 2–3× higher than the TPS alternative.
The Liberty "Migration Assist" Programme
IBM has a WebSphere Migration Toolkit and associated professional services offering. IBM positions this as help to migrate to Liberty. In practice, WAS-to-Liberty migration involves substantial application rearchitecting — particularly for applications using WAS-specific APIs (proprietary session management, JCA adapters, or WAS security features) that have no direct Liberty equivalent. TPS on existing WAS is the cost-effective alternative for organisations where migration ROI is unclear or negative.
TPS Coverage: What Is Included
WebSphere Application Server Network Deployment (WAS ND) TPS Coverage
- WAS ND core application server — Java EE 6/7/8 container, servlet/JSP engine, EJB container, JAX-RS/JAX-WS web services
- Deployment Manager and Node Agents — distributed WAS cell management, node synchronisation, and cluster topology support
- WAS security subsystem — LTPA/LTPA2 tokens, SSO configuration, JAAS authentication, and role-based access control
- JVM tuning and GC analysis — heap sizing, GC policy configuration, verbose GC analysis, and OutOfMemoryError diagnosis
- WebSphere MQ integration — WAS-MQ JMS provider configuration, message listener ports, and connection factory management
- Database connection pools (JDBC) — WAS datasource configuration, connection pool tuning, and connection leak diagnosis
- Security patches and Java fixpacks — IBM JDK security patches and WAS fixpacks backported to your installed version
- Custom application support — EAR/WAR deployment issues, classloader configuration, and application-specific WAS interaction bugs
- Performance analysis — thread dump analysis, heap dumps, FFDC log analysis, and PMI metrics interpretation
- High-availability cluster support — session replication, in-memory grid, and failover configuration
WebSphere Liberty Core / Base TPS Coverage
- Liberty server configuration — feature configuration (server.xml), dynamic feature loading, and configuration validation
- Liberty security — LDAP/SAML/OAuth feature configuration, SSL/TLS setup, and certificate management
- MicroProfile API support — JAX-RS, CDI, MicroProfile Config, MicroProfile Health, MicroProfile Metrics
- Liberty JVM and performance — OpenJ9/IBM J9 JVM tuning, memory analysis, and thread contention diagnosis
- Docker/container deployment issues — Liberty in containerised environments (Kubernetes/OpenShift), health probe configuration, and startup/readiness issues
- Security patches — Liberty fixpacks and Java security patches for your installed version
- Custom application issues — feature dependency conflicts, classloading, and Liberty-specific deployment problems
WAS and Liberty Version Matrix
| Product | Version | IBM EOS | TPS Available |
|---|---|---|---|
| WAS ND | 7.0 | April 2015 | ✓ Available |
| WAS ND | 8.0 | June 2016 | ✓ Available |
| WAS ND | 8.5 | April 2025 | ✓ Available |
| WAS ND | 9.0 | September 2025 (mainstream) / 2030 ext. | ✓ Available |
| WebSphere Liberty | 8.5.5 / Liberty Core | Apr 2025 | ✓ Available |
| WebSphere Liberty | 16.0.0.x – 22.0.0.x | Varies by version | ✓ Available |
| WebSphere Liberty | 23.0.0.x – 24.0.0.x | Active | ✓ Available |
| WAS Base | 8.5 / 9.0 | As above | ✓ Available |
How Much Could You Save on WebSphere Support?
Get a specific cost model for your WAS or Liberty environment — processor count, version, and current IBM support spend benchmarked against TPS pricing.
Request WebSphere Assessment Download IBM Licensing GuideTPS Cost Model: Four WAS/Liberty Profiles
| Profile | Environment | IBM Support / yr | TPS / yr | 3-Year Saving |
|---|---|---|---|---|
| Regional bank WAS ND 9.0, 4-node cluster, core banking apps |
WAS ND 9.0, 16 proc | £132,000/yr | £52,800/yr | £237,600 |
| NHS Trust WAS ND 8.5, 2-server cluster, EPR/clinical apps |
WAS ND 8.5, 8 proc | £66,000/yr | £26,400/yr | £118,800 |
| Telco billing WAS ND 9.0 + Liberty, 32 proc, CDR processing apps |
Mixed WAS + Liberty, 32 proc | £264,000/yr | £105,600/yr | £475,200 |
| Large insurer WAS ND 9.0, 8-node cluster, policy/claims processing |
WAS ND 9.0, 64 proc | £528,000/yr | £211,200/yr | £950,400 |
IBM Liberty Subscription vs. TPS: The Commercial Analysis
IBM's WebSphere Liberty pricing under Hybrid Edition and Cloud Pak for Applications is constructed around Virtual Processor Cores (VPCs) — a different metric from the processor-based WAS ND licencing most customers hold. The conversion from WAS ND processor licences to Liberty VPCs typically results in a 1.5–2× increase in the unit count, multiplied by the subscription rate.
For a WAS ND customer with 16 processors paying £132,000/year in IBM support, the equivalent Liberty subscription pricing is often £200,000–£280,000/year — before any application rearchitecting costs. TPS at £52,800/year (60% saving on current IBM support) represents a 73–81% saving against the Liberty subscription alternative.
Perpetual Licence Protection
IBM cannot revoke your WAS ND perpetual licence entitlements. If you hold a perpetual WAS ND licence and move to TPS, you continue to use the software under your licence terms. IBM does not have a mechanism to force migration to Liberty or to subscription billing. Your legal position is protected — TPS simply replaces the support contract.
Sector Perspectives
Financial Services: Core Banking and Trading Platforms
UK and European banks running WAS ND for SWIFT payment processing, FIX protocol trading gateways, or core banking front-end applications have deeply certified WAS deployments. The certification effort for any middleware platform change — including Liberty migration — requires months of regression testing against trading systems, payment rail integrations, and clearing/settlement platforms. TPS preserves the certified environment while dramatically reducing maintenance cost.
Healthcare: NHS EPR and Clinical Application Middleware
Many NHS Trusts and private hospitals run WAS ND as the application server layer for Cerner/Epic integration engines, HL7 messaging adapters, and clinical portal applications. Clinical application re-certification on a new runtime is a clinical governance obligation — migration is not a routine IT decision. TPS allows NHS organisations to maintain operational stability and reduce support cost simultaneously.
Public Sector: Legacy Government Application Portfolios
Central and local government organisations in the UK and Europe operate large WAS ND estates serving citizen-facing applications, tax administration systems, and benefits processing platforms. These environments are stable, mission-critical, and subject to change-management constraints that make migration programmes multi-year propositions. TPS is a recognised cost-reduction measure in public sector IT estate rationalisation programmes.
Frequently Asked Questions
Will IBM try to audit our WAS licences if we cancel IBM support?
IBM licence audits are not directly triggered by support contract changes. IBM's audit programme is driven by discovery of undisclosed deployments, not by contract terminations. Cancelling IBM support does not create audit risk. That said, before any TPS transition, a licence position review to confirm entitlements is standard practice.
Can TPS cover WAS ND in a virtualised environment (VMware)?
Yes. WAS ND in VMware or other virtualised environments is within TPS scope. Unlike Oracle's virtualisation policies, IBM's WAS ND licensing on VMware does not carry the same processor-counting complexity — the existing processor-based licence structure applies.
Does TPS cover IBM MQ (formerly WebSphere MQ) as well?
IBM MQ support is available under a separate TPS stream. Many organisations manage WAS ND and IBM MQ TPS together. See our IBM MQ TPS article for the full analysis.