IBM WebSphere Application Server

WebSphere Application Server
Company type	Software
Industry	Middleware, Web application server
Founded	1998
Founder	Donald F. Ferguson
Products	WebSphere Application Server, WebSphere Liberty Profile
Parent	IBM

WebSphere Application Server (WAS) is a middleware software solution that operates as a web application server, providing a software framework and environment for hosting Java-based web applications. It stands as IBM's premier offering within the WebSphere product line. Originally developed by Donald F. Ferguson, who later became CTO of Software at Dell, the initial release appeared in 1998, evolving from the IBM HTTP Server team and the Domino Go web server.

Architecture

The foundation of WAS relies on open standard technologies such as Java EE, XML, and Web Services. It is compatible with various operating systems, including Windows, AIX, Linux, Solaris, IBM i, and z/OS. From Versions 6.1 through 9.0, the implementation of open standard specifications remains uniform across platforms, while platform-specific enhancements are applied beneath this standardized layer.

WAS integrates seamlessly with multiple Web servers, including Apache HTTP Server, Netscape Enterprise Server, Microsoft's Internet Information Services (IIS), as well as IBM HTTP Servers across i5/OS, z/OS, AIX, Linux, Windows, and Solaris environments. The default communication ports typically include 9060 for administrative tasks and 9080 for web content delivery.

The conventional WAS setup functions as a distributed architecture deployed over several operating system instances that collectively form a WebSphere cell. A centralized management component—the Deployment Manager—oversees application deployments and facilitates rolling updates across all nodes. Configuration data for the cell—covering node quantity, application deployment status, session handling, and resource configurations—is stored in XML files that are propagated to each node. Initially managed in files, configuration storage transitioned to databases around version 3.5 before reverting back to file-based storage by version 5.

Due to its distributed design, WAS security mechanisms could potentially override local security settings if improperly configured. Earlier management consoles permitted specifying remote log file locations, which risked unauthorized file access; thus, it was advised against running server processes with root-level privileges. Starting with version 6, default security configurations adopted a more secure baseline requiring explicit changes to enable certain features. Originally, all nodes operated within a single security domain for both management and security purposes; beginning with version 6.1, support for multiple security domains was introduced to separate administrative controls from application-level security.

Several IBM solutions, such as IBM InfoSphere DataStage, utilize WebSphere Application Server as their foundational infrastructure platform.

Version history

Extracted from IBM Knowledge Center: Programming model APIs and specifications alongside WebSphere product lifecycle timelines
WebSphere version	WebSphere Liberty (Continuous Delivery)	9.0	8.5.5	8.5 Liberty Profile	8.5	8.0	7.0	6.1	6.0	5.1	5.0	4.0	3.5
Latest Fix Pack	22.0.0.7	9.0.5.21	8.5.5.24	8.5.5.9 (next: 16.0.0.2)	8.5.0.2	8.0.0.15	7.0.0.45	6.1.0.47	6.0.2.43	5.1.1.19	5.0.2	4.0.7	3.5.7
Release date	5 July 2022	September 10, 2024	July 31, 2023	June 15, 2012	June 15, 2012	June 17, 2011	October 17, 2008	June 30, 2006	December 31, 2004	January 16, 2004	January 3, 2003	August 15, 2001	August 31, 2000
End of support				June 24, 2016 (with release of 16.0.0.2)		April 30, 2018	April 30, 2018	September 30, 2013	September 30, 2010	September 30, 2008	September 30, 2006	April 30, 2005	November 30, 2003
Java SE support	6 (until 17.0.0.2), 7, 7.1, 8 and 11 (since 19.0.0.1)	8	6 (until 8.5.5.13), 7, 7.1 (since 8.5.5.2) and 8 (since 8.5.5.9)	6,7,7.1 (since 8.5) and 8 (since fix pack)	6	6	5	1.4	1.4	1.3	1.3	1.2

IBM has issued numerous versions of WebSphere Application Server aimed at enterprise customers to accommodate evolving Java SE and Java EE standards aligned with contemporary application requirements.

Initially known as Servlet Express during its beta phase, WebSphere's versioning scheme includes major releases denoted by x.x and x.x.x formats—for example, versions such as v6.1 and v5.1 represent significant milestones comparable to releases like v8.5 and v3.5—highlighting IBM’s strategic emphasis on scalable and adaptable middleware solutions for enterprise environments.

WebSphere Liberty Versions

WebSphere Liberty was first introduced as the WebSphere Liberty Profile within WebSphere Application Server (WAS) version 8.5, following the same versioning scheme as WAS. In 2016, IBM transitioned to a continuous delivery approach, adopting a new fix pack numbering system that reset Liberty versions starting at 16.0.0.2, reflecting the year and quarter of release. This strategy facilitates more rapid deployment of enhancements and new functionalities. A shared Liberty version is included across both WAS 8.5 and 9.0 distributions.

Version 9.0

With the release of WebSphere Application Server version 9.0, support for Java EE 7 and Java SE 8 was introduced, aligning the traditional WAS platform with Liberty’s Java EE capabilities established since 2015. This marked the first WAS version available for both on-premises deployment and as WebSphere as a Service on IBM Cloud.

Liberty continues to be the preferred runtime for cloud-native applications, with Liberty version 16.0.0.2 bundled in WAS 9.0.0.0. The subsequent Liberty 16.0.0.3 update added compatibility with the MicroProfile programming model, enhancing development for cloud-native Java EE applications. Deployment flexibility includes options such as Docker containers and Cloud Foundry buildpacks. In September 2017, IBM open-sourced Liberty development under the Open Liberty initiative, which constitutes the runtime foundation for WebSphere Application Server. The OpenLiberty.io community manages Open Liberty distributions, while IBM provides commercial support through WAS.

Version 8.5.5

WebSphere Application Server version 8.5.5 expanded the Liberty profile by integrating support for Java SE 8 and complete Java EE 7 compliance starting with fix pack 8.5.5.6, along with incorporating WebSphere’s intelligent management features. Java EE support within Liberty is activated through configurable feature sets that differ by edition: the WAS Liberty Core edition offers Java EE Web Profile capabilities, whereas other editions include full Java EE 7 features. The Network Deployment edition enhances Liberty with intelligent management functionalities, and the z/OS edition provides additional platform-specific Liberty enhancements.

Version 8.5.0

WebSphere Application Server version 8.5 continued to support Java EE 6 and Java SE 6 by default, with optional compatibility for Java SE 7. Notable introductions in this release include the Liberty profile and intelligent management features.

The Liberty profile, available across all commercial editions, delivers a lightweight server environment tailored for web, mobile, and OSGi applications. It is characterized by a minimal installation footprint under 50 MB, approximately three-second startup times, and an XML-based configuration system that allows dynamic feature management via OSGi services to enhance developer efficiency. Applications can be deployed as a packaged server, which bundles the server runtime, configuration, and application into a single deployable unit for simplified distribution. Centralized managed installations are supported through the Job Manager component within the Network Deployment edition.

The intelligent management capabilities are integrated into both Network Deployment and z/OS editions, combining operational tools originally found in WebSphere Virtual Enterprise (WVE), such as application editioning, server health monitoring, dynamic clustering, and intelligent request routing.

Additionally, Compute Grid functionality is included in these editions; this feature was previously offered separately as WebSphere XD Compute Grid for orchestrating and managing Java batch processing workloads.

Version 7.0

Launched on September 9, 2008, Version 7.0 complies with Java EE 5 standards as an application server.

Highlighted enhancements include:

Advanced Management capabilities designed for overseeing extensive, geographically dispersed WebSphere Application Server and Network Deployment environments
Business-Level Application oversight that operates independently from packaging or programming frameworks
Property-Based Configuration to streamline automated administration using property files

Between the releases of WebSphere Application Server V7 and V8 (2011), IBM introduced multiple feature packs to provide new functionalities ahead of the subsequent major version. These fully supported feature packs, treated like core releases, featured:

Modern Batch processing
OSGi Applications alongside JPA 2.0 support
Service Component Architecture (SCA)
Web 2.0 and Mobile enhancements
XML improvements
Communication Enabled Applications

Version 6.1

Released on June 30, 2006, Version 6.1 adheres to Java EE 1.4 compliance. IBM extended its support lifecycle until September 30, 2013, offering incentives for migration.

Key capabilities included:

Compatibility with Java SE 1.5 and JSR 168 Portlets
Session Initiation Protocol (SIP) Servlet support
Upgraded WebSphere Install Factory and IBM Support Assistant tools
Simplified management through enhanced certificate/key handling and security improvements
Administration of IBM HTTP Server via the WebSphere Administrative Console
Support for early WS-Security 1.0 (pre-OASIS), Web Services Resource Framework, and WS-BusinessActivity standards
JSR160 JMX remote connections limited to IBM agents
Enhanced scripting with Jython command assistance in the Administrative Console, marking the beginning of Jacl syntax deprecation
Availability of 64-bit servants and Apache-based IBM HTTP Server support on z/OS

Support for EJB 3.0 and web services standards arrived through EJB and webservices feature packs, later incorporated into Version 7. These provided:

Partial asynchronous programming model support
Multiple payload structure handling
Streaming API for XML (StAX)
Limited WS-ReliableMessaging (WS-RM)
OASIS WS-Security 1.0 compliance
Restricted WS-Addressing support
JAXB integration
Limited policy set implementation
Secured thin client capabilities (limited)
SOAP MTOM optimization techniques
CGI and CORBA compatibility

Version 6.0

Released December 31, 2004, this Java EE 1.4 compliant application server introduced significant security upgrades, including support for JACC 1.0 and early WS-Security 1.0 (pre-OASIS) standards.

- Compatibility with Java Standard Edition 1.4
- Several programming model features from WebSphere Application Server V5.0 Enterprise Edition were incorporated into Express and Base editions, such as application profiles, startup beans, schedulers, and asynchronous beans
- The JMS engine was completely rewritten in Java and renamed "WebSphere Platform Messaging," offering enhanced functionality; WebSphere MQ remained supported as a JMS provider with interoperability
- Clustering architecture was revamped utilizing a high availability manager to oversee all singleton services and enable hot recovery processes
- Transaction logs could now reside on shared file systems, permitting cluster members to perform hot recovery of in-doubt XA transactions without relying on external high availability software
- The Deployment Manager’s responsibilities were confined to centralized JMX administration and configuration tasks; it no longer controlled clustering runtime functions
- Mixed version cells (ranging from V5 to V6) were supported in production settings

- WebSphere Application Server for z/OS**
- Provides core Network Deployment features enriched by platform-specific benefits:
  - z/OS Workload Manager facilitates prioritization of mixed workload processing
  - Resource Recovery Services improve transactional integrity during complex operations
  - Integration with mainframe security systems such as RACF
  - Enhanced vertical scalability through separation of control regions and server regions for dynamic workload management
  - IBM Parallel Sysplex support enables sophisticated failover capabilities and geographically distributed environments with centralized logging and administration

- WAS XD** improves manageability and scalability by enabling dynamic virtualization across application server pools. The ObjectGrid component—a standalone distributed caching solution—was introduced, compatible with any application server running JDK 1.4 or any J2SE 1.4 runtime environment, including zLinux and z/OS.

- Community Edition** is built upon the Apache Geronimo project.

With this release, certain features previously part of WebSphere Business Integration Server Foundation (WBISF) were transitioned to the newly established IBM WebSphere Process Server or migrated to other editions such as Express and higher tiers.

Version 5.1

Launched on January 16, 2004, this application server, compliant with J2EE 1.4 standards, featured the following editions:

Express
Base
Network Deployment
WebSphere Application Server for z/OS
The 5.1 release for z/OS added support for zAAP processors.
WebSphere Business Integration Server Foundation V5.1
Serving as the successor to WebSphere Application Server Enterprise Edition V5.0, this version incorporated a BPEL-compliant workflow engine that replaced the proprietary FDML. It was re-priced and made accessible across all IBM platforms, ranging from Intel-based systems to mainframes.
WebSphere eXtended Deployment (XD)

Version 5.0

Debuted on November 19, 2002, this J2EE 1.3 certified server represented a significant overhaul from versions 3 and 4 by unifying the codebase across all supported platforms—from Intel x86 architectures to mainframe environments—ensuring consistency throughout. The previous database-driven configuration was replaced by a replication-based XML file system overseen by a Deployment Manager responsible for maintaining the master cell configuration. Version 5 also introduced an embedded instance of MQ 5.3 as its Java Message Service (JMS) provider.

The Express Edition succeeded the Standard Edition, targeting small and medium-sized enterprises (SMEs) within IBM's software portfolio.
Base
Network Deployment offered clustered deployment capabilities with J2EE failover support and included Edge Components for proxying, load balancing, and content routing functions.
Enterprise Edition incorporated a workflow engine named Process Choreographer (predating BPEL) and introduced WebSphere Asynchronous Beans to facilitate application threading.
The WebSphere Application Server for z/OS edition mirrored Network Deployment features but was optimized to leverage z/OS functionalities such as Workload Manager, thereby enhancing scalability and security for critical enterprise workloads.

Version 4.0

This release was certified for J2EE 1.2 and maintained the database-based configuration model except in the single-server edition, which utilized an XML datastore instead. Editions included:

AE (Advanced Edition)
AEs (Advanced Edition single)—a single-server version without clustering capabilities.
AEd (Developer Edition)—similar to AEs but intended exclusively for development purposes outside of production environments.
EE (Enterprise Edition)

Version 3.5 (and 3.0)

Version 3.5 represented the first widely embraced iteration of WebSphere. On an IBM AIX RS6000 platform, startup begins with the primary WAS bootstrap process—a standalone Java JVM—that subsequently launches multiple JVM instances, each hosting an enterprise application equipped with its own classloader.

Due to classes being loaded across multiple JVMs, WebSphere provides configuration options to manage class visibility effectively. Both administrators and developers are required to carefully arrange the hierarchy of .ear and .war files along with their MANIFEST entries to prevent class conflicts. Ensuring correct class visibility is essential to avoid runtime issues such as type casting errors.

Version 2.0

IBM expanded support to include JavaBeans, CORBA, and Linux platforms while offering two editions: Standard Edition (SE) and Advanced Edition (AE).

Version 1.0

Released in June 1998, this initial version primarily served as a Java Servlet engine.

Security

The security architecture of WebSphere Application Server combines operating system capabilities with the Java EE security framework, accommodating various user registry types:

Local operating system user registry
LDAP-based user registry
Federated user registry (introduced in version 6.1)
Custom-defined user registry

Authentication is facilitated through IBM Lightweight Third Party Authentication (LTPA), which ensures strong user verification and access control.

External links

IBM WebSphere official site