Previous Contents Index Next |
Sun Java System Application Server 7 2004Q2 Update 1 Standard and Enterprise Edition Troubleshooting Guide

> ## Chapter 9
> Migration Problems

> This chapter discusses problems you may encounter while migrating applications to the Application Server environment.

> The following sections are contained in this chapter:

> - Migration Toolbox doesn’t run correctly
> - Non-fatal error occurs during extraction
> - Fatal error occurs during extraction
> - Translation error occurs
> - Trouble migrating from WebLogic

> Full instructions for performing migration tasks can be found in the Sun Java System Application Server Migrating and Redeploying Server Applications manual.

> ##

> Migration Toolbox doesn’t run correctly

> If you have difficulty running the Sun Java System Application Server Migration Toolbox, consider the following possibilities:

> - Is the script customized for your environment?
> - Are JAR files in your extension directory?
> - Are you using the correct JDK?

> ### Is the script customized for your environment?

> It is important that the %MIGTBX_HOME%/bin/setenv.bat script be customized for your environment. Because of limitations of the JDK, you cannot install the Migration Toolbox in a path containing directory names with spaces. For example, do not unpack the archive in your C:\Program Files directory. Instead, unpack the archive either in c:\AppServer7 or c:\.

> ### Are JAR files in your extension directory?

> To avoid class version issues, all JAR files should be removed from your JDK extension directory (%JAVA_HOME%/jre/lib/ext) while running the Migration Toolbox. All the classes necessary for running the Migration Toolbox are included with the distribution.

> Note | Simply renaming the JAR files in the extension directory is not sufficient; you must move them to a different location.

> ### Are you using the correct JDK?

> Because many development machines have several installed copies or versions of the JDK, be sure you know which copy of the JDK you are using. Set the JAVA_HOME environment variable in the %MIGTBX_HOME%/bin/setenv.bat file to ensure you are running the preferred copy with the Migration Toolbox application.

> ##

> Non-fatal error occurs during extraction

> If only part of the automated migration succeeds (or fails), implement one of the solutions in Migration Toolbox doesn’t run correctly, then rerun the extraction or translation. If that doesn’t work, consider the following possibilities:

> - Are you doing a NetDynamics migration?
> - Is manual migration warranted?

> ### Are you doing a NetDynamics migration?

> If a problem occurs with a NetDynamics migration, create a new project in the NetDynamics Studio and import the problematic objects. Simplify them until you can get this project to run through the appropriate tools. Introduce these files back into the original, now-migrated, project.

> ### Is manual migration warranted?

> You may need to migrate the failed objects by hand. This is not as difficult as it may sound. The JATO framework was also designed for manual application authoring. Using the templates in the application package, follow the example of a migrated object of the same type. Documentation has been created to assist in creating new JATO objects manually.

> ##

> Fatal error occurs during extraction

> If a fatal error occurs, verify that the following items are not factors in the failure (listed in approximate order of likelihood):

> 1. Incorrect environment settings—Check the settings of your %MIGTBX_HOME%/bin/setenv.bat file and ensure they are appropriate for your machine.
> 2. Missing external classes
> 3. Incorrect tool property settings—Ensure that the Extraction Tool has valid property settings.
> 4. Using a non-existent runtime feature in a critical location, such as a class initializer or initialization of non-Spider threads to perform background tasks
> 5. Missing links directory or corrupted class files
> 6. Using the incorrect JDK version or platform
> 7. Conflicting class file versions in the boot classpath, such as those present in the JDK's extension directory

> ##

> Translation error occurs

> If you encounter an error during application translation, do the following:

> - Verify that your application description file looks complete and that the XML is valid. Use a tool like XMLSpy or Internet Explorer to open the document and view it.
> - Verify that the Translation Tool settings are correct.
> - Verify that your environment settings in the %MIGTBX_HOME%/bin/setenv.bat file are appropriate for your machine.
> - Verify that you have a complete Migration Toolbox installation.

> ##

> Trouble migrating from WebLogic

> User is trying to port a WebLogic 6.1 web application to Sun Java System Application Server 7 using the Application Server Migration Toolbox. The job is nicely done.

> But now two things occur when using a web application:

> - it don't know if the webapp is connecting with the Oracle DB
> - in debug mode the AppServ gave me this:

> LONG message...

> ##### Possible Solution

> 1. Copy the struts.jar file into /WEB-INF/lib and make the TLD and DTD files valuables on this directory.
> 2. Rebuild the EAR file with the *.sh.

> It seems that the Migration Toolbox cannot handle JSP files that contain struts and other custom tags. These files do not get copied to the target area by the Migration Toolbox, and are listed as errors. I'm assuming that these files can just be moved manually, and the server then configured with the appropriate JAR files (struts.jar, and so on). I was just wondering if anyone had already got past this tool limitation, and if they'd be willing to share their experiences on migrating struts components into Sun Java System Application Server 7.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.