Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1111
  • Last Modified:

Deployment on Websphere ND Server Clustered Environment Without Outage....

Hi All,

Has anyone done this ???

Whenever you deploy the new version of the application we stop the application, uninstall the existing version & install the new version.

Now, our problem is we dont want to bring down the server.

Environment:

We have a websphere ND server clustered environment. In the current environment we have one deployment manager & multiple appservers are federated to this. We dont deploy the application on individual servers, instead we deploy the application on Deployment Manager. The DMgr transparently deploys on the individual servers.

For doing this we need to stop the application, uninstall it. This will uninstall from all the servers. so, we need an outage until new version is installed.

we want to avoid this, we want to upgrade the servers one by one ....so, that our system will be running 24/7.

can you think of some solution.

Any help will be highly appreciated.

thanks & regards,

*satish
0
satishAnanthuni
Asked:
satishAnanthuni
  • 2
1 Solution
 
Peter KwanAnalyst ProgrammerCommented:
One option is to
1. install the new version first, using another application name (You can set it in the Step 1 page).
2. Stop the old version
3. Start the new version
4. Uninstall the old version
0
 
satishAnanthuniAuthor Commented:
Hi Wan,

I will try this...

we create separate profiles for the app servers but there is only one deployment manager. We deploy the application on dmgr.

Is there any configuration or setting in the websphere for stopping the server one by one & upgrading it ?


If this is not possible,

I was thinking of option of having multiple deployment managers.

*satish
0
 
satishAnanthuniAuthor Commented:
Hi,

I have found this solution, I will try this:

WebSphere Application Server version 6 has a new cluster-update feature to phase distribute an update to each of a cluster's members one node at a time, including the stopping and restarting of affected servers being updated. Where server failure and session recovery have been configured and provide sufficient functionality, very good high availability will be provided during cluster updates. This feature currently cannot be used to phase distribute an update to unclustered servers and does not do preemptive quiescing or reactivation of work rerouting. If multiple cluster members are on the same node (vertical clustering for scalability), then they will be simultaneously updated (and simultaneously unavailable) as if the Node Agent had performed a regular NodeSync.

Also WebSphere Application Server version 6 cluster updates can only be done for one application at a time. If multiple applications need to be updated within a cluster, then multiple cluster update operations must be individually performed, and each cluster member node and its affected servers will be cycled again during each individual cluster update.
In summary, the WebSphere Application Server version 6 new cluster-update feature is a convenient way to distribute a single update throughout a horizontal cluster with cluster members across multiple nodes, and it does so while maintaining high-availability.

*satish
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now