IBM Support

PK96996: WHEN MIGRATING A CLUSTER TO VERSION 7 THE APPLICATION SERVER ATTEMPTS TO START THE SYSTEM APPLICATIONS.

Fixes are available

PK96996; 7.0.0.7: systemapps.xml entries are not migrated
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The client is going through the migration steps to
    migrate their configuration from Websphere Application Server
    version 6.1 to Version 7.0. After they migrate a node that
    contains a cluster member the member shows these error
    when it is started:
      WSVR0215W: Starting application, ManagementEJB, failed.  The
        application is not installed.
      WSVR0100W: An  error occurred initializing, ManagementEJB
         com.ibm.ws.exception.ConfigurationWarning: No cluster
         target found for application, ManagementEJB
      WSVR0215W: Starting application, filetransferSecured, failed.
        The application is not installed.
      WSVR0100W: An error occurred initializing, filetransferSecured
        com.ibm.ws.exception.ConfigurationWarning: No cluster target
        found for application, filetransferSecured
     -
    This is because the systemapps.xml containied these entries. The
    systemapps.xml on the migrated node was not updated from the
    Version 6 mode.
    

Local fix

  • You can get rid of this messages by editting
    Profile_Home/config/cells/cellname/nodes/nodename/systemapps.xml
    and removing the entries for the applications that should not
    be started.
     -
    Search Keywords: migrate preupgrade postupgrade cluster addnode
    WCS WPS
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who are using the migration tools.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When migrating Websphere Application    *
    *                      Server version 6.1 to Version 7.0,      *
    *                      the systemapps.xml entries are not      *
    *                      migrated.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When migrating Websphere Application Server version 6.1 to
    Version 7.0, the systemapps.xml entries are not migrated.  If
    there weren't any entries in the previous version and the
    profile is migrated into a default profile the profile will
    now start a systemapp in the new version.  If server1 is part
    of a cluster in the old, it will be in the new as well and
    the systemapps.xml entry will not be valid, causing an
    application start error:
    
    WSVR0215W: Starting application, ManagementEJB, failed.  The
    application is not installed.
    WSVR0100W: An  error occurred initializing, ManagementEJB
    com.ibm.ws.exception.ConfigurationWarning: No cluster
    target found for application, ManagementEJB
    WSVR0215W: Starting application, filetransferSecured, failed.
    The application is not installed.
    WSVR0100W: An error occurred initializing, filetransferSecured
    com.ibm.ws.exception.ConfigurationWarning: No cluster target
    found for application, filetransferSecured
    

Problem conclusion

  • Migration now handles the migration of systemapps.xml and it's
    entries, with one exception.  Migration will proceed as
    federation of a node does during federated node migration.
    During federation, there are specific applications that remain
    installed as a system app and are therefore in the
    systemapps.xml file.  If nothing existed in the old
    systemapps.xml, migration will still keep the systemapp that
    is supposed to remain after federation in the new version.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  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 number

    PK96996

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-23

  • Closed date

    2009-10-20

  • Last modified date

    2010-06-11

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021