• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Websphere 6 / RAD: what versions to use?

 
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi

We are possibly upgrading to Websphere 6.1 from WS 5.1.1.10, and I need some advice.

Our production and UAT / Staging environments will at some point require vertical and horizontal scaling for redundancy and failover. From my brief look , it would appear that we'll need WebSphere� Application Server Network Deployment V6.1

Our other test environments are Sys and Dev. A fully scaled Application Server environment seems here to be overkill, as at this point we're testing the business logic, so some other (less expensive!) Websphere option would seem to make sense. As there is potential for a number of projects to be on the go simultaneously, we'll need numerous instances of the Application Server each containing different instances of the middleware (which would ultimatley be merged at UAT prior to release). Would this point us to licences for IBM� WebSphere� Application Server, V6.1 as a less heavyweight version of the networked edition? Is it too simplistic to think of using the Community Edition for development? And if we use the Community Edition, we can run it inside Eclipse, avoiding the purchase of WS6.1 version of WSAD.

Having the full Network Deployment option across all environments seems like overkill to me, and would also be prohibitivly expensive. Our hardware is set out as follows:

Prod: 2 Servers, Dual 3.8GHz processor(HS20), 4Gb Ram, 40Gb Disk
UAT: Virtual Server x2, LS41 Quad AMD Opteron,
SYS: Virtual Server, HS20 Dual Processor, 2Gb Ram, 40Gb Disk
DEV: Virtual Server, HS20 Dual Processor, 2Gb Ram, 40Gb Disk

Any recommendations gratefully received!
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Alana Sparx:
we'll need numerous instances of the Application Server each containing different instances of the middleware (which would ultimatley be merged at UAT prior to release


Why can't they share an instance of WebSphere? You can create numerous application servers within the WebSphere cell and define resource references on the application level.
 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
First, the community edition is not a true WebSphere Application Server in the sence it is build on top og Apache Geronimo.

There are many differences between the WebSphere Base and ND version, some of them are related to HA configurations, functionality or daily maintance. Both versions can be used in any configuration, but each requires its own configuration.

The quest for more websphere instances in a development enviroment is quit common, since the developers want to try many things, and some require restarts or other intrusive things. From that point on it is quit common to specify different profiles in a development environment.

The main thing a ND version will add here is the single admin intarface through which the servers can be configured.
reply
    Bookmark Topic Watch Topic
  • New Topic