IBM platforms we actually know.

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 help teams stabilise what's there, untangle EAR-and-shared-library sprawl, and plan honest paths off traditional WAS — to WebSphere Liberty, Open Liberty, or containerised JVMs — without pretending it's a weekend job.

• ▸Traditional WAS administration, profiling, and tuning
• ▸Liberty / Open Liberty migrations and containerisation
• ▸Heap, GC, and classloader troubleshooting on real workloads
• ▸WAS ↔ MQ, JMS, and Db2 integration patterns

AS/400, iSeries, System i, IBM i — same machine, four decades of name changes, and still the system of record for a surprising amount of the world's banking, insurance, distribution, and manufacturing. RPG III, RPG IV, RPG Free, CL, COBOL, Db2 for i, journaling, subsystems, work management, the lot.

We modernise without insulting the platform: expose Db2 for i via REST, refactor OPM RPG to ILE, replace 5250 screens where it pays back, and bring open source (Node.js, Python, Git on PASE) into the workflow alongside the green screens that still earn their keep.

• ▸RPG III → RPG IV → Free-Form modernisation
• ▸Db2 for i exposure via REST, SOAP, and Db2 Web Query
• ▸5250 modernisation, screen-scrape decommissioning, web front-ends
• ▸Open source on IBM i: Node.js, Python, Git, and PASE tooling
• ▸Work management, journaling, and HA/DR (PowerHA, Mimix) reviews

Rational tools are still the requirements and ALM backbone in defence, aerospace, automotive, and regulated engineering. DOORS and DOORS Next for requirements, Rational Team Concert (Jazz) for work and SCM, ClearCase and ClearQuest where they're still hanging on, Rational Software Architect for modelling.

We help teams that have to stay on Rational get more out of it, and teams that want to leave plan the exit — DOORS to DOORS Next or Polarion, RTC to Git plus Jira or Azure DevOps, ClearCase to Git — without losing the audit trail that put them on Rational in the first place.

• ▸DOORS / DOORS Next requirements engineering and migration
• ▸Rational Team Concert (Jazz) administration and Git/Jira migrations
• ▸ClearCase and ClearQuest assessments and exit plans
• ▸Rational Software Architect / UML asset rescue
• ▸Audit-trail preservation through ALM migrations

DataPower Gateway — physical appliances, virtual editions, and the container form factor — is still terminating TLS, enforcing WS-Security, and brokering SOAP / REST / MQ traffic in plenty of enterprises. It's powerful and unforgiving in equal measure, and the people who actually know XSLT, GatewayScript, and the DataPower object model are getting rarer.

We build, operate, and modernise DataPower estates: Multi-Protocol Gateways and Web Service Proxies, policy authoring, certificate and crypto-object hygiene, and clean migration paths into API Connect or modern API gateways when the appliance no longer fits.

• ▸Multi-Protocol Gateway and Web Service Proxy design
• ▸XSLT, GatewayScript, and policy authoring
• ▸WS-Security, mTLS, OAuth, and JWT enforcement
• ▸Containerised DataPower in Kubernetes and OpenShift
• ▸Migration paths to API Connect or vendor-neutral gateways