Do you support WAS 7, 8.5, 9 and Liberty Profile?
Yes. WAS 9.0.5+ (current, latest deployments) — T-Mobile, PZU. WAS 8.5.5 ND (LTS, ~80% of clients in production) — banking, insurance. WAS 7.0 / 6.1 (legacy, mainly migrations to newer versions) — older administrative systems. Liberty Profile 22.x+ (modular alternative) — cloud-native apps and microservices. Plus IBM HTTP Server, MQ, Integration Bus, Portal Server, DataPower.
Do you migrate from WAS Classic to Liberty Profile?
Yes, a common service in 2026. Process: (1) run binaryAppScanner to detect features required by the application, (2) refactor server.xml with appropriate feature managers (e.g. jpa-2.2, servlet-4.0, ejbLite-3.2), (3) migrate JNDI bindings, JDBC, JMS resources, (4) regression tests + performance comparison Classic vs Liberty. Typically 2–4 weeks for a standard JEE application. Benefit: 50–70% less RAM, ~5x faster startup, easier K8s deployment.
Do you offer SLA for production WAS clusters?
Yes. Premium 7/24 plan: SLA 15 min response, 4 h P1 resolution, 24/7/365 on-call, contractual penalties agreed in the contract. Care 5/8 plan: SLA 4 h response during business hours (Mon-Fri 9-17), 1 day P1 resolution. Enterprise: individual SLA with named engineer, KNF/ISO/GDPR audits. Average ND cluster uptime for our clients: 99.97% (rolling 12 months).
What does WAS cluster performance tuning look like?
Four layers: (1) JVM — OpenJ9 (or Oracle JDK), -Xms/-Xmx, GC algorithm (gencon for most, balanced for large heap, metronome for low-latency), Verbose GC analysis. (2) WAS — thread pools (Web Container, ORB, Default), JDBC connection pools (initial/max/test on reserve), EJB pool sizes, session timeout, plugin-cfg.xml retry/maxConnections. (3) Application — query optimisation, prepared statement cache, lazy loading EJB. (4) OS/net — AIX vmo/no/ioo, Linux sysctl, NFS sync. Every change measured before/after (PMI + thread dumps + heap dumps with IBM HeapAnalyzer).
Do you integrate WAS with IBM MQ and Integration Bus?
Yes. IBM MQ: queue managers, channels (SVRCONN, sender/receiver), JMS bus federation, Q/T configuration in WAS, foreign destinations. WebSphere Message Broker / Integration Bus (IIB): message flows, ESQL, MQ Input/Output nodes, WAS integration via SIBus or direct JMS. DataPower Gateway: XSL transform configuration, security policies, throttling. Experience: T-Mobile (MQ + IIB), PZU (MQ + WAS bus).
What about security: LTPA, SAML, LDAP?
LTPA tokens: cross-cell SSO, custom expiration, token propagation between WAS nodes. Federated Repositories: Active Directory + LDAP fallback, custom user attribute mapping. SAML SSO: IdP integration (ADFS, Okta, Auth0), trust association interceptor. OAuth 2.0 / OpenID Connect: configuration as Resource Server or Provider. SSL/TLS: cell + node keystores, certificate rotation, FIPS 140-2 mode for regulated environments. IBM Fix Packs: security patch application quarterly (or out-of-band for critical CVEs).
Do you train in-house teams?
Yes, two formats:
(1) Open — scheduled training (WAS 9, 8, 7) at
/en/training/, groups up to 10, at our Warsaw venue or online.
(2) Dedicated on-site — we come to the client, agenda tailored to real ND clusters, using your cell (with proper isolation). Trainer: Krzysztof Sarna (CEO, IBM Certified System Administrator for WAS ND V6 and V8.5.5 + Liberty Profile). Vouchers, VAT invoice, FlexNet completion certificate.
How do we get started?
Most common path:
(1) fill in the contact form or email
[email protected];
(2) within 24 h an engineer (not HR) replies with 3–4 technical questions (WAS version, cell topology, main issues);
(3) 30-min call with CEO/engineer;
(4) proposal with scope, timeline and price in 48–72 h. NDA signed as standard. For urgent P0 (WAS cluster down) — response within 1 h.