IBM Support

PM20942: DURING POST MIGRATION, HOSTNAME IS CHANGED IN SERVERINDEX.XML

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The problem is that the source profile has a short hostname
    listed in the serverindex.xml header.  When the target profile
    was created the hostname appears as the long name.  This
    triggers the code further down the line to update the host
    attribute of all the endpoints to match the "new" hostname in
    the header line of the serverindex.xml.
    
    6.1 headerline for serverindex.xml  (Source profile)
    <serverindex:ServerIndex xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:serverindex="http://www.ibm.com/websphere/appserver/schema
    s/5.0/s
    rverindex.xmi" xmi:id="ServerIndex_1281036240856"
    hostName="myserver" ...
    
    versus 7.0 headerline for serverindex.xml (Target profile)
    <serverindex:ServerIndex xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:serverindex="http://www.ibm.com/websphere/appserver/schema
    s/5.0/s
    rverindex.xmi" xmi:id="ServerIndex_1281036240856"
    hostName="myserver.ibm.com" ...
    
    Probable cause is that in one way or another the manageprofiles
    command is setting the "hostname" differently in the Target
    profile than how it was set in the source profile.
    

Local fix

  • Workaround is to provide the manageProfile command with
    -hostName parameter and provide the hostname in the same format
    as is set in the source profile.  For example:
    
    host=`hostname --short` ;
    manageprofiles.sh  -create  -profileName AppSrv01
    -serviceUserName scp -dmgrPort  8879 -omitAction
    enableAdminSecurity false -dmgrAdminUserName system
    -enableService true samplesInstallAndConfig -dmgrAdminPassword
    xxxxxxxxx -templatePath
    /opt/IBM/WebSphere7/AppServer/profileTemplates/managed
    -federateLater true   -nodeName ${host}Node01 -hostName ${host}
    
    This will cause the serverindex.xml to match the 6.1 setting.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users migrating to IBM WebSphere        *
    *                  Application Server V7.0 where the target    *
    *                  profile hostname is different than the      *
    *                  source profile hostname.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The host name of the EndPoints are      *
    *                      modified because of the hostname        *
    *                      differences between the source and      *
    *                      target profiles.                        *
    ****************************************************************
    * RECOMMENDATION:  When migrating to the same machine, always  *
    *                  create the target profile with the          *
    *                  identical hostname used to create the       *
    *                  source profile.                             *
    ****************************************************************
    The migration code compares of the hostname values used to
    create the source and target profiles.  It did not take into
    consideration a short hostname and a FQDN were actually the
    same. It then determined that a machine change had occurred
    and proceeded to update the host of all the endpoints.
    

Problem conclusion

  • Instead of a string compare, the migration code will resolve
    each hostname to an InetAddress and compare on that value.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Recreate the target profile with the same name as used be the
    source profile and then redo the migration.  For a cell
    migration you should restore the Deployment Manager to the
    point just before the Federated node migration if the node
    migration was the problem.
    

Comments

APAR Information

  • APAR number

    PM20942

  • 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

    2010-08-20

  • Closed date

    2010-11-29

  • Last modified date

    2010-11-29

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM20942

Modified date: 29 November 2010