Version 6.0.1 and later WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Applying fix packs to multiple clusters in the same cell

This section describes applying fix packs to multiple clusters in the same cell using Deployment Manager

The section takes into consideration applying fix packs to multiple clusters in the same cell.

WebSphere Portal Express fix packs are always applied to every installation of WebSphere Portal Express to ensure all file system resources are updated. If a particular WebSphere Portal Express profile serves as the primary profile for a cluster definition, the Portal Update Installer utility determines if any of either the updated applications or portlets in the filesystem are actually in use by the cluster, and if so, updates the application through Deployment Manager.

Most WebSphere Portal Express fix packs contain fixes to several enterprise applications and portlets. Since there could be multiple primary WebSphere Portal Express profiles in the same cell, one for each unique cluster, it is possible that common applications will get updated more than once, each time the primary portal profile is updated. Control the synchronization of these updates to all clusters, to ensure that only those clusters whose nodes have been updated also receive the updated application.

To ensure this goes smoothly, use the following procedure. For this example, assume the cell has two portal-based clusters, Cluster A and Cluster B, that are currently at the same maintenance level, but are independently configured portals. Also, for this example, assume that traffic can be stopped against Cluster A, then Cluster B, or both at the same time. If high availability is required, where production traffic is maintained during this update, then parallel clusters (Cluster A and Cluster B) must be available, identically configured to their counterparts, that can remain in production until both clusters are fully updated.

  1. Disable automatic synchronization for the cell within Deployment Manager’s administration console. This puts synchronization of updates made to any aspect of the cell’s configuration with the managed nodes within administrative control.

  2. Apply the fix pack to Cluster A’s primary node. The Portal Update Installer utility detects that this is the primary node and applies any application updates contained within the fix pack to currently deployed applications. The utility may also update the common database domains.

  3. Using Deployment Manager’s Administration Console, manually synchronize configuration updates to the primary server in Cluster A.

  4. Apply the fix pack to each secondary node in Cluster A, and using the Deployment Manager’s Administration Console, manually synchronize configuration updates with that secondary node.

  5. Test the updates made to Cluster A.

  6. Repeat steps 1 through 5 on Cluster B.

  7. Re-enable automatic synchronization once the update is complete.
If any applications are common between Cluster A and Cluster B, they will have been updated twice, when the primary nodes in each cluster are updated with the fix pack. Although it is a redundant operation, following these basic procedures consistently, regardless of the cluster being updated, ensures a complete upgrade.

 

Parent topic:

Version 6.0.1 and later Installing updates for multiple clusters

 

Next topic

Version 6.0.1 and later Applying interim fixes to multiple clusters in the same cell