Before you begin
Prepare your environment for high availability Application Update.Why and when to perform this task
Workload routing is controlled by stopping the Application Server on which the cluster member being updated resides. This results in a quiesce of that server. All existing requests already in the server are allowed to complete, but no new requests are accepted. Both the Sysplex Distributor and the WebSphere Application Server's Web server plug-in will route work away from the quiescing server. After all work has completed, start the application update process on this server:
Steps for this task
set node NODE set na_id [$AdminConfig getid /Node:$node/Server:nodeagent/] set syncServ [$AdminConfig list ConfigSynchronizationService $na_id] $AdminConfig modify $syncServ {{autoSynchEnabled false}} $AdminConfig modify $syncServ {{synchOnServerStartup false}} $AdminConfig save set nodeSync [$AdminControl completeObjectName type=NodeSync,node=$node,*] $AdminControl invoke $nodeSync sync
Note: For a production environment, it is reasonable to always run the node agent with automatic synchronization disabled. However, it is advisable for startup synchronization to be enabled for the node agent so that it can acquire configuration updates that occur when the node agent is down. Startup Synchronization can be left enabled provided you can ensure that you will not restart the node agent manually, through automation, or through automatic restart manager during the application update process.
set app_loc /path/to/app set app_options {application options ie: -appname app} set options [list -update] lappend options $app_options $AdminApp install $app_loc $options $AdminConfig save
At this point, you have the updated the version of your application (App v2 in the following figure) in your Master Configuration. However, the original version of your application (App v1 in the following figure) is still running in the cluster that has Cluster members on LPAR1 and LPAR2.
Perform one of the following processes to complete this step:
set node NODE set server SERVER $AdminControl stopServer $server $node
STOP short_server_nameFor example:
STOP BBOS001
set node NODE set nodeSync [$AdminControl completeObjectName type=NodeSync,node=$node,*] $AdminControl invoke $nodeSync sync
As illustrated in the following figure, the updated version of the application (App v2) now resides in the node on LPAR1.
set node NODE set server SERVER $AdminControl startServer $server $node
START procname,JOBNAME=server_short_name.ENV=cell_short_name.node_short_name.server_short_nameFor example:
START BBO5ACR,JOBNAME=BBOS001,ENV=PLEX1.SY1.BBOS001
Results
The application update process is complete when the new version of the application is running on all of the LPARs in the cluster. The following figure illustrates what a two LPAR cluster will look like after you restart the server on LPAR2.