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  J2EE applications that 
  were developed on other J2EE application servers to Sun Java 
  System Application Server 8x (hereafter called the Application Server).

  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.x/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 

New Features
------------

1) Scripts to install the schema tables in Derby DB for the examples 
   were added. 

Known Problems and Limitations:
-------------------------------
 
  1) 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.

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

     Solution: Change the source code to use the J2EE APIs only.

  3) 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.

  4) Problem:  A component which is 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.

  5) Problem:  On SJSAS 8.2 EE if the value for the runtime deployment descriptor
               element, cache-idle-timeout-in-seconds is 0 for an entity bean, the
               application may throw an error during undeployment.

     Solution: Set the value of cache-idle-timeout-in-seconds element in the
               corresponding sun-ejb-jar.xml file to a value greater
               than 0 or remove the element from the file.  Removing the
               element will allow the server's default value to be used.

  6) Problem:  The CLI commands for SJSAS 8.2 PE and SJSAS 8.2 EE have slight
               differences.  The documentation in this tool describes the CLI
               commands for the SJSAS 8.2 PE product.  The SJSAS 8.2 CLI
               commands for creating JDBC resources, such as, create-jdbc-resource,
               and create-persistence-resource required the use of the --target option.

     Solution: Verify the CLI command options with the asadmin help command.

  7) Problem:  In the CLI commands for SJSAS 8.2 PE and EE the value of the
               --port option is the port number of the admin port.  The default
               port number for SJSAS 8.2 PE is 4848.  The default port number
               for SJSAS 8.2 EE is 4849.  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.

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

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


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