PI79913: HEALTHCLASS.XML MISSING CLUSTER TARGETMEMBERSHIPS AFTER MIGRATION

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• After a migration, health policies which had clusters as
  target members no longer do so.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Configuration Migration Toolkit      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Clusters that set as targets to         *
  *                      health actions in the previous          *
  *                      environment are no longer targets in    *
  *                      the new environment.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The healthclass.xml file for each health action contains a set
  of <targetMembership> tags which specify which servers,
  clusters, etc. to apply the action to. When a user migrates
  their profile from a supported version of WAS to v9, those
  <targetMembership> tags which specified a cluster are removed
  inadvertently, due to an issue with modifying cluster.xml
  files on the deployment manager during migration.
  

Problem conclusion

• To prevent the missing target membership entries, Migration was
  updated to ensure that all target memberships are preserved
  for each health action.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.4.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP