IBM WebSphere Application Server (WAS)
2012-09-06 17:22
477 查看
IBM WebSphere Application Server (WAS), a softwareapplication server, is the flagship product withinIBM'sWebSphere
brand. It was initially created by Donald Ferguson, who later became CTO ofCA Technologies,[3]
and the first version launched in 1998.
open standards such as
Java EE,
XML, and
Web Services. It is supported on the following platforms: Windows, AIX, Linux, Solaris, i/OS andz/OS. Beginning
with Version 6.1 and now into Version 8.5, the open standard specifications are aligned and common across all the platforms. Platform exploitation, to the extent it takes place, is donebelow the open standard specification line.
It works with a number of
Web servers including
Apache HTTP Server,
Netscape Enterprise Server,
Microsoft
Internet Information Services (IIS),
IBM HTTP Server for
i5/OS, IBM HTTP Server for
z/OS, and IBM HTTP Server for
AIX/Linux/Microsoft Windows/Solaris.
It uses port 9060 for connection as the default.
This table is derived from
IBM has shipped several versions and editions of WebSphere Application Server.
In the first beta versions, WebSphere had been called
Servlet Express.
Although the versioning scheme x.1 and x.5 would usually indicate a
minor release in the software industry, WebSphere v6.1 and v5.1 are major releases, just like WebSphere v8.5 and v3.5.[7]
Java EE 6 and
Java SE 6 (by default) as V8.0 and also provides - and can be configured to run on -Java SE 7. The primary new capabilities
in V8.5 are theLiberty profile of WebSphere Application Server and theintelligent management features.
The Liberty profile of WebSphere Application Server is included with all the commercial editions of the server, providing a lightweight profile of the server for web, mobile and OSGi applications. It is a functional subset of the full profile
of WebSphere Application Server, for both development and production use, with an install size of under 50 MB, a startup time of around 3 seconds and a new XML-based server configuration which can be treated as a development artefact to aid developer productivity.
Server capabilities are engaged through the set of features defined in the server configuration; features are added and removed dynamically through internal use of OSGi services. A new model is provided for moving applications through the pipeline
from development to production as a packaged server; this is a complete archive of the server, server configuration and application forunzip deploy. A centralized managed install is optionally available through theJob Manager component
of WebSphere Application Server Network Deployment edition.
Intelligent management capability is added in the Network Deployment andz/OS editions of WebSphere Application server. This integrates operational features that were previously available in the separateWebSphere Virtual
Enterprise (WVE) offering: application editioning, server health management, dynamic clustering and intelligent routing.
Java EE 6 compliant application server and incorporates the capabilities originally delivered as feature packs with WebSphere Application Server V7. This version of WebSphere Application Server is installed using the IBM Installation Manager.
Java EE 5 compliant application server.
Following are the flagship features introduced by WebSphere Application Server Version 7:
Flexible Management
Flexible Management facilitates administration of a large number of WebSphere Application Server base edition and Network Deployment topologies that might be geographically distributed.
Business-Level Application
Business-Level Application is used for managing application artifacts independent of packaging or programming models.
Property Based Configuration
The Property Based Configuration feature simplifies the experience of automating administration: an administrator can update the WebSphere Application Server Version 7 configuration using a simple property file.
Between the general availability of WebSphere Application Server V7 and WebSphere Application Server V8 (in 2011), a number of additional capabilities were made available for V7 in the form offeature packs which are optionally added to a V7 install.
Feature Pack content has the same quality and support as main release content - the purpose of a feature pack is to deliver new innovation before the next major release. The following feature packs were provided for WebSphere Application Server V7:
Feature Pack for Modern Batch
Feature Pack for OSGi Applications and JPA 2.0
Feature Pack for SCA
Feature Pack for Web 2.0 and Mobile
Feature Pack for XML
Feature Pack for Communication Enabled Applications
Java EE 1.4 compliant application server and includes the following function:
Support for Java Standard Edition 1.5
Support for running
JSR 168
Portlets in the application server
Session Initiation Protocol (SIP) Servlets
Enhancements to the WebSphere Install Factory
IBM Support Assistant
IBM JSF
Widget Library
Simplified Administration
Improved Certificate and Key Management
Security Enhancements
Administration of
IBM HTTP Server from WebSphere Admin Console
Support for (pre-OASIS)WS-Security 1.0
Support for
Web Services Resource Framework and WS-BusinessActivity (WS-BA)
Support for JSR160 JMX Remote Connections (From IBM Agents Only)
Administrative Console
Jython Command Assistance
Enhanced scripting. This version started the deprecation process for the Jacl syntax.[8]
64-bit servants and a new Apache-based IBM HTTP Server for z/OS
Support for the EJB 3.0 technology and support for some webservices standards were provided by the EJB feature pack and the webservices feature packs, respectively. These function in these feature packs has been folded into the main product in version 7.
Functions in the webservices feature pack include:
Asynchronous programming model (Limited functional support)
Multiple Payload structures
StAX (Streaming API for XML)
WS-RM (Limited functional support)
Support for (OASIS specified)WS-Security 1.0.
WS-Addressing (Limited functional support)
JAX-B support
Policy Set (Limited functional support)
Secured thin client (Limited functional support)
SOAP (protocol) Message Transmission Optimization Mechanism (MTOM)
Supports CGI and CORBA
Java EE 1.4 compliant application server. Security enhancements include support for JACC 1.0 and (pre-OASIS)WS-Security
1.0.
Support for Java Standard Edition 1.4
Community Edition (free,support
for fee)
Code based on
Apache Geronimo projectMany programming model extensions previously found in WebSphere Application Server V5.0 Enterprise Edition were moved out of enterprise and into Express and Base. These APIs included application profile, startup beans, the scheduler, and async beans.The JMS engine, now called "WebSphere Platform Messaging," was rewritten in 100% Java and its functionality greatly enhanced. (WebSphere MQ is still supported as the JMS provider and is interoperable with WebSphere Platform Messaging.)The clustering was rewritten to use the high availability manager. This manages all singletons in the WebSphere environment and can provide hot recovery for those singletons.WebSphere was modified so that a shared file system can be used to store transaction logs and this meant that any cluster member with that shared file system mounted can hot recover in-doubt XA transactions with no external HA software.The Deployment Manager's role was eliminated from all clustering runtime operations. It's only required for centralizedJMX admin and
config changes.Now supports running mixed version cells (V5 to V6) in production.
WebSphere Application Server for z/OS
Provides the same core functionality as Network Deployment, since it shares a common programming model, but still contains the platform advantages such as:
z/OS Workload Manager for prioritized management of mixed workloads
Resource Recovery Services (added transactional integrity for complex, critical transactions)
Support for security mainframe products such a
RACF
Advanced vertical scaling for application server by featuring a unique control region (integrated control area) server region (where workloads are completed) separation which enables the control region to open and close server regions as needed by the volume
of incoming requests
Parallel Sysplex support for full participation in the Sysplex, enabling advanced failover support and a geographically dispersed environment that
seamlessly acts as one with a centralized logging and management facility
WAS XD as it is known increases the functionality of the application server in two main areas - Manageability and Performance. It also allows makes possible new configurations, such as dynamic virtualization between pools of application servers.Under the performance header the ObjectGrid component was added, which is a standalone distributed cache that can be used with any application server (any version with a 1.4 JDK) or with any J2SE 1.4 runtime, including zLinux and z/OS support.
With Version 6, some of the functionality previously found in WebSphere Business Integration Server Foundation (WBISF) moved into the newIBM
WebSphere Process Server. Other function moved into the other editions (Express and above).
from
Intel x86 to the mainframe, are substantially the same code. The database-based configuration repository was replaced with a replicationXML file-based configuration repository. A
service called theDeployment Manager had the master copy of the cell configuration, and nodes had the file(s) they needed copied from this master server whenever they changed. V5 also included a miniature version ofMQ
5.3 called the embedded
Java Message Service (JMS) server.
Express Edition replaces the Standard Edition. Express now becomes the term to indicateSME-oriented offerings
from IBM, across all its software brands.
Base
Network Deployment. This version supports deployment of a cell configuration with cluster and J2EE failover support. It now also includesEdge Components, previously known asEdge Server. This provides a proxy server,
load balancing, and content-based routing.
Enterprise Edition. This version added a workflow engine, called theProcess Choreographer, for the first time but predates theBPEL
standard. It also added the first fully supported application threading model called WebSphere Asynchronous Beans.
WebSphere Application Server for z/OS. This version is essentially the same as the Network Deployment product but is optimized to take full advantage of z/OS features, such as Workload Manager, to leverage the key technologies that make the mainframe
indispensable for mission-critical, scalable, and secure workloads.
Express
Base
Network Deployment
WebSphere Application Server for z/OS
Version 5.1 for z/OS is the first to support
zAAP engines.
WebSphere Business Integration Server Foundation V5.1
This is the follow on product to WebSphere Application Server Enterprise Edition V5.0. The workflow engine was updated to support BPEL rather than the proprietaryFDML
format used in V5.0. The product was also repriced and available on all IBM platforms from the Intel environments to the mainframe.
WebSphere eXtended Deployment (XD)
For more information please reference the
#WebSphere eXtended Deployment section below.
AE (Advanced Edition)
AEs (Advanced Edition single). Single-server edition that was not able to run in a cluster configuration.
AEd (Developer Edition). Functionally equivalent to AEs, but intended only for non-production development use.
EE (Enterprise Edition)
JavaBean,
CORBA and
Linux support. Comes in two editions: Standard Edition (SE) and Advanced Edition (AE).
Java Servlet engine.
security model. WebSphere Application Server provides implementations of user authentication and authorization mechanisms providing support for various user registries:
Local operating system user registry
LDAP user registry
Federated user registry (as of version 6.1)
Custom user registry
The authentication mechanisms supported by WebSphere are[9]
Lightweight Third Party Authentication (LTPA)
Java (software platform)
zSeries Application Assist Processor
zAAP
IBM Rational Application Developer
IBM Rational Business Developer
Java EE version history
Other Java EE application servers:
Comparison of application servers
Apache Geronimo/Tomcat
GlassFish
JBoss AS
SAP NetWeaver Application Server
WebLogic Server
product lifecycle dates
^http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921,
WebSphere Application Server detailed system requirements
^"The
mantra of CA Technologies' Donald Ferguson: Simplify".BBC.com. 8 December 2010. Retrieved 17 October 2011.
^IBM
United States Software Announcement 212-109
^After
upgrade from version 6 delivered in standard
^With
EJB Feature Pack; otherwise 2.1
^Update
Strategy for WebSphere Application Server V6.1
^SG24-7304-00
WebSphere Application Server V6.1: System Management and Configuration, p. 250
^SG24-6316-01
IBM WebSphere Application Server V6.1 Security Handbook
World Wide WebSphere User Group
Jerry Cuomo's blog - the WebSphere CTO provides insights into the directions of the WebSphere team
brand. It was initially created by Donald Ferguson, who later became CTO ofCA Technologies,[3]
and the first version launched in 1998.
Architecture
WAS is built usingopen standards such as
Java EE,
XML, and
Web Services. It is supported on the following platforms: Windows, AIX, Linux, Solaris, i/OS andz/OS. Beginning
with Version 6.1 and now into Version 8.5, the open standard specifications are aligned and common across all the platforms. Platform exploitation, to the extent it takes place, is donebelow the open standard specification line.
It works with a number of
Web servers including
Apache HTTP Server,
Netscape Enterprise Server,
Microsoft
Internet Information Services (IIS),
IBM HTTP Server for
i5/OS, IBM HTTP Server for
z/OS, and IBM HTTP Server for
AIX/Linux/Microsoft Windows/Solaris.
It uses port 9060 for connection as the default.
Version history
| WebSphere version | 8.5 | 8.0 | 7.0 | 6.1 | 6.0 | 5.1 | 5.0 | 4.0 | 3.5 |
|---|---|---|---|---|---|---|---|---|---|
| Release date | 15 Jun 2012 [4] | 17 Jun 2011 | 17 Oct 2008 | 30 Jun 2006 | 31 Dec 2004 | 16 Jan 2004 | 03 Jan 2003 | 15 Aug 2001 | 31 Aug 2000 |
| End of support | 30 Sept 2012 | 30 Sept 2010 | 30 Sept 2008 | 30 Sept 2006 | 30 April 2005 | 30 Nov 2003 | |||
| Java SE | 7 [5] | 6 | 6 | 5 | 1.4 | 1.4 | 1.3 | 1.3 | 1.2 |
| Java EE | 6 | 6 | 5 | 1.4 | 1.4 | 1.3 | 1.3 | 1.2 | 1.2 (not fully compliant) |
| Servlet | 3.0 | 3.0 | 2.5 | 2.4 | 2.4 | 2.3 | 2.3 | 2.2 | 2.1&2.2 |
| JSP | 2.2 | 2.2 | 2.1 | 2.0 | 2.0 | 1.2 | 1.2 | 1.1 | 0.91 and 1.0&1.1 |
| JSF | 2.0 | 2.0 | 1.2 | 1.1 | 1.0 | ||||
| EJB | 3.1 | 3.1 | 3.0 | 3.0 [6] | 2.1 | 2.0 | 2.0 | 1.1 | 1.0 |
| JMS | 1.1 | 1.1 | 1.1 | 1.1 | 1.1 | 1.02 | |||
| JDBC | 4.1 | 4.0 | 4.0 | 3.0 | 3.0 | ||||
| JPA | 2.0 | 2.0 | 2.0 | 1.0 |
In the first beta versions, WebSphere had been called
Servlet Express.
Although the versioning scheme x.1 and x.5 would usually indicate a
minor release in the software industry, WebSphere v6.1 and v5.1 are major releases, just like WebSphere v8.5 and v3.5.[7]
Version 8.5
WebSphere Application Server V8.5 offers the sameJava EE 6 and
Java SE 6 (by default) as V8.0 and also provides - and can be configured to run on -Java SE 7. The primary new capabilities
in V8.5 are theLiberty profile of WebSphere Application Server and theintelligent management features.
The Liberty profile of WebSphere Application Server is included with all the commercial editions of the server, providing a lightweight profile of the server for web, mobile and OSGi applications. It is a functional subset of the full profile
of WebSphere Application Server, for both development and production use, with an install size of under 50 MB, a startup time of around 3 seconds and a new XML-based server configuration which can be treated as a development artefact to aid developer productivity.
Server capabilities are engaged through the set of features defined in the server configuration; features are added and removed dynamically through internal use of OSGi services. A new model is provided for moving applications through the pipeline
from development to production as a packaged server; this is a complete archive of the server, server configuration and application forunzip deploy. A centralized managed install is optionally available through theJob Manager component
of WebSphere Application Server Network Deployment edition.
Intelligent management capability is added in the Network Deployment andz/OS editions of WebSphere Application server. This integrates operational features that were previously available in the separateWebSphere Virtual
Enterprise (WVE) offering: application editioning, server health management, dynamic clustering and intelligent routing.
Version 8.0
This version was released on June 17, 2011. It is aJava EE 6 compliant application server and incorporates the capabilities originally delivered as feature packs with WebSphere Application Server V7. This version of WebSphere Application Server is installed using the IBM Installation Manager.
Version 7.0
This version was released on September 9, 2008. It is aJava EE 5 compliant application server.
Following are the flagship features introduced by WebSphere Application Server Version 7:
Flexible Management
Flexible Management facilitates administration of a large number of WebSphere Application Server base edition and Network Deployment topologies that might be geographically distributed.
Business-Level Application
Business-Level Application is used for managing application artifacts independent of packaging or programming models.
Property Based Configuration
The Property Based Configuration feature simplifies the experience of automating administration: an administrator can update the WebSphere Application Server Version 7 configuration using a simple property file.
Between the general availability of WebSphere Application Server V7 and WebSphere Application Server V8 (in 2011), a number of additional capabilities were made available for V7 in the form offeature packs which are optionally added to a V7 install.
Feature Pack content has the same quality and support as main release content - the purpose of a feature pack is to deliver new innovation before the next major release. The following feature packs were provided for WebSphere Application Server V7:
Feature Pack for Modern Batch
Feature Pack for OSGi Applications and JPA 2.0
Feature Pack for SCA
Feature Pack for Web 2.0 and Mobile
Feature Pack for XML
Feature Pack for Communication Enabled Applications
Version 6.1
This version was released on June 30, 2006. It is aJava EE 1.4 compliant application server and includes the following function:
Support for Java Standard Edition 1.5
Support for running
JSR 168
Portlets in the application server
Session Initiation Protocol (SIP) Servlets
Enhancements to the WebSphere Install Factory
IBM Support Assistant
IBM JSF
Widget Library
Simplified Administration
Improved Certificate and Key Management
Security Enhancements
Administration of
IBM HTTP Server from WebSphere Admin Console
Support for (pre-OASIS)WS-Security 1.0
Support for
Web Services Resource Framework and WS-BusinessActivity (WS-BA)
Support for JSR160 JMX Remote Connections (From IBM Agents Only)
Administrative Console
Jython Command Assistance
Enhanced scripting. This version started the deprecation process for the Jacl syntax.[8]
64-bit servants and a new Apache-based IBM HTTP Server for z/OS
Support for the EJB 3.0 technology and support for some webservices standards were provided by the EJB feature pack and the webservices feature packs, respectively. These function in these feature packs has been folded into the main product in version 7.
Functions in the webservices feature pack include:
Asynchronous programming model (Limited functional support)
Multiple Payload structures
StAX (Streaming API for XML)
WS-RM (Limited functional support)
Support for (OASIS specified)WS-Security 1.0.
WS-Addressing (Limited functional support)
JAX-B support
Policy Set (Limited functional support)
Secured thin client (Limited functional support)
SOAP (protocol) Message Transmission Optimization Mechanism (MTOM)
Supports CGI and CORBA
Version 6.0
This version was released on December 31, 2004. It is aJava EE 1.4 compliant application server. Security enhancements include support for JACC 1.0 and (pre-OASIS)WS-Security
1.0.
Support for Java Standard Edition 1.4
Community Edition (free,support
for fee)
Code based on
Apache Geronimo projectMany programming model extensions previously found in WebSphere Application Server V5.0 Enterprise Edition were moved out of enterprise and into Express and Base. These APIs included application profile, startup beans, the scheduler, and async beans.The JMS engine, now called "WebSphere Platform Messaging," was rewritten in 100% Java and its functionality greatly enhanced. (WebSphere MQ is still supported as the JMS provider and is interoperable with WebSphere Platform Messaging.)The clustering was rewritten to use the high availability manager. This manages all singletons in the WebSphere environment and can provide hot recovery for those singletons.WebSphere was modified so that a shared file system can be used to store transaction logs and this meant that any cluster member with that shared file system mounted can hot recover in-doubt XA transactions with no external HA software.The Deployment Manager's role was eliminated from all clustering runtime operations. It's only required for centralizedJMX admin and
config changes.Now supports running mixed version cells (V5 to V6) in production.
WebSphere Application Server for z/OS
Provides the same core functionality as Network Deployment, since it shares a common programming model, but still contains the platform advantages such as:
z/OS Workload Manager for prioritized management of mixed workloads
Resource Recovery Services (added transactional integrity for complex, critical transactions)
Support for security mainframe products such a
RACF
Advanced vertical scaling for application server by featuring a unique control region (integrated control area) server region (where workloads are completed) separation which enables the control region to open and close server regions as needed by the volume
of incoming requests
Parallel Sysplex support for full participation in the Sysplex, enabling advanced failover support and a geographically dispersed environment that
seamlessly acts as one with a centralized logging and management facility
WAS XD as it is known increases the functionality of the application server in two main areas - Manageability and Performance. It also allows makes possible new configurations, such as dynamic virtualization between pools of application servers.Under the performance header the ObjectGrid component was added, which is a standalone distributed cache that can be used with any application server (any version with a 1.4 JDK) or with any J2SE 1.4 runtime, including zLinux and z/OS support.
With Version 6, some of the functionality previously found in WebSphere Business Integration Server Foundation (WBISF) moved into the newIBM
WebSphere Process Server. Other function moved into the other editions (Express and above).
Version 5.1
This version was released on 16 Jan 2004. It is a J2EE 1.3 compliant application server.Version 5.0
The version released on 19 November 2002. This was a J2EE 1.3 certified application server. It was a major rewrite of the V3/V4 codebase and was the first time WebSphere Application Server was coded from a common codebase. Now WAS across all deployment platforms,from
Intel x86 to the mainframe, are substantially the same code. The database-based configuration repository was replaced with a replicationXML file-based configuration repository. A
service called theDeployment Manager had the master copy of the cell configuration, and nodes had the file(s) they needed copied from this master server whenever they changed. V5 also included a miniature version ofMQ
5.3 called the embedded
Java Message Service (JMS) server.
Express Edition replaces the Standard Edition. Express now becomes the term to indicateSME-oriented offerings
from IBM, across all its software brands.
Base
Network Deployment. This version supports deployment of a cell configuration with cluster and J2EE failover support. It now also includesEdge Components, previously known asEdge Server. This provides a proxy server,
load balancing, and content-based routing.
Enterprise Edition. This version added a workflow engine, called theProcess Choreographer, for the first time but predates theBPEL
standard. It also added the first fully supported application threading model called WebSphere Asynchronous Beans.
WebSphere Application Server for z/OS. This version is essentially the same as the Network Deployment product but is optimized to take full advantage of z/OS features, such as Workload Manager, to leverage the key technologies that make the mainframe
indispensable for mission-critical, scalable, and secure workloads.
Express
Base
Network Deployment
WebSphere Application Server for z/OS
Version 5.1 for z/OS is the first to support
zAAP engines.
WebSphere Business Integration Server Foundation V5.1
This is the follow on product to WebSphere Application Server Enterprise Edition V5.0. The workflow engine was updated to support BPEL rather than the proprietaryFDML
format used in V5.0. The product was also repriced and available on all IBM platforms from the Intel environments to the mainframe.
WebSphere eXtended Deployment (XD)
For more information please reference the
#WebSphere eXtended Deployment section below.
Version 4.0
This was a J2EE 1.2 certified application server. It inherited the database-based configuration model from V3.x for all but the single-server edition, which already used an XML datastore.AE (Advanced Edition)
AEs (Advanced Edition single). Single-server edition that was not able to run in a cluster configuration.
AEd (Developer Edition). Functionally equivalent to AEs, but intended only for non-production development use.
EE (Enterprise Edition)
Version 3.5 (and 3.0)
WebSphere 3.5 is the first widely used version of WebSphere.Version 2
IBM addsJavaBean,
CORBA and
Linux support. Comes in two editions: Standard Edition (SE) and Advanced Edition (AE).
Version 1
Initial release in June, 1998. Was primarily aJava Servlet engine.
Security
The WebSphere Application Server security model is based on the services provided in the operating system and theJava EEsecurity model. WebSphere Application Server provides implementations of user authentication and authorization mechanisms providing support for various user registries:
Local operating system user registry
LDAP user registry
Federated user registry (as of version 6.1)
Custom user registry
The authentication mechanisms supported by WebSphere are[9]
Lightweight Third Party Authentication (LTPA)
See also
IBM HTTP ServerJava (software platform)
zSeries Application Assist Processor
zAAP
IBM Rational Application Developer
IBM Rational Business Developer
Java EE version history
Other Java EE application servers:
Comparison of application servers
Apache Geronimo/Tomcat
GlassFish
JBoss AS
SAP NetWeaver Application Server
WebLogic Server
References
^WebSphereproduct lifecycle dates
^http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921,
WebSphere Application Server detailed system requirements
^"The
mantra of CA Technologies' Donald Ferguson: Simplify".BBC.com. 8 December 2010. Retrieved 17 October 2011.
^IBM
United States Software Announcement 212-109
^After
upgrade from version 6 delivered in standard
^With
EJB Feature Pack; otherwise 2.1
^Update
Strategy for WebSphere Application Server V6.1
^SG24-7304-00
WebSphere Application Server V6.1: System Management and Configuration, p. 250
^SG24-6316-01
IBM WebSphere Application Server V6.1 Security Handbook
External links
WebSphere software brand siteWorld Wide WebSphere User Group
Jerry Cuomo's blog - the WebSphere CTO provides insights into the directions of the WebSphere team
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- 利用 IBM Tivoli Directory Server V5.2 实现 WebSphere Application Server V6.0.x 的全局安全性并保护 WAS 管理控制台
- linux系统安装IBM WebSphere Application Server（简称WAS）报错：JVM terminated. Exit code=1 ....
- 在 Eclipse 中结合 IBM WebSphere Application Server 使用
- (转)Eclipse 远程调试 WebSphere Application Server (WAS)
- Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566)
- IBM WebSphere Application Server 诊断和调优
- BM WebSphere 系列产品和 BEA Tuxedo Server 的集成方案，第 2 部分: 通过 XUG 建立IBM WebSphere Application Server 和BEA Tuxedo Server 的访问通路
- IBM WebSphere Application Server 诊断和调优---宕机问题分析（二）
- IBM WebSphere Application Server V6.1 Fix Pack 29于2010.01.18发布
- IBM WebSphere 开发者技术期刊: WebSphere Application Server V6 的系统管理
- IBM WebSphere Application Server 诊断和调优---宕机问题分析（一）
- IBM WebSphere Application Server V7.0 Fix Pack 9于2010.03.25发布
- WebSphere Application Server 更新web.xml的问题以解决有些应用在tomcat环境下可以跑，更新到was上失效的问题
- IBM WebSphere Application Server Network Deployment 6集群简单介绍
- 开发者技术期刊: 为 IBM WebSphere Application Server 开发 Spring 应用程序——第 1 部分
- 关于 IBM WebSphere Application Server 产品家族的问题集锦
- IBM DB2 Alphablox 8.3 build 149 安装过程 部署 WebSphere Application Server 6.0.1上
- IBM WebSphere Application Server下使用URL Rewrting进行Session Tracking的实现
- Eclipse 远程调试 WebSphere Application Server (WAS)
- IBM WebSphere Application Server诊断和调优