Version 6.0.1 and later WebSphere

 

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

 

Applying interim fixes to multiple clusters in the same cell

This section describes applying interim fixes to multiple clusters in the same cell using Deployment Manager

The section takes into consideration applying interim fixes, also known as interim fixes or APARS, to multiple clusters in the same cell.

Interim fixes, like fix packs, may contain updates to either enterprise applications or portlets, or both. But unlike fix packs, installation of an interim fix will not automatically update the target application or portlet. That operation will be left to the administrator, per instructions delivered with the interim fix.

If an interim fix does not contain any application or portlet updates, it can be applied to any portal cluster member in any cluster in any order, and it restarts each updated server accordingly. It may not be obvious, however, just by looking at the contents of an interim fix, if an application or portlet update is necessary. When in doubt, contact IBM Service.

If an interim fix requires updates to an application, first use the procedure documented in Application sharing between clusters to determine if the application is shared between clusters, and if so, which ones. To apply the update, follow these steps:

  1. Disable automatic synchronization for the cell within Deployment Manager’s administration console. This will put synchronization of updates made to any application with the managed nodes in the administrator's control.

  2. If the update applies to a standard enterprise application, update the application as instructed by the iinterim fix documentation.

  3. If the update is to a portlet, pick a WebSphere Portal Express node where a configured cluster member profile is running this portlet application. Update the portlet on that node as instructed by the interim fix documentation. .

  4. Manually synchronize the updated application with each affected cluster and test the update.

  5. Re-enable automatic synchronization when testing is complete.

 

Parent topic:

Version 6.0.1 and later Installing updates for multiple clusters

 

Previous topic

Version 6.0.1 and later Applying fix packs to multiple clusters in the same cell

 

Next topic

Version 6.0.1 and later Applying updates to custom applications