Troubleshooting: Application not supported on node error

You attempt to migrate an application from a previous version of WebSphere Commerce to WebSphere Commerce Version 7 in a clustered environment, but you encounter an error during application configuration. The error states that application type is not supported on one federated node. As a result of the error, the migration process cannot continue.

Problem

The error occurs during application configuration, when the migrated application is being deployed to the server. You find an error message similar to the following example in the migration log.
 [2011.08.10.18.17.54] INFO [wsadmin] WASX7327I: Contents of was.policy file:
 [2011.08.10.18.17.54] INFO [wsadmin] grant codeBase "${application}" {
 [2011.08.10.18.17.54] INFO [wsadmin] permission java.security.AllPermission; };
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5017I: Uninstallation of WC_demo started.
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5104I: The server index entry for WebSphere:cell=fp87Cell01,node=fp87Node01+WebSphere:cell=fp87Cell01,node=WC_demo_node is updated successfully.
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5102I: The configuration data for WC_demo from the configuration repository is deleted successfully.
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5011I: The cleanup of the temp directory for application WC_demo is complete.
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5106I: Application WC_demo uninstalled successfully.
 [2011.08.10.18.18.30] INFO [wsadmin] ADMA5016I: Installation of WC_demo started.
 [2011.08.10.18.18.49] INFO [wsadmin] ADMA5055E: Errors in validating application target association for WC_demo -
 [2011.08.10.18.18.49] INFO [wsadmin] ADMA0110E: This type of J2EE application 50 is not supported on nodes [fp87Node01] of version [6]
 [2011.08.10.18.18.49] INFO [wsadmin] ADMA5011I: The cleanup of the temp directory for application WC_demo is complete.
 [2011.08.10.18.18.49] INFO [wsadmin] ADMA5069E: The installation of application WC_demo failed. This application was in the middle of a full update 
                       and therefore is uninstalled from the configuration session. Discard your current configuration session immediately 
                       to recover the application. Do not save changes to the WebSphere Application Server configuration repository. 
                       The application is not uninstalled from this repository. Until the current configuration session is discarded you do 
                       not see this application in the current session.
 [2011.08.10.18.18.49] INFO [wsadmin] WASX7017E: Exception received while running file "C:/IBM/WEBSPH~1/COMMER~1/migration/xml/scripts/deployMigratedEAR.jacl"; 
                       exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for WC_demo failed: 
                       see previous messages for details.
 [2011.08.10.18.18.49] INFO [wsadmin] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
 [2011.08.10.18.18.49] ERROR BUILD FAILED
 [2011.08.10.18.18.49] ERROR C:\IBM\WEBSPH~1\COMMER~1\migration\xml\build.xml:32: The following error occurred while executing this line:
 [2011.08.10.18.18.49] ERROR C:\IBM\WEBSPH~1\COMMER~1\migration\xml\build.xml:50: The following error occurred while executing this line:
 [2011.08.10.18.18.49] ERROR C:\IBM\WEBSPH~1\COMMER~1\migration\xml\ws.xml:39: The following error occurred while executing this line:
 [2011.08.10.18.18.49] ERROR C:\IBM\WEBSPH~1\COMMER~1\migration\xml\ws.xml:390: The following error occurred while executing this line:
 [2011.08.10.18.18.49] ERROR C:\IBM\WEBSPH~1\COMMER~1\migration\xml\ws.xml:448: Java returned: 105

The error states that the type J2EE application 50 is not supported on one federated node of WebSphere Commerce Version 6. The migrated application cannot be deployed successfully, because not all additional federated nodes can be migrated to WebSphere Commerce Version 7 from the previous version before the primary node is migrated.

Solution

Use one of the following solutions.

  1. If you do not want to migrate all the additional nodes:
    1. Redo deployment manager migration from the previous version of WebSphere Commerce to WebSphere Commerce Version 7.
    2. After the deployment manager is migrated, remove the nodes that you do not want to migrate from the previous version of WebSphere Commerce to WebSphere Commerce Version 7.
      1. Open the administrative console of the migrated WebSphere Application Server Deployment Manager in Version 7.
      2. Expand System Administration, then click Nodes.
      3. Select the additional nodes that you want to remove, then click Force Delete.
      4. Click OK.
      5. Click Synchronize changes with nodes to ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes.
      6. Click Save and click OK.
    3. Migrate the other nodes that you did not remove in the previous step.
    4. Redo application migration for the primary node.
  2. If you want to migrate all the additional nodes:
    1. Redo deployment manager migration from the previous version of WebSphere Commerce to WebSphere Commerce Version 7.
    2. Migrate all the additional nodes before you migrate the primary node.
    3. Redo application migration for the primary node.