Updating the instance in a cluster on Feature Pack 6 or earlier (zero downtime)
You must manually control the node agents and servers in the cluster to ensure that your site remains available during a fix pack upgrade.
Before you begin
- Ensure that the WebSphere Application Server Deployment Manager (DMGR) and all node agents are running.
- Ensure that your store is online and serving traffic.
About this task
- You are on WebSphere Commerce Fix Pack 7 or later
- You are on Feature Pack 6 or earlier
- You have a clustered environment similar to the following diagram:
Note: This task assumes that you have three nodes in your cluster. If you have more than three
nodes, group multiple nodes to conform to the diagram and group the nodes in a way that ensures site
availability during the update. Consider the states of your servers and decide how you want to group
your nodes:
- Initially you take down the servers in node WN1, therefore your site initially relies on nodes WN2 and WN3 to serve traffic.
- When the nodes in WN1 are updated, you update nodes WN2 and WN3, which forces your site to rely solely on the servers on WN1 to serve traffic.
- Group four nodes to represent WN1, three nodes to represent WN2, and two nodes to represent WN3. Therefore, your site has the five servers in WN2 and WN3 to serve traffic while the servers in WN1 are updating. After the update, your site can rely on the four updated servers in WN1 while WN2 and WN3 are updating.
Procedure
Results
What to do next
Depending on your environment, you might have to complete some final steps. For more information, see Installing final steps.