PI18547: VERSION 6.1 FAIL TO START IN MIXED CELL ENVIROMENT AFTER FEDERATION TO VERSION 7.0 CELL

7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as new function.

Error description

• In mixed cell environment of WebSphere Application Server 7.0
  tranformation of configuration file has not been performed for
  the WebSphere Applicaiton Server Version 6.1 managed nodes due
  to which those nodes are not able to start properly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: File registry is not synchronized in    *
  *                      the network deployement environment     *
  *                      to all the managed nodes.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If any changes are made in the file regsitry at deployment
  manager profile level those changes are not synchronized to
  the managed nodes because file registry is not recognized as
  the file that has been changed since its not a config file.
  

Problem conclusion

• Any changes which are made in the file registry at the
  deployment manager level will be synchorized to all the
  managed nodes automatically.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.35, 8.0.0.10 and 8.5.5.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

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP