Migration Tool for Sun Java System Application Server
=====================================================

  The Migration Tool for Sun Java System Application Server (hereafter 
  called the Migration Tool) is used to migrate Java EE applications that 
  were developed on other Java EE application servers to Sun Java 
  System Application Server 9 (hereafter called the Application Server or SJSAS).

  The Migration Tool supports the migration of applications to the 
  Application Server from the following source application servers:

    - J2EE Reference Implementation 1.3/1.4
    - Sun ONE Application Server 6.0/6.5
	- Sun Java System Application Server 7
    - WebLogic Server 5.1/6.0/6.1/8.1
    - WebSphere Application Server 4.0/5.1 
    - JBoss 3.0
    - Sun ONE Web Server 6.0
    - Apache Tomcat 4.1


Contact Information
--------------------

For technical questions or discussions on the Migration Tool, please visit the Sun 
Java System Application Server Migration forum.

Send us your feedback by email to appserver-migration@sun.com

If you need additional information regarding the Application Server Migration 
program, please contact us at ascsp@sun.com

For additional information on the Sun Java System Application Server Migration 
program, please refer to:
         http://wwws.sun.com/software/products/appsrvr/migration/index.html 

Enhancements
------------

1) The target server command-line designator is "sjsas9".

2) If a Java EE archive is provided as the input object a
   corresponding Java EE archive is provided in the output 
   directory.  The build script and ant file are no long
   provided for deployment assistance.

3) Source Server Sun ONE Web Server is no longer supported by the tool.


Known Problems and Limitations:
-------------------------------
 
  1) Problem:  Migration Tool does not work with JDK 6.0.
	
     Solution: Use JDK 5.0.

 2) Problem:  Some JSP files may fail to migrate because they require 
               the inclusion of JSP fragments to make them valid. Although 
               these types of JSPs will work at runtime, it is considered 
               invalid by the Migration Tool because the tool parses the 
               files without considering the included fragments.

     Solution: Copy these files manually from the source directory to the 
               migrated directory.

  3) Problem:  When migrating an archive (EAR, WAR, JAR or RAR file), the 
               Migration Tool does not check the class files to see if  
               non-Java EE APIs are used.  If non-Java EE APIs are used, the 
               migrated application may not run on the Application Server.

     Solution: Change the source code to use the Java EE APIs only.

  4) Problem:  If the structure of the input EAR file is such that the 
               included JAR/WAR files are not directly under the EAR file, 
               but are nested inside a folder structure, the Migration Tool 
               will fail to migrate such an EAR file and will hang during 
               the extraction phase.

     Solution: Change the structure of the input EAR file so all JAR/WAR 
               files are directly under the EAR file. You may also need 
               to edit the application.xml file to effect this change.

  5) Problem:  A web service client might be migrated as a web service.

     Solution: Use the application server's wscompile utility to generated
	       the client classes for deployment.

  6) Problem:  In the CLI commands for SJSAS 9 PE, the value of the
               --port option is the port number of the admin port.  The default
               port number for SJSAS 9 PE is 4848. These values could have been overridden
               during the installation of the application server.

     Solution: Check with the server administrator to confirm the admin port
               number.

  7) Problem:  The help documents may not be viewable in the GUI.

     Solution: Use the local browser window to view the local files in 
               ${ASMT_HOME}/doc/index.html.

  8) Problem:  The Migraton Tool does not support file names and path names with spaces for either the 
	       input archive/source location or the output location.

     Solution: Eliminate spaces in path names and file names. 
    

  See <ASMT_HOME>/doc/limitations.html for a complete list of the Migration 
  Tool's limitations