Use "migrationDisablementReversal.jacl" script to restore functionality to WebSphere V5.x instance migrated to WebSphere V6.0.
 Technote (troubleshooting)
 
Problem(Abstract)
A WebSphere Application Server V5.x instance migrated to WebSphere Application Server V6.0 is disabled during the migration process so that it will no longer start after being migrated.
 
Cause
During migration of a WebSphere Application Server V5.x.x instance to WebSphere Application Server V6.0, the execution of WASPostUpgrade disables the instance being migrated by renaming the serverindex.xml file to serverindex_disabled.xml. If you need to restore functionality to the migrated instance or if you need to run the migration again on this instance, the "migrationDisablementReversal.jacl script installed on the instance during migration will need to be executed to restore the previous instances functionality.
 
Resolving the problem
An example of the script run from the bin directory of the previous migrated V5 instance is as follows:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE

The setupCmdLine script should be executed as administrative user (Windows) or actual root user (Unix) from the <WAS_HOME>/bin directory of the instance being restored prior to executing the command. The command is as follows:

Windows
setupCmdLine.bat

Unix
. ./setupCmdLine.sh

There are several possible scenarios where the migrationDisablementReversal.jacl script could be executed. They are as follows:

Scenario 1- Rollback everything to WebSphere V5.x (DeploymentManager along with migrated nodes)
  1. Stop all V5.x and V6.0 running DeploymentManager/Node processes.
  2. Run migrationDisablementReversal.jacl script against the V5.x DeploymentManager.
  3. Run migrationDisablementReversal.jacl script against the V5.x federated Node.
  4. Start the V5.x DeploymentManager ... start the V5.x federated Node.
  5. WebSphere Application Server V5.x environment should be working.

Scenario 2 - Rollback just a managed Node to V5 after it has been migrated to V6 (ex: want to have a V6 DeploymentManager managing a V5 node)
  1. Migrate V5.x DeploymentManager to V6.0 DeploymentManager.
  2. Before running Managed Node migration, run backupConfig against V6 DeploymentManager. ( This should be performed prior to each Node being migrated so you have multiple backups during each stage of migration.)
    (At this point you have a V6.0 DeploymentManager managing a V6 Node.)
  3. Stop WebSphere Application Server V6.0 DeploymentManager and managed Node.
  4. Run restoreConfig against your V6 DeploymentManager.
  5. Run migrationDisablementReversal.jacl script against the V5 managed Node.
  6. Start the V6.0 DeploymentManager and then start the V5 Managed Node.
  7. Environment should now consist of a V6 DeploymentManager managing a V5.x managed Node.

The migrationDisablementReversal.jacl script should be run against any migrated V5.x instance that you either need to restore functionality or to restore so that WASPreUpgrade can be executed again.
 
Related information
Troubleshooting migration
Rolling back your environment to V5.x
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
92639.500.000
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Migration
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1203464
IBM Group: Software Group
Modified date: Jun 30, 2005