IBM WebSphere services.
Traditional WAS, Liberty, Open Liberty, IBM HTTP Server. We keep estates healthy, untangle the parts that have grown organically over a decade, and plan honest migrations off traditional WAS to Liberty or containerised JVMs — without pretending it's a weekend job.
- ▸ WAS Network Deployment (8.5, 9.0)
- ▸ WebSphere Liberty
- ▸ Open Liberty
- ▸ IBM HTTP Server (IHS)
WebSphere never really left.
WebSphere Application Server didn't stop running the business when the industry got bored of it. Traditional WAS, Liberty, and IBM HTTP Server still front a lot of regulated workloads — and they need engineers who actually know JNDI, classloader hierarchies, JCA adapters, and the WebSphere Console well enough to be useful at 3am.
We work with WebSphere as it actually exists in 2026: a decade or two of EAR sprawl, shared libraries that nobody wants to touch, server.xml files that have accreted features in feature packs nobody documented, and Liberty migrations that started with energy and ran out somewhere in the middle. The work is to stabilise, simplify, and chart a path forward that the existing team can actually own.
Capabilities
Traditional WAS administration
- ▸Network Deployment cells, nodes, clusters, and Deployment Manager
- ▸EAR and shared-library lifecycle, classloader policies, isolation
- ▸JNDI, datasource pooling, JCA adapters, and connection sizing
- ▸WebSphere Console and wsadmin (Jython) automation
Liberty / Open Liberty
- ▸WebSphere Liberty and Open Liberty migrations from traditional WAS
- ▸server.xml configuration, feature management, and dropins discipline
- ▸Reactive features, MicroProfile, and Jakarta EE 10 / 11 readiness
- ▸Liberty in Docker, Kubernetes, and OpenShift
JVM and runtime performance
- ▸Heap, GC, and metaspace analysis (IBM J9, OpenJ9, HotSpot)
- ▸Thread dumps, javacore, and GC log forensics
- ▸Classloader leak hunting and graceful recovery
- ▸Capacity reviews ahead of seasonal load
Integration
- ▸WebSphere MQ / IBM MQ connectivity (binding and client modes)
- ▸JMS, Activation Specs, and message-driven beans
- ▸Db2, Oracle, and Db2 for i datasource integration
- ▸IBM HTTP Server (IHS), WebSEAL, and plug-in configuration
Migration paths
- ▸Traditional WAS → WebSphere Liberty (with realistic timelines)
- ▸WebSphere Liberty → Open Liberty (drop-in compatibility)
- ▸Liberty → containerised JVMs on OpenShift or Kubernetes
- ▸Selective lift to Quarkus or Spring Boot where it pays back
Familiar situations.
- ▸Traditional WAS is out of support soon and IBM is quoting an Enterprise License renewal you'd rather not sign.
- ▸Liberty migration started two years ago and stalled at "works in test, fails in prod". Heap behaviour is different and nobody can quite say why.
- ▸Production heap keeps drifting up over the day and you're recycling cells weekly to keep things alive.
- ▸WebSphere connections to MQ are flapping under load and the team can't tell whether it's MQ tuning, Activation Spec config, or a JCA adapter issue.
- ▸You want to put Liberty in OpenShift but need a realistic picture of what changes — image strategy, config management, observability, certs.
Got a WebSphere estate worth talking about?
Whether you want to keep it running, get more out of it, or plan an honest exit — we've done all three.
Get in touch →