Goto Wellesley Information Services web site

The Sphere Journal

Home|Subscribe|Knowledgebase|About Us|Contact Us|Downloads

 email address 

  password 

  search 

Our Subscribers
e-Newsletters
Read a Sample Article
Helpful Resources
Renew
 

Choosing the WebSphere Application Server ND topology that's right for your system

Achieving high stability for multiclient WebSphere applications

Jamie Pope, senior technology manager
Ying Ding, president, Greater Charlotte WebSphere Users Group

November, 2008


Many enterprise WebSphere systems use topologies that share Java Virtual Machine (JVM) clusters with both mission-critical core applications and client applications. Learn about three alternate topologies based on WebSphere Application Server Network Deployment (ND) that you can implement to prevent costly system instability and downtime.


A large WebSphere system can have hundreds of Java Virtual Machine (JVM) instances running on more than a dozen physical servers at multiple data centers. To simplify administration and management, many companies employ an infrastructure where numerous client applications share the same JVM cluster with a large, mission-critical enterprise application that they contact for a service or data. However, this architectural model can raise a pronounced risk for a company in terms of the system’s overall stability. Because both the client applications and the enterprise application run on a single clustered JVM, a glitch in one system can affect all of the systems. The system downtime that follows any such failure — and the time it takes to isolate the problem — can adversely affect a company’s bottom line and customer satisfaction.

To help WebSphere system and application professionals avoid such potential stability pitfalls, we discuss three architectural solutions that use topologies based on WebSphere Application Server Network Deployment (ND) and show how you can achieve high resiliency and high stability for your enterprise WebSphere systems. For each solution, we highlight the challenges you may encounter and the factors you should consider when planning the design and implementation of the infrastructure.

Before discussing the challenges you face in choosing the topology to best support and enhance the stability of your WebSphere systems, we take a moment to define our terms in this discussion. By “core application,” we mean a large mission-critical enterprise Java EE application or application suite that executes within the Java EE containers provided by a dedicated WebSphere Application Server system. A “client application” is a Java EE application that typically requests services from the core application. “WebSphere infrastructure” refers to a physical server, such as an IBM midrange server, and other related hardware and system software, such as the operating system software and WebSphere Application Server system software.

Electronic license holders click here to access full article.

Would you like to see the full version of this and every article? Click here to subscribe.


Download The Sphere 2008
Solutions Supplement

Evaluation Guide & Checklist - How to Choose a Web Application Management Solution