MustGather: Migration problems
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with the IBM® WebSphere® Application Server Migration component. Gathering this information before calling IBM® support helps familiarize you with the troubleshooting process and saves you time.
 
Resolving the problem
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click MustGather: Read first for all WebSphere Application Server products.


Migration specific MustGather information
The WebSphere Application Server migration process spans components of WebSphere and includes several unique tools. When performing problem determination on migration tools, gather the following information.
  • Background:
    • As of WebSphere Application Server V5.0, the definitive WebSphere migration document is: Migrating to WebSphere V5.0: An End-to-End Migration Guide.

    • If you are migrating to WebSphere Application Server V5.1, follow the recommendations given in: Manually migrating V5.0.2 releases of Network Deployment or Base Edition to V5.1.0 releases.

    • The majority of this document focuses on manual steps required for you to move your applications from earlier versions of WebSphere Application Server to WebSphere Application Server V5.0.

    • How-to questions represent the majority of migration problems. Answers to most questions can be located in the Migration sections of the various WebSphere Application Server Information Centers. Go to the WebSphere Application Server Library and select the appropriate WebSphere Application Server Information Center.

    • Most customers choose not to use the migration utilities, opting to perform a new installation of their migrated applications onto a new system.

    • All releases of WebSphere Application Server V4.0, V5.0, V5.1 and V6.0 provide two automated migration tools to assist you with migration of applications and configurations:
      • WASPreUpgrade saves your previous version application and system configuration.
      • WASPostUpgrade restores your application and system configuration to the new WebSphere Application Server version.

      Information concerning the command line parameters available with the above commands can be located in the WebSphere Application Server Information Center. Go to the WebSphere Application Server Library and select the appropriate WebSphere Application Server Information Center. Then search for WASPreUpgrade or WASPostUpgrade to locate the command line information.
  • When your migration utility experiences a failure, follow these steps:
    1. Trace the shell script:
      • UNIX®: Insert set -x as the second line of the script.
      • Windows®: Insert echo on as the first line of the script.

    2. Trace the Java™ code:
      • When using the WASPreUpgrade and WASPostUpgrade commands, add the -traceString parameter to the command line syntax as shown in the following Windows example:

        WASPostUpgrade.bat "C:\WAS_Backup" -traceString "*=all=enabled" -traceFile logfileName
      • If you are using the Migration GUI, the WASPostUpgrade script should have the -traceString parameters added to the script. The last line of the code executes $JAVA_HOME/bin/java.
      • Insert the following as an argument before -classpath:

        -traceString "*=all=enabled" -traceFile logfileName

    3. Document every Interim Fix installed, including Java™ Development Kit (JDK™) or Java 2 SDK, Standard Edition upgrades.

    4. Provide files in the install_root/logs and backup directories.

    5. Provide the following directories:
      • From the system being migrated:

        install_root/config
        install_root/properties

      • From the migrated system:

        install_root/config
        install_root/properties

      • If migrating a Network Deployment environment, provide the following directories from both the Deployment Manager and the Application Server from each WebSphere version:

        install_root/config
        install_root/properties

    6. Provide a complete explanation of migration environment, such as:
      • What migration step was being performed (WASPreupgrade or WASPostUpgrade)?
      • Does the source environment use models and clones?
      • Was a coexistence installation performed?
      • Is the migration being performed on a single system or multiple systems?
      • Is security enabled?
      • Is this a production system?

    7. Follow instructions to send diagnostic information to IBM support.

  • Migration Utilities:
    • WASPostUpgrade.sh/WASPostUpgrade.bat
    • WASPreUpgrade.sh/WASPreUpgrade.bat
  • Important Notes:.
    • If problems occur in any other WebSphere component, such as install, follow the appropriate Install MustGather procedures.

For a listing of all technotes, downloads, and educational materials specific to the Migration component, search the WebSphere Application Server support site.

 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
A quick guide for migrating to WebSphere Application Se
IBM Redbooks | WebSphere Application Server V6 Migratio
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Migration
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1141284
IBM Group: Software Group
Modified date: Mar 29, 2005